Power Platform Export Solution failing with anonymous access

(0) Share

Report

Posted on by diegochb

Hello, trying to connect via Azure Devops to migrate an application from one environment to another.

On authentication type, I have "Service Principal/Client Secret (supports MFS)"

The from the Service connection list, I select the first environment connection (previously created with the Server URL, Tenant ID, Application ID, Client secret of Application ID).

This tasks runs after Power Platform Tool Installer (completes successful). But the export task fails with

##[error]Failed to connect to instance: <MY URL HERE>. Please verify your credentials for *** and instance url.
Invalid Login Information : The HTTP request was forbidden with client authentication scheme 'Anonymous'.
The HTTP request was forbidden with client authentication scheme 'Anonymous'. => The remote server returned an error: (403) Forbidden.
Unable to Login to Dynamics CRM

Am I missing some configuration? Why is it using anonymous ??

Thanks!

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (4)

Answers (1)

Sort by

Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

If you're using a Service principal, make sure that you have given the App Registration the correct permissions within Azure Active Directory (portal.azure.com). Additionally, make sure the server url is the Power platforms url (org.crm.dynamics.com), and theTenant ID refers to the Azure tenant ID - not the power platform environment instance.

We were able to successfully set this up last week after some troubleshooting

Was this reply helpful? Yes No
diegochb 19 on at

Like (0)

Report
Copy link

Link copied!

Thanks @Anonymous !
Yes, its the ....dynamics.com url, and the tenant id was created with the powershell script provided by MS.
I will check the permissions on the azure portal, thanks a lot!

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

@diegochb The application user associated with the application ID also needs a D365 security role that would allow it to export.

Was this reply helpful? Yes No
Verified answer

diegochb 19 on at

Like (0)

Report
Copy link

Link copied!

Thanks! Yes, apparently I was missing creating a user application with the same application ID previously created.
Then assigning the system admin role, all withing the <env>.crm.dynamics.com url under security settings.

THanks!

Was this reply helpful? Yes No