Connection could not be created due to a connection API Policy violation

(1) Share

Report

Posted on by uzma-fis

Finding something quite strange.

Created environment with dataverse.

I go to tables, Import data, select a SharePoint site as example. I cannot sign in nor can I connect and have this error message

Unable to create an OAuth connection. Reason: "Connection could not be created due to a connection API Policy violation. Policies may be adjusted in the Power Platform admin center. (Session ID: c163fd45-a72c-4fb1-a5ff-d383a2cf6e5c, Region: uk)"

I have checked DLP policy and we have power query, dataflow, sharepoint connector. I don't know what "API" would even mean?

Surely this should just work for dataverse? It must be policy but would like more understanding if anyone can help.

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (18)

Answers (0)

cchannon 4,702 Moderator on at

Like (0)

Report

Is the connection cross-tenant? That is a common constraint as part of data loss prevention rules.

Was this reply helpful? Yes No
uzma-fis 8 on at

Like (0)

Report

Not cross tenant at all

Was this reply helpful? Yes No
cchannon 4,702 Moderator on at

Like (0)

Report

Then if you're not a Power Platform Admin or Global Admin, you're going to have to get in touch with the correct person and find out what policies have been set. You won't be able to solve this without their visibility and access.

Was this reply helpful? Yes No
John_DLC 2 on at

Like (0)

Report

HTTP with Azure AD connector must be in the Business category of the DLP policy for the OAuth connection to work. Just ran into this issue and had to go through numerous connectors to track down the root cause.

Was this reply helpful? Yes No
cihys 16 on at

Like (0)

Report

Have exactly the same issue. Unlocking HTTP with Azure AD didn't help 😞

Was this reply helpful? Yes No
uzma-fis 8 on at

Like (0)

Report

Here's the pickle. I have another environment with dataverse and it works fine. It has it's own specific DLP policies.

We moved the problematic environment to this DLP and it still did not work.

We noticed connections or authentication does not pick up when you go to connection from a dataflow or an import.

We will log a call with Microsoft and see how things go

Was this reply helpful? Yes No
Plinderoth 42 on at

Like (0)

Report

Was this solved? If so, how?

Was this reply helpful? Yes No
P3Sven 119 on at

Like (0)

Report

Would be interesting for me as well. Have the same issue! Any update from Microsoft?

Was this reply helpful? Yes No
RadVine 34 on at

Like (1)

Report

Same ocurred to us as the change from HTTP with Azure was changed to HTTP with Entra ID. Mgiht have to involve MS to solve this.

Was this reply helpful? Yes No
JPMayorga 3 on at

Like (0)

Report

Hey, hello there, I have exactly the same issue, has someone found a solution?

Was this reply helpful? Yes No