Please support the use of Azure Public Logic Apps and an on-premise data gateway registered by a GCC-Mid (L2) Azure Active Directory tenant
We are a government customer with a GCC-Mid (L2) Azure Active Directory tenant. That means that it is a GCC tenant that runs on Azure Public infrastructure so that it can provide identity services to Office 365 GCC. We have our Azure Public subscriptions linked to that tenant within https://portal.azure.com/. Everything works fine EXCEPT being able to register an on-premise data gateway within our tenant and allowing our Logic Apps in Azure Public to connect to that on-premise data gateway. This is because the gateway is registered in an Azure Government region so that Power BI GCC can leverage it. That all makes sense for a customer who uses Office 365 GCC, but it doesn't work when we ALSO want to use Logic Apps in Azure Public in subscriptions that are linked to the same tenant. For now the workaround would be to create a 2nd AAD tenant in Azure Public, but that is not a great solution because it introduces additional management overhead of a second identity provider when all of our identity is centered already in the GCC-Mid (L2) tenant.
Is there any way this can be simplified for the government customers who want to leverage Azure Public as much as possible?
Jeremy Brun commented
Related GitHub issue that documents this.