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?
Closing the loop on this one. This has been accepted by the Product Group as a bug. They provided a workaround that involved manually updating multiple core solutions and this bug will be patched in the next release that goes out to GCC High.
The plot thickens: I previously assumed this must be a permissions issue of some kind, but it now appears that this is a bug in GCC High, or at least in our customer's GCC High environment. When attempting to create a flow from inside a solution we can trace the execution and find a 500 error on a put request to a specific URL, including qsparams.
We are currently investigating the possibility that LogicApps Policies were put in place by someone on the customer Azure team which might somehow be blocking us from the necessary API we need for the PUT request the error message reflects.
Block connections for specific API connectors - Azure Logic Apps | Microsoft Docs
Unfortunately, this is an extremely large enterprise environment with several hundred policies in place and we have no good way to evaluate these other than reading each one at a time.
It happens on all Dataverse triggers, all SharePoint triggers, and all Teams triggers. We haven't tested more than that because we aren't working with any event triggers outside those apps.
I don't have a screenshot handy, but the error message is already captured in my original post:
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
Edit: the error message above references the shared_commondataserviceforapps API, but the same error message is seen for SharePoint and Teams Triggers as noted above; each of those reflects an appropriate endpoint. That is, when it is a SharePoint trigger, the error message references the endpoint:
and when it is Teams it references the endpoint:
Can you please provide the screenshot & trigger name.
Dataflows, Custom Connectors, Gateways -- all other content that requires a Premium license still works.
Dear partner,
Please validate customer has a premium license assigned.
Did I answer your question? Please consider to mark my post as a solution to help others.
Regards,
Mohamed Sanuj Basheer