Closed
Conversation
Added detailed steps for creating and sharing a semantic model connection, including connection settings and user management.
Contributor
|
@NanditaSa : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
Contributor
Updated image sources and alt texts for clarity in the semantic model connection documentation.
Contributor
|
Learn Build status updates of commit b5d1436:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| docs/iq/plan/planning-sheet-create-share-semantic-connection.md | Details | ||
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/dl-apply-connection.png | 💡Suggestion | Details | |
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/dl-connection.png | 💡Suggestion | Details | |
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/dl-semantic-settings.png | 💡Suggestion | Details | |
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/dl-sql-connection.png | 💡Suggestion | Details | |
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/manage-connection-gateways.png | ✅Succeeded | ||
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/manage-users-settings.png | ✅Succeeded | ||
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/manage-users.png | ✅Succeeded | ||
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/new-semantic-connection.png | ✅Succeeded |
docs/iq/plan/planning-sheet-create-share-semantic-connection.md
- Line 59, Column 1: [Warning: file-not-found - See documentation]
Invalid file link: 'media/planning-sheet-create-share-semantic-connection/semantic-settings.png'. - Line 64, Column 1: [Warning: file-not-found - See documentation]
Invalid file link: 'media/planning-sheet-create-share-semantic-connection/connection.png'. - Line 69, Column 1: [Warning: file-not-found - See documentation]
Invalid file link: 'media/planning-sheet-create-share-semantic-connection/new-connection.png'. - Line 73, Column 1: [Warning: file-not-found - See documentation]
Invalid file link: 'media/planning-sheet-create-share-semantic-connection/apply-connection.png'.
docs/iq/plan/media/planning-sheet-create-share-semantic-connection/dl-apply-connection.png
- Line 0, Column 0: [Suggestion: image-name-incomplete - See documentation]
The image name contains an incomplete word, misspelled word, acronym, or abbreviation that is disallowed.
docs/iq/plan/media/planning-sheet-create-share-semantic-connection/dl-connection.png
- Line 0, Column 0: [Suggestion: image-name-incomplete - See documentation]
The image name contains an incomplete word, misspelled word, acronym, or abbreviation that is disallowed.
docs/iq/plan/media/planning-sheet-create-share-semantic-connection/dl-semantic-settings.png
- Line 0, Column 0: [Suggestion: image-name-incomplete - See documentation]
The image name contains an incomplete word, misspelled word, acronym, or abbreviation that is disallowed.
docs/iq/plan/media/planning-sheet-create-share-semantic-connection/dl-sql-connection.png
- Line 0, Column 0: [Suggestion: image-name-incomplete - See documentation]
The image name contains an incomplete word, misspelled word, acronym, or abbreviation that is disallowed.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
Contributor
|
@NanditaSa : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
Contributor
|
Learn Build status updates of commit 28100d2:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| docs/iq/plan/planning-sheet-create-share-semantic-connection.md | Details | ||
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/dl-connection.png | 💡Suggestion | Details | |
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/dl-semantic-settings.png | 💡Suggestion | Details | |
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/dl-sql-connection.png | 💡Suggestion | Details | |
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/apply-connection.png | ✅Succeeded | ||
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/manage-connection-gateways.png | ✅Succeeded | ||
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/manage-users-settings.png | ✅Succeeded | ||
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/manage-users.png | ✅Succeeded | ||
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/new-semantic-connection.png | ✅Succeeded |
docs/iq/plan/planning-sheet-create-share-semantic-connection.md
- Line 59, Column 1: [Warning: file-not-found - See documentation]
Invalid file link: 'media/planning-sheet-create-share-semantic-connection/semantic-settings.png'. - Line 64, Column 1: [Warning: file-not-found - See documentation]
Invalid file link: 'media/planning-sheet-create-share-semantic-connection/connection.png'. - Line 69, Column 1: [Warning: file-not-found - See documentation]
Invalid file link: 'media/planning-sheet-create-share-semantic-connection/new-connection.png'.
docs/iq/plan/media/planning-sheet-create-share-semantic-connection/dl-connection.png
- Line 0, Column 0: [Suggestion: image-name-incomplete - See documentation]
The image name contains an incomplete word, misspelled word, acronym, or abbreviation that is disallowed.
docs/iq/plan/media/planning-sheet-create-share-semantic-connection/dl-semantic-settings.png
- Line 0, Column 0: [Suggestion: image-name-incomplete - See documentation]
The image name contains an incomplete word, misspelled word, acronym, or abbreviation that is disallowed.
docs/iq/plan/media/planning-sheet-create-share-semantic-connection/dl-sql-connection.png
- Line 0, Column 0: [Suggestion: image-name-incomplete - See documentation]
The image name contains an incomplete word, misspelled word, acronym, or abbreviation that is disallowed.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
Contributor
|
Learn Build status updates of commit d62477a: ✅ Validation status: passed
For more details, please refer to the build report. |
Contributor
PRMerger Results
|
Updated language to clarify that both admins and members can create shareable cloud connections for semantic models. Adjusted wording for non-admin users to simply 'users' for consistency.
Contributor
|
Learn Build status updates of commit ff5e288: ✅ Validation status: passed
For more details, please refer to the build report. |
Contributor
PRMerger Results
|
Contributor
|
Learn Build status updates of commit 1618ca6: ✅ Validation status: passed
For more details, please refer to the build report. |
Contributor
PRMerger Results
|
Corrected the section title and updated prerequisite wording. Changed image syntax to the new format for better consistency.
Contributor
|
Learn Build status updates of commit 73066a6:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| docs/iq/plan/planning-create-database-connection.md | Details | ||
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/apply-connection.png | ✅Succeeded | ||
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/connection.png | ✅Succeeded | ||
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/manage-connection-gateways.png | ✅Succeeded | ||
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/manage-users-settings.png | ✅Succeeded | ||
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/manage-users.png | ✅Succeeded | ||
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/new-connection.png | ✅Succeeded | ||
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/new-semantic-connection.png | ✅Succeeded | ||
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/semantic-settings.png | ✅Succeeded | ||
| docs/iq/plan/planning-sheet-create-share-semantic-connection.md | ✅Succeeded |
docs/iq/plan/planning-create-database-connection.md
- Line 2, Column 1: [Warning: author-missing - See documentation]
Missing required attribute: 'author'. Add the current author's GitHub ID. - Line 2, Column 1: [Warning: ms-author-missing - See documentation]
Missing required attribute: 'ms.author'. Add the current author's Microsoft alias. - Line 2, Column 1: [Warning: ms-service-missing - See documentation]
Missing attribute: 'ms.service'. If you specify 'ms.subservice', you must also specify 'ms.service'. - Line 2, Column 1: [Suggestion: ms-service-suggested]
Missing required attribute: 'ms.service'. ms.service is suggested for each article that is published on Learn.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
Removed author metadata from the database connection documentation.
Contributor
|
Learn Build status updates of commit 591824f: ✅ Validation status: passed
For more details, please refer to the build report. |
Contributor
PRMerger Results
|
Added steps for creating and connecting a Planning sheet to a dataset, including prerequisites and detailed instructions.
Contributor
|
Learn Build status updates of commit e50022a:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| docs/iq/plan/planning-how-to-get-started.md | Details | ||
| docs/iq/plan/planning-sheet-creation.md | Details | ||
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/apply-connection.png | ✅Succeeded | ||
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/connection.png | ✅Succeeded | ||
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/manage-connection-gateways.png | ✅Succeeded | ||
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/manage-users-settings.png | ✅Succeeded | ||
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/manage-users.png | ✅Succeeded | ||
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/new-connection.png | ✅Succeeded | ||
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/new-semantic-connection.png | ✅Succeeded | ||
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/semantic-settings.png | ✅Succeeded | ||
| docs/iq/plan/planning-create-database-connection.md | ✅Succeeded | ||
| docs/iq/plan/planning-sheet-create-share-semantic-connection.md | ✅Succeeded |
docs/iq/plan/planning-how-to-get-started.md
- Line 2, Column 8: [Warning: duplicate-titles - See documentation]
Title 'Get started with Planning sheets - Microsoft Fabric' is duplicated in: 'iq/plan/planning-how-to-get-started.md(2,8), iq/plan/planning-sheet-creation.md(2,8)'. Titles must be unique within a docset. - Line 3, Column 14: [Suggestion: duplicate-descriptions - See documentation]
Attribute 'description' with value 'Learn how to get started with your first Planning sheet in plan (preview). Discover how to create a Planning sheet, connect to your semantic model, and perform planning, budgeting, forecasting, and data analysis.' is duplicated in 'iq/plan/planning-how-to-get-started.md(3,14)', 'iq/plan/planning-sheet-creation.md(3,14)'.
docs/iq/plan/planning-sheet-creation.md
- Line 2, Column 8: [Warning: duplicate-titles - See documentation]
Title 'Get started with Planning sheets - Microsoft Fabric' is duplicated in: 'iq/plan/planning-how-to-get-started.md(2,8), iq/plan/planning-sheet-creation.md(2,8)'. Titles must be unique within a docset. - Line 12, Column 30: [Warning: file-not-found - See documentation]
Invalid file link: 'plan/planning-create-database-connection.md'. - Line 13, Column 30: [Warning: file-not-found - See documentation]
Invalid file link: 'plan/planning-sheet-create-share-semantic-connection.md'. - Line 38, Column 5: [Warning: file-not-found - See documentation]
Invalid file link: 'media/planning-sheet-how-to-get-started/new-plan-creation.png'. - Line 42, Column 5: [Warning: file-not-found - See documentation]
Invalid file link: 'media/planning-sheet-how-to-get-started/new-plan-creation-2.png'. - Line 3, Column 14: [Suggestion: duplicate-descriptions - See documentation]
Attribute 'description' with value 'Learn how to get started with your first Planning sheet in plan (preview). Discover how to create a Planning sheet, connect to your semantic model, and perform planning, budgeting, forecasting, and data analysis.' is duplicated in 'iq/plan/planning-how-to-get-started.md(3,14)', 'iq/plan/planning-sheet-creation.md(3,14)'. - Line 29, Column 4: [Suggestion: duplicate-alt-text - See documentation]
Alt text 'Screenshot of the getting started options.' is duplicated. Within an article, alt text must be unique. - Line 38, Column 5: [Suggestion: duplicate-alt-text - See documentation]
Alt text 'Screenshot of the getting started options.' is duplicated. Within an article, alt text must be unique.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
Contributor
|
Learn Build status updates of commit edb2d4e:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| docs/iq/plan/planning-how-to-get-started.md | Details | ||
| docs/iq/plan/planning-sheet-creation.md | Details | ||
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/apply-connection.png | ✅Succeeded | ||
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/connection.png | ✅Succeeded | ||
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/manage-connection-gateways.png | ✅Succeeded | ||
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/manage-users-settings.png | ✅Succeeded | ||
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/manage-users.png | ✅Succeeded | ||
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/new-connection.png | ✅Succeeded | ||
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/new-semantic-connection.png | ✅Succeeded | ||
| docs/iq/plan/media/planning-sheet-create-share-semantic-connection/semantic-settings.png | ✅Succeeded | ||
| docs/iq/plan/media/planning-sheet-how-to-get-started/new-plan-creation-2.png | ✅Succeeded | ||
| docs/iq/plan/media/planning-sheet-how-to-get-started/new-plan-creation.png | ✅Succeeded | ||
| docs/iq/plan/planning-create-database-connection.md | ✅Succeeded | ||
| docs/iq/plan/planning-sheet-create-share-semantic-connection.md | ✅Succeeded |
docs/iq/plan/planning-how-to-get-started.md
- Line 2, Column 8: [Warning: duplicate-titles - See documentation]
Title 'Get started with Planning sheets - Microsoft Fabric' is duplicated in: 'iq/plan/planning-how-to-get-started.md(2,8), iq/plan/planning-sheet-creation.md(2,8)'. Titles must be unique within a docset. - Line 3, Column 14: [Suggestion: duplicate-descriptions - See documentation]
Attribute 'description' with value 'Learn how to get started with your first Planning sheet in plan (preview). Discover how to create a Planning sheet, connect to your semantic model, and perform planning, budgeting, forecasting, and data analysis.' is duplicated in 'iq/plan/planning-how-to-get-started.md(3,14)', 'iq/plan/planning-sheet-creation.md(3,14)'.
docs/iq/plan/planning-sheet-creation.md
- Line 2, Column 8: [Warning: duplicate-titles - See documentation]
Title 'Get started with Planning sheets - Microsoft Fabric' is duplicated in: 'iq/plan/planning-how-to-get-started.md(2,8), iq/plan/planning-sheet-creation.md(2,8)'. Titles must be unique within a docset. - Line 12, Column 30: [Warning: file-not-found - See documentation]
Invalid file link: 'plan/planning-create-database-connection.md'. - Line 13, Column 30: [Warning: file-not-found - See documentation]
Invalid file link: 'plan/planning-sheet-create-share-semantic-connection.md'. - Line 3, Column 14: [Suggestion: duplicate-descriptions - See documentation]
Attribute 'description' with value 'Learn how to get started with your first Planning sheet in plan (preview). Discover how to create a Planning sheet, connect to your semantic model, and perform planning, budgeting, forecasting, and data analysis.' is duplicated in 'iq/plan/planning-how-to-get-started.md(3,14)', 'iq/plan/planning-sheet-creation.md(3,14)'. - Line 29, Column 4: [Suggestion: duplicate-alt-text - See documentation]
Alt text 'Screenshot of the getting started options.' is duplicated. Within an article, alt text must be unique. - Line 38, Column 5: [Suggestion: duplicate-alt-text - See documentation]
Alt text 'Screenshot of the getting started options.' is duplicated. Within an article, alt text must be unique.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
Contributor
|
If you approve the new content in this PR, the commits must be moved to the private repository for automated checks and publishing. After you move the commits, close this PR ( Note that the new articles will need to be added to a TOC file. The real names in #label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team |
Contributor
|
@NanditaSa I'll create a copy of this PR in the internal repo and make requested changes. I'll leave comments in this PR for any major updates I think should be made to your suggested content, just so you are aware of them (but no need for you to implement them, I will do it in my PR). |
baanders
reviewed
Apr 6, 2026
| @@ -0,0 +1,54 @@ | |||
| --- | |||
Contributor
There was a problem hiding this comment.
A version of this getting started document already exists on the site, Get started with Planning sheets. We can't publish a second version next to it.
I think your intent here is to replace the current Getting Started flow, which shows the steps to create the connections in the same article, with a flow that outsources those steps to their own documents?
I'll edit the existing docs to reflect this.
Contributor
There was a problem hiding this comment.
Real connection strings can't be shown in docs images, it should be replaced with a fictitious value. I use the text box editor in Paint.
Contributor
There was a problem hiding this comment.
Unfortunately blur isn't an approved way to obscure sensitive information in docs, it should be replaced with a fictitious value.
Contributor
There was a problem hiding this comment.
I'll reduce the size of this image and others like it that are small horizontally, so it doesn't show up huge in doc text. I use the Resize and Skew feature of Paint.
baanders
reviewed
Apr 6, 2026
|
|
||
| ## Connect a Planning sheet to a dataset | ||
|
|
||
| 1. Select **Planning > Name the new Planning sheet** and **Create. |
Contributor
There was a problem hiding this comment.
This step sounds like it should be part of the previous section, "Create a planning sheet"
| @@ -0,0 +1,39 @@ | |||
| --- | |||
| title: "Create a Database Connection in Fabric Plan " | |||
Contributor
There was a problem hiding this comment.
We use sentence case for titles and headings
| description: "Learn how to create a database connection in Fabric Plan." | ||
| ms.topic: how-to | ||
| ms.date: 04/02/2026 | ||
| #customer intent: As a user, I want to know understand and use Forecasts effectively. |
Contributor
There was a problem hiding this comment.
Customer intent looks mismatched
| To connect to a semantic model from a Plan artifact. | ||
|
|
||
| ## Create a semantic model connection | ||
|
|
Contributor
There was a problem hiding this comment.
I'm guessing this article should also have a prereq section, similar to the one for database connections
|
|
||
| Before you set up Planning sheets, make sure you have the following prerequisite in place: | ||
|
|
||
| * Create your individual connections or data sources to connect with a Fabric SQL database and Power BI semantic model. |
Contributor
There was a problem hiding this comment.
Thinking it might be appropriate to change this to something like "Data in a Fabric SQL database."
It seems strange to suggest they create connections, since that's the purpose of this article, and to suggest they create Power BI semantic models, since there's a different article for that.
| These steps must be completed by a workspace admin or member who has access to the semantic model. | ||
| 1. Go to **Settings > Manage connections and gateways > New.** | ||
|
|
||
| :::image type="content" source="media/planning-sheet-create-share-semantic-connection/manage-connection-gateways.png" alt-text="Screenshot of opening the manage connection gateways settings."::: |
Contributor
There was a problem hiding this comment.
Images in a list must be indented or they'll break the list formatting.
Contributor
|
Closing in favor of internal PR linked above. #please-close |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Thank you for contributing to Microsoft Fabric documentation
Fill out these items before submitting your pull request:
If you are working internally at Microsoft:
Provide a link to an Azure DevOps Boards work item that tracks this feature/update.
Who is your primary Skilling team contact? @mention them individually tag them and let them review the PR before signing off.
@SnehaGunda
For internal Microsoft contributors, check off these quality control items as you go
1. Check the Acrolinx report: Make sure your Acrolinx Total score is above 80 minimum (higher is better) and with no spelling issues. Acrolinx ensures we are providing consistent terminology and using an appropriate voice and tone, and helps with localization.
2. Successful build with no warnings or suggestions: Review the build status to make sure all files are green (Succeeded).
3. Preview the pages:: Click each Preview URL link to view the rendered HTML pages on the review.learn.microsoft.com site to check the formatting and alignment of the page. Scan the page for overall formatting, and look at the parts you edited in detail.
4. Check the Table of Contents: If you are adding a new markdown file, make sure it is linked from the table of contents.
5. #sign-off to request PR review and merge: Once the pull request is finalized and ready to be merged, indicate so by typing
#sign-offin a new comment in the Pull Request. If you need to cancel that sign-off, type#hold-offinstead. Signing off means the document can be published at any time. Note, this is a formatting and standards review, not a technical review.Merge and publish
#sign-off, there is a separate PR Review team that will review the PR and describe any necessary feedback before merging.#sign-offagain. The PR Review team reviews and merges the pull request into the specified branch (usually the main branch or a release- branch).