Working within a customer-managed environment, one of our dev teams has suddenly encountered a blocker working with PowerAutomate and connection references. For some reason, the team appears to be unable to create or use connection references within PowerAutomate.
The failure happens anywhere we need to add a connection, even in Trigger events. So, for example, a developer creates a new Flow and tries to set a Dataverse/SharePoint/Teams/{anything that requires a connection} Trigger and instead of defaulting to the currently logged in user's connection, it prompts them to Sign In to create a connection.
Many connections already exist in this environment, yet when the dev clicks the three dots to select an existing Connection Reference, none appear in the list. So, the dev clicks Sign In and provides valid credentials, but they then get the error:
failed to create connection for connection id '/providers/Microsoft.PowerApps/apis/shared_commondataserviceforapps/connections/shared-commondataser-5735739a-fe7a-48ee-84cd-4696-48a6ae5c'. error putting connection /providers/Microsoft.PowerApps/apis/shared_commondataserviceforapps/connections/shared-commondataser-5735739a-fe7a-48ee-84cd-4696-48a6ae5c for connector /providers/Microsoft.PowerApps/apis/shared_commondataserviceforapps
The Guid is different every time; it appears to be a valid Guid for a valid Connection Reference that does get created, but somehow fails during this PUT call to "/providers/Microsoft.PowerApps.apis/shared_commondataserviceforapps" (shared_sharepoint and shared_teams for other connection types).
And now it gets even weirder. If the same dev on the same credentials backs out of the new Flow and goes to Create a new Connection from the Data area, it works just fine. The Connection and Connection Reference get created without issue. But even still, back in Flow, this newly added connection reference is still not available to select.
Because this happened suddenly and has hit all developers on the team (and even service accounts we use) we believe that some kind of permission change was made in the customer-managed environment, but we can't imagine what that could be.
Any thoughts?
