Update region availability and footnote references#2850
Update region availability and footnote references#2850vasivara-MSFT wants to merge 1 commit intoMicrosoftDocs:mainfrom
Conversation
Removing UDF reference as it is available in Canada east now
|
@vasivara-MSFT : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit f8b393f: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Hi @vasivara-MSFT - This pull request was opened in the public repo. PMs should work in the private repo, per the Microsoft Docs contributor guide. We can keep this PR open for review and merge, but would you make future content updates in the private repo? Thank you! @msmimart - Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
There was a problem hiding this comment.
Pull request overview
This PR updates Fabric region availability documentation to reflect that Fabric User Data Functions are now available in Canada East, and reindexes the remaining feature footnotes accordingly.
Changes:
- Removes the Canada East footnote marker that previously indicated a feature limitation.
- Removes the “Fabric User Data Functions” limitation footnote entry and renumbers remaining footnotes.
- Updates all affected superscript references in the “All workloads” region table to match the new footnote numbering.
| <sup>6</sup> [Plan (preview)](../iq/plan/overview.md) isn't available in these regions. | ||
| <sup>3</sup> [Digital twin builder (preview)](../real-time-intelligence/digital-twin-builder/overview.md) isn't available in these regions. | ||
| <sup>4</sup> [Operations agent (preview)](../real-time-intelligence/operations-agent.md) isn't available in these regions. | ||
| <sup>5</sup> [Plan (preview)](../iq/plan/overview.md) isn't available in these regions. |
There was a problem hiding this comment.
The UDF footnote was removed from this region table, but other docs still state that User Data Functions aren't available in a subset of regions and direct readers here for the up-to-date list (for example, docs/data-engineering/user-data-functions/user-data-functions-service-limits.md under "Regional limitations for User Data Functions"). Either keep a footnote/list here for UDF regional availability (updated for Canada East), or update the UDF docs to stop referencing this page for that list so the docs remain consistent.
| <sup>5</sup> [Plan (preview)](../iq/plan/overview.md) isn't available in these regions. | |
| <sup>5</sup> [Plan (preview)](../iq/plan/overview.md) isn't available in these regions. | |
| <sup>6</sup> [User Data Functions](../data-engineering/user-data-functions/overview.md) have region-specific availability. For the current list of supported regions, see [User Data Functions service limits](../data-engineering/user-data-functions/user-data-functions-service-limits.md). |
Removing UDF reference as it is available in Canada east now
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.
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).