We've created an Azure Storage Account and have granted a service principal the "Storage Blob Data Contributor" role. Testing via the console and applicaition code works, we're able to connect to the endpoint, access the container, and see the blobs. Knowing that this is working, we then went over to Power Automate and created a connector to Azure Blob Storage and provided the storage account name, and the necessary connection information to use our service principal.
Unfortunately, when running the trigger, we're getting a "BadGateway" error. Looking more deeply, it looks like the connector is "assuming" that our Azure tenant is also in GCC (which is "not" the case) and its attempting to replace our endpoint URLs with ones within the context of GCC. I've attached a screenshot of the flow's error code along with a screenshot of our Storage Account's list of endpoints in Azure (commercial). Can we create a custom connector that "does not" assume our Azure tenant is GCC?
