Whenever you are asked to select a Region, stop and think!

Sep 11 (edited) in General

There are many places where you can be asked to select a Region in Fabric, or in Azure more generally.

So I recommend, always stopping and thinking about the region you select (do research on the topic, before you choose), because the selection you make can sometimes have quite a big impact on functionality/ user experience.

Here's some very common places where you need to specify a region, and where making the wrong decision, can cause issues:

When you set up your Fabric free trial - make sure you select a Region that is supported. You can find which region you are currently in (in Microsoft's world) - using this link.
And you can find a list of supported Fabric regions in this link. If you set up your Azure instance outside one of these regions, it's likely you will NOT have access to all the Fabric experiences
When you set up Azure DevOps organisation - this is a classic one. Unfortunately, currently you cannot connect an ADO repository to a Workspace attached to a Capacity in a different Azure region. It's also not possible to sync your Fabric workspace to an ADO repository on another tenant.
Setting up a new capacity. And then switching the Capacity of a workspace from Capacity A (in Region A) to Capacity B (in Region B) can cause issues too with Region Locking. This basically restricts you from making such a change, and might cause you to have to manually migrate your assets between two regions.

What are your experiences, have you ever selected the wrong region and lived to regret it?

6 comments