Disaster Recovery considerations for Power BI Embedded Capacity

Hi Shagil_I -Power BI allows for workspaces to be moved between capacities, but moving to a capacity in a different region may not always provide immediate disaster recovery. While you can reassign a Power BI workspace to another capacity in a different region, the actual data (reports, models, datasets) remains tied to the original region where the workspace was created. For full disaster recovery, additional steps such as replicating data or utilizing Azure's geo-redundancy options would be necessary.

Ref links:

Microsoft Fabric disaster recovery experience specific guidance - Microsoft Fabric | Microsoft Learn

Power BI high availability, failover, and disaster recovery FAQ - Power BI | Microsoft Learn

Public Preview of Multi-Geo for Power BI Premium | Blog di Microsoft Power BI | Microsoft Power BI

Multi-Geo support for Fabric - Microsoft Fabric | Microsoft Learn

Hi rajendraongole1, 
Thanks for your response. 

Our use case is to ensure data refresh and report accessibility when the region of Capacity is in outage, assuming all Azure services in this region are down; but services in Power BI home region remain available.

Looking at https://learn.microsoft.com/en-us/fabric/admin/service-admin-premium-multi-geo?tabs=power-bi-embedded#considerations-and-limitations 

When you're using Multi-Geo, the following items are stored in the region that isn't your home region:
- Models (.ABF files) for import and DirectQuery semantic models
- Query cache
- R images

From this, i understand that in our use case, as rest of the items are in home region, we only need to consider how to bring these items in the region of the target capacity (in same geographic area).

From the same page, it also appears to say that when a capacity is changed to one in a new region, the items are copied to new region.

When moving data from one region to another, the source data might 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. The data is removed from this region and destroyed during the 30-day period.

Also, here it says that large semantic models cannot be moved to new regions, so, i assume that small semantic models can be moved to other regions.

It's possible to create and maintain large-storage format semantic models in remote regions to meet data residency requirements. However, you can't move storage format semantic models to another region. Moving large-storage format semantic models from the region where they were created results in reports failing to load the semantic model. Move the large-storage semantic model back to its original region to make it available. If you must move such a model, deploy it as if it was a new model, and then delete the old model from the undesired region.

So, the questions is mainly to know whether there is a region level replication of the items (Models, Query cache, R images, as mentioned above) for Power BI Embedded ensuring, at least, read access (to allow copy) of these items to another region in case of a disaster.

What we are looking for is similar to as described here for Power BI items: https://learn.microsoft.com/en-us/fabric/security/experience-specific-guidance#sample-scenario. This page is for specific Fabric items. Does this also apply to Power BI Semantic Models, and other items in a Power BI Workspace associated with Embedded Capacity?