[CoE Starter Kit - BUG] Azure Resource Manager connector and GCC

[dtheilen]

Does this bug already exist in our backlog?

• [X] I have checked and confirm this is a new bug.

Describe the issue

The latest Setup Wizard app includes the Azure Resource Manager connector and I am not able to establish this connection in my GCC tenant:

I'd like to proceed to manual setup but it's not clear if this connector is used in any other apps or flows.

Expected Behavior

No response

What solution are you experiencing the issue with?

Core

What solution version are you using?

4.15

What app or flow are you having the issue with?

Setup Wizard

What method are you using to get inventory and telemetry?

Cloud flows

Steps To Reproduce

1. Install Core (it was a fresh install)
2. Run Setup Wizard app. (unable to authenticate to the Azure Resource Manager connector)

Anything else?

No response

AB#2203

[Jenefer-Monroe]

The connector is only used in the setup wizard to help with things like Azure Secrets. It shows as being supported by all regions https://learn.microsoft.com/en-us/connectors/arm/ And I am able to use it in tenants without any Azure connectivity.

I also just tested, if I click dont allow here

I will get this error

But as long as I dont try to do Azure things with it like this secret in the new wizard, then it still works.

I'll reach out to our Gov folks internally to see if this is known, and in the meantime you should be able to hit "Dont allow" and proceed from within the Setup Wizard.

[dtheilen]

Wouldn't that not allow all of these connectors though? This was a fresh install.

[Jenefer-Monroe]

oh i see. I only got the one in my case. Maybe because mine was an upgrade

[Jenefer-Monroe]

If you hit switch account, is it the name you woudl expect? Can you use a different connection and get access? Perhaps if you are using a shared account for example.

[dtheilen]

Once I click Switch Account then But if I click on either Create or Don't Allow from there, I'm just brought back to the prior consent screen. If I then click Switch Account again: (nothing is in either dropdown)

Thank you for looking into this!

[Jenefer-Monroe]

Can you go to Connections in the envt and filter to azure resource manager? What do you see?

[dtheilen]

[Jenefer-Monroe]

Can you delete all of those

And then create a new one?

[dtheilen]

Same thing

[Jenefer-Monroe]

ok ive asked our local gcc folks. If you are able to contact product support that might help too.

[dtheilen]

Thank you. I have a couple fresh installs planned with different customers next week. Sounds like the GCC recommendation would be manual setup vs. setup wizard.

[pnoot7]

Getting same issue during fresh install, and connector is allowed in DLP policy.

Is the only path forward to open a support ticket?

[js9331]

Getting same issue during fresh install, and connector is allowed in DLP policy.

Is the only path forward to open a support ticket?

I am a GCC customer and also experiencing this issue after installing September 2023 version this morning... please advise on path forward...

[dtheilen]

The manual setup instructions still work. I've tested this out on a couple different environments and haven't run into any issues. (https://learn.microsoft.com/en-us/power-platform/guidance/coe/setup-core-components#set-up-the-inventory-components-manually)

[pnoot7]

The manual setup instructions still work. I've tested this out on a couple different environments and haven't run into any issues. (https://learn.microsoft.com/en-us/power-platform/guidance/coe/setup-core-components#set-up-the-inventory-components-manually)

It might be, but this has turned into a monthly issue of not being able to use the setup wizard. I question if it should be removed from the product at this point. It is very clear that GCC does not get tested before release.

[dtheilen]

The manual setup instructions still work. I've tested this out on a couple different environments and haven't run into any issues. (https://learn.microsoft.com/en-us/power-platform/guidance/coe/setup-core-components#set-up-the-inventory-components-manually)

It might be, but this has turned into a monthly issue of not being able to use the setup wizard. I question if it should be removed from the product at this point. It is very clear that GCC does not get tested before release.

I don't disagree, and I had a lot of hope for the September release of the Setup Wizard app. An update to the setup documentation calling out the limitation in GCC with this particular app is needed.

[js9331]

The manual setup instructions still work. I've tested this out on a couple different environments and haven't run into any issues. (https://learn.microsoft.com/en-us/power-platform/guidance/coe/setup-core-components#set-up-the-inventory-components-manually)

It might be, but this has turned into a monthly issue of not being able to use the setup wizard. I question if it should be removed from the product at this point. It is very clear that GCC does not get tested before release.

I don't disagree, and I had a lot of hope for the September release of the Setup Wizard app. An update to the setup documentation calling out the limitation in GCC with this particular app is needed.

I've submitted a ticket to Microsoft under my org's support contract to try to find out what's going on with that connector - I'll post back here what I find out from Microsoft, but I'm assuming this is another problem that arises from GCC customers being in Azure Commercial for their various Azure services, while having Power Platform in GCC infrastructure...

[pnoot7]

I've also got a support ticket and have been in contact with our CSAM. Was careful to not mention CoE at all to avoid the support loop of pointing fingers at each other. Will report back if I hear anything.

[Jenefer-Monroe]

Thank you! I should have an answer from internal contact on what they believe to be happening soon and will include here as well.

[Jenefer-Monroe]

If you go Apps (outside of the solution) and chose Edit for the CoE Setup and Upgrade Wizard

You can then remove the Audit Log Setup wizard page

Then Save Then Publish

You should now be able to boot the app. Can you please try that as the workaround while I drive for actual resolution?

[js9331]

The manual setup instructions still work. I've tested this out on a couple different environments and haven't run into any issues. (https://learn.microsoft.com/en-us/power-platform/guidance/coe/setup-core-components#set-up-the-inventory-components-manually)

It might be, but this has turned into a monthly issue of not being able to use the setup wizard. I question if it should be removed from the product at this point. It is very clear that GCC does not get tested before release.

I don't disagree, and I had a lot of hope for the September release of the Setup Wizard app. An update to the setup documentation calling out the limitation in GCC with this particular app is needed.

I've submitted a ticket to Microsoft under my org's support contract to try to find out what's going on with that connector - I'll post back here what I find out from Microsoft, but I'm assuming this is another problem that arises from GCC customers being in Azure Commercial for their various Azure services, while having Power Platform in GCC infrastructure...

Hi - I just got a response back from Microsoft. Short-story is that this connector will not work for GCC users who have Azure in Commercial. Here is the exact response from MS:

If you are using Azure Commercial, unfortunately, this is currently expected behavior. When creating the connector, Power Platform will attempt to authenticate into Azure Gov. If you are using Azure Commerical, it will not find the account, since it is not in Azure Gov. There is currently no known workaround at this time, but our internal teams are working on this issue. There is currently no timeline for this however.

[js9331]

If you go Apps (outside of the solution) and chose Edit for the CoE Setup and Upgrade Wizard

You can then remove the Audit Log Setup wizard page

Then Save Then Publish

You should now be able to boot the app. Can you please try that as the workaround while I drive for actual resolution?

I will give this a try tomorrow and let you know if it worked for us

[dtheilen]

If you go Apps (outside of the solution) and chose Edit for the CoE Setup and Upgrade Wizard

You can then remove the Audit Log Setup wizard page

Then Save Then Publish

You should now be able to boot the app. Can you please try that as the workaround while I drive for actual resolution?

This worked. I deleted Audit logs page, and the connection prompt appeared right after. This was a bit confusing but I was still able to click the Save and Publish icons in the command bar. It took a while to publish. Once it did, a new connector prompt w/out the ARM connector appeared, but I closed the browser tab so I could test this in the published running app instead. I was able to consent and boot the app from there.

[Jenefer-Monroe]

This is wonderful news. Thank you for confirming! Hopefully we can get this connector fixed for GCC soon and in the meantime we can ship a little differently to make sure you can use the Setup Wizard without this workaround in Oct.

[Jenefer-Monroe]

We'll hold this bug open to track the product gap, and I've posted this issue to tweak the kit to have this work for you all in Oct. https://github.com/microsoft/coe-starter-kit/issues/6579

[Jenefer-Monroe]

Hiding all the failed attempts at workarounds above so the real one is easier to find (meanign removing the Audit Log setup wizard page from the setup wizard)

[pnoot7]

I will work to try the work around tomorrow. However, MS Support gave me the same update that was posted above, but I am concerned that outages/issues/advisories are not being posted by the product group, and that they said there is no ETA on a fix.

Is it possible to release a more stable/tested branch of the CoE specific to GCC?

[Jenefer-Monroe]

Hello. I realize you came in at a very bad time for GCC + CoE with first the flow bug that blocked us for weeks and then this. But GCC and CoE has actually been historically quite stable, aside from these two recent product bugs. I do apologize for them and hopefully you see the effort we have put in to remidy for you. We are a very small (2 person) team, and the kit is not a supported product. As a result, we cannot generate specific releases for different configurations, nor can we test on them all. The CoE is not for everyone so you may not be comfortable taking a dependence on it. Hopefully you will give it a shot and see more reliability now that we got over these two recent issues.

[GU-VITA]

Same issue here with GCC tenant. Is this fixed in the October toolkit?

[Star-Donovan]

Same issue now in June 2024