clarifying the limitation around dataflows gen1 #1712
Conversation
As per this article https://learn.microsoft.com/en-us/fabric/data-factory/dataflow-gen2-migrate-from-dataflow-gen1 dataflows gen1 can work in a multi-geo configuration if the storage is setup to use a container in the same region as the multi-geo capacity
|
@dgosbell : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
|
Learn Build status updates of commit 6dc3c01:
|
| File | Status | Preview URL | Details |
|---|---|---|---|
| docs/admin/service-admin-premium-multi-geo.md | Details |
docs/admin/service-admin-premium-multi-geo.md
- Line 128, Column 156: [Warning: file-not-found - See documentation]
Invalid file link: '(/power-bi/transform-model/dataflows/dataflows-azure-data-lake-storage-integration)'.
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.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
| @@ -125,7 +125,7 @@ Large-storage format semantic models shouldn't be moved from the region where th | |||
|
|
|||
| * Detailed semantic model metadata lives in the home tenant. | |||
|
|
|||
| * The [dataflows](/power-bi/transform-model/dataflows/dataflows-introduction-self-service) feature isn't supported on Multi-Geo. | |||
| * To use [dataflows gen1](/power-bi/transform-model/dataflows/dataflows-introduction-self-service) on Multi-Geo you must configure dataflow storage to use [Azure Data Lake Storage (ADLS) Gen2]((/power-bi/transform-model/dataflows/dataflows-azure-data-lake-storage-integration)). | |||
There was a problem hiding this comment.
| * To use [dataflows gen1](/power-bi/transform-model/dataflows/dataflows-introduction-self-service) on Multi-Geo you must configure dataflow storage to use [Azure Data Lake Storage (ADLS) Gen2]((/power-bi/transform-model/dataflows/dataflows-azure-data-lake-storage-integration)). | |
| * To use [dataflows gen1](/power-bi/transform-model/dataflows/dataflows-introduction-self-service) on Multi-Geo you must configure dataflow storage to use [Azure Data Lake Storage (ADLS) Gen2](/power-bi/transform-model/dataflows/dataflows-azure-data-lake-storage-integration). |
|
Can you review the proposed changes? Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
|
@dgosbell : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
@KesemSharabi As per this article https://learn.microsoft.com/en-us/fabric/data-factory/dataflow-gen2-migrate-from-dataflow-gen1 dataflows gen1 can work in a multi-geo configuration if the storage is setup to use a container in the same region as the multi-geo capacity
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).