Solved: premium capacity in different region

jessegorter · ‎08-31-2022

Hi,

does anyone else have a premium capacity in a different region than their tenant? and does this pose extra performance issues or other issues?

Moving a capacity seems intensive work, and I would like to know if it is worth the effort?

v-luwang-msft · ‎09-04-2022

Hi @jessegorter ,

Multi-Geo is a Power BI Premium feature that helps multinational customers address regional, industry-specific, or organizational data residency requirements. As a Power BI Premium customer, you can deploy content to datacenters in regions other than the home region of the Power BI tenant. A geo (geography) can contain more than one region.

And it with the below limitations:

Confirm that any movement you initiate between regions follows all corporate and government compliance requirements prior to initiating data transfer.
Cached data and queries stored in a remote region stays in that region at rest. Additionally the data at rest will be replicated to another region in the same Azure geography for disaster recovery if the Azure geography contains more than one region. Data in transit may go back and forth between multiple geographies.
When moving data from one region to another in a Multi-Geo environment, the source data may remain in the region from which the data was moved for up to 30 days. During that time end users don't have access to it. It's removed from this region and destroyed during the 30-day period.
Query text and query result traffic for imported and DirectQuery data models does not transit through the home region. The report metadata does still come from the home region, and certain DNS routing states may take such traffic out of the region.
Certain features such as screenshots, data alerts and others will still process data in the home region.
The detailed dataset metadata that is cached as part of enhanced metadata scanning is always stored in the home region, even if the scanned dataset is located in a remote region.
The dataflows feature is not supported on Multi-GEO at this time.
It is possible to create and maintain large-storage format datasets in remote regions to meet data residency requirements. However, note that you cannot move storage format datasets to another region. Moving large-storage format datasets from the region where they were created will result in reports failing to load the dataset. Move the large-storage dataset back to its original region to make it available. If you must move such a model, you must deploy it as if it was a new model, and then delete the old model from the undesired region.
Multi-Geo doesn't support Metrics.

To learn more details and how to configure it ,refer:

https://docs.microsoft.com/en-us/power-bi/admin/service-admin-premium-multi-geo

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Best Regards,
Lucien

View solution in original post

Pepi · ‎04-03-2024

Hi @v-luwang-msft

If I'm reading the article (Configure Multi-Geo support for Power BI Premium ) correctly, creating a Fabric capacity in a region that is not your tenant's home region and moving some PBI workspace there, would migrate the data on that workspace (semantic models etc) to the capacity's region - is that correct? I need to find a definitive confirmation for this because I'm getting some conflicting advices on this even from Microsoft support.

Thanks

bernhard0614 · ‎10-28-2022

Hi, just a short questions about the limitations - do they apply to all workspaces, that are running on the premium capacity or do they affect the whole power bi tenant (including all "pro" workspaces)?

Thanks in Advance,
Best regards,
Bernhard

v-luwang-msft · ‎09-04-2022

Hi @jessegorter ,

Multi-Geo is a Power BI Premium feature that helps multinational customers address regional, industry-specific, or organizational data residency requirements. As a Power BI Premium customer, you can deploy content to datacenters in regions other than the home region of the Power BI tenant. A geo (geography) can contain more than one region.

And it with the below limitations:

Confirm that any movement you initiate between regions follows all corporate and government compliance requirements prior to initiating data transfer.
Cached data and queries stored in a remote region stays in that region at rest. Additionally the data at rest will be replicated to another region in the same Azure geography for disaster recovery if the Azure geography contains more than one region. Data in transit may go back and forth between multiple geographies.
When moving data from one region to another in a Multi-Geo environment, the source data may remain in the region from which the data was moved for up to 30 days. During that time end users don't have access to it. It's removed from this region and destroyed during the 30-day period.
Query text and query result traffic for imported and DirectQuery data models does not transit through the home region. The report metadata does still come from the home region, and certain DNS routing states may take such traffic out of the region.
Certain features such as screenshots, data alerts and others will still process data in the home region.
The detailed dataset metadata that is cached as part of enhanced metadata scanning is always stored in the home region, even if the scanned dataset is located in a remote region.
The dataflows feature is not supported on Multi-GEO at this time.
It is possible to create and maintain large-storage format datasets in remote regions to meet data residency requirements. However, note that you cannot move storage format datasets to another region. Moving large-storage format datasets from the region where they were created will result in reports failing to load the dataset. Move the large-storage dataset back to its original region to make it available. If you must move such a model, you must deploy it as if it was a new model, and then delete the old model from the undesired region.
Multi-Geo doesn't support Metrics.