Forum Discussion
Helper IFabric Capacity location != Azure DevOps location
Hi,
my customer has an trial capacity based on West Germany and also wanted to start an F64 capacity within germany region in the near future.
We also created a new AzureDevOps organization but there we only has "Europe" as an option for the location.
And now we get the following error when we wanted to connect our Workspace with DevOps:
This workspace is in a different region. Go to the workspace admin settings to enable cross-region connections.
Is the option "enable cross-region connections" currently the only option or is there an option i.e. to relocate the DevOps Organization to Germany?
Hi Anonymous , sorry for my late replay.
The workaround is to enable the "cross region git connections" option in the admin portal.
For me this is only an workaround becauce I think the regions available when creating an fabric capacity are much more "detailed" then the regions available when creating a new AzureDevOps-Organization.
For example:
Fabric:
- West Germany
- North Germany
- France
- ...
Azure DevOps
- Europe
- North America
And this does not make sense for me.
6 Replies
- NandanHegde
Super User
updating the admin portal settings is the most easy way or having a fabric capacity in same region as ADO.
You can update the geo of ADO but you need to raise request with MSFT :
tkiwiThanks, but the listed geos of ADO are very different from the available regions for the capacities. Example: Fot ADO there is only europe and for the capacities there are more specific regions available.
- NandanHegde
yes, agree in most Geo cases. Hence the best possible approach is to enable the property in admin portal
Hi tkiwi,
Thanks for reaching out to the Microsoft fabric community forum.
It looks like you are looking for a way to connect workspace of two different orgs in different regions. As NandanHegde already responded to your query, please go through his response and mark it as solution if it solves your issue.
I would also take a moment to thank NandanHegde, for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference.
If I misunderstand your needs or you still have problems on it, please feel free to let us know.
Best Regards,
Hammad.
Community Support TeamIf this post helps then please mark it as a solution, so that other members find it more quickly.
Thank you.
Hi tkiwi,
As we haven’t heard back from you, so just following up to our previous message. I'd like to confirm if you've successfully resolved this issue or if you need further help.
If yes, you are welcome to share your workaround and mark it as a solution so that other users can benefit as well. If you find a reply particularly helpful to you, you can also mark it as a solution.
If you still have any questions or need more support, please feel free to let us know. We are more than happy to continue to help you.
Thank you for your patience and look forward to hearing from you.- tkiwi
Hi Anonymous , sorry for my late replay.
The workaround is to enable the "cross region git connections" option in the admin portal.
For me this is only an workaround becauce I think the regions available when creating an fabric capacity are much more "detailed" then the regions available when creating a new AzureDevOps-Organization.
For example:
Fabric:
- West Germany
- North Germany
- France
- ...
Azure DevOps
- Europe
- North America
And this does not make sense for me.
