Forum Discussion
Helper IFabric Capacity location != Azure DevOps location
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.
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.
Helper IHi 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.