Update documentation on Dataflow limitations #2316
Conversation
Clarify limitations of Power Platform Dataflow Connector in workspaces with private links enabled and public access denied.
|
Learn Build status updates of commit 3c4b8c1: ✅ Validation status: passed
For more details, please refer to the build report. |
|
@sasalam : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
There was a problem hiding this comment.
Pull Request Overview
This PR updates the documentation to clarify limitations of the Power Platform Dataflow Connector when used in workspaces with private links enabled and public access denied. The change adds a specific note about dataflow-to-dataflow connectivity limitations that will be resolved in a future rollout.
- Added clarification about Power Platform Dataflow Connector limitations in private link workspaces
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
|
|
||
| A virtual network data gateway must be used for every dataflow connector. The virtual network data gateway must reside in the same virtual network as the workspace-level private link endpoint used by the workspace. | ||
|
|
||
| Power Platform Dataflow Connector - When a workspace has workspace private links enabled and public access denied, for any two dataflows in that workspace (dataflow A and dataflow B), neither dataflow will be able to connect to the other dataflow (using the Power Platform Dataflow Connector) because the dataflow will not appear in the navigator. This functionality will be rolling out soon. |
There was a problem hiding this comment.
The phrase 'This functionality will be rolling out soon' is ambiguous. It's unclear whether the rollout refers to the limitation being introduced or the fix for the limitation. Consider clarifying what specific functionality is being rolled out.
| Power Platform Dataflow Connector - When a workspace has workspace private links enabled and public access denied, for any two dataflows in that workspace (dataflow A and dataflow B), neither dataflow will be able to connect to the other dataflow (using the Power Platform Dataflow Connector) because the dataflow will not appear in the navigator. This functionality will be rolling out soon. | |
| Power Platform Dataflow Connector - When a workspace has workspace private links enabled and public access denied, for any two dataflows in that workspace (dataflow A and dataflow B), neither dataflow will be able to connect to the other dataflow (using the Power Platform Dataflow Connector) because the dataflow will not appear in the navigator. The ability for dataflows in the same workspace to connect to each other using the Power Platform Dataflow Connector will be rolling out soon. |
|
|
||
| A virtual network data gateway must be used for every dataflow connector. The virtual network data gateway must reside in the same virtual network as the workspace-level private link endpoint used by the workspace. | ||
|
|
||
| Power Platform Dataflow Connector - When a workspace has workspace private links enabled and public access denied, for any two dataflows in that workspace (dataflow A and dataflow B), neither dataflow will be able to connect to the other dataflow (using the Power Platform Dataflow Connector) because the dataflow will not appear in the navigator. This functionality will be rolling out soon. |
There was a problem hiding this comment.
| Power Platform Dataflow Connector - When a workspace has workspace private links enabled and public access denied, for any two dataflows in that workspace (dataflow A and dataflow B), neither dataflow will be able to connect to the other dataflow (using the Power Platform Dataflow Connector) because the dataflow will not appear in the navigator. This functionality will be rolling out soon. | |
| Power Platform Dataflow Connector - When a workspace has workspace private links enabled and public access denied, for any two dataflows in that workspace (dataflow A and dataflow B), neither dataflow will be able to connect to the other dataflow (using the Power Platform Dataflow Connector) because the dataflow will not appear in the navigator. |
We can't publish future promises.
|
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.
Approved with the change noted by @v-dirichards.
@sasalam will you please make this change? Then I'll sign off. Thanks!
|
@sasalam - Can you respond to the requested changes or let us know if you would like us to commit them? @msmimart - When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
|
Replaced by https://github.com/MicrosoftDocs/fabric-docs-pr/pull/10939 #please-close |
3 participants
Clarify limitations of Power Platform Dataflow Connector in workspaces with private links enabled and public access denied.
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).