Solved Dynamics 365 Integration Error: "AADSTS900971: No reply address provided."

Status
Not open for further replies.

David_FIO

New User
Joined
Apr 22, 2021
Messages
5
Reaction score
2
Hello,

we have a 3CX onPrem and a Dynamics 365 in the cloud.
I try to integrate these two systems with the follwing manual: https://www.3cx.com/docs/dynamics-crm-integration/

I created an App-Registartion in Azure for 3CX. In this App-Registration it was neccessary to enter the URL to our 3CX-Management-Console as Reply-URI.

The URL to our 3CX-Management-Console is only accessible via VPN. It is not accessible from external.

I'm not able to authorize 3CX in the managemnt console like it is in the manuel described:
1619086167598.png
I always get the error message: "AADSTS900971: No reply address provided" after I click on the button and try to authorize me.

But a reply address is provided in the app registration. (The URL to our 3CX-Managment-Console )

Is it neccessary for the integration with Dynamics 365 that the URL to the 3CX-Management-Console is accessible from external?

Best Regards
David
 
Hello David,

No need to access externally, the Redirect URL is where Dynamics will send your browser after you grant access to 3CX, so as long as you're in the LAN when you do this authorization, it should work.

If you're getting this error, that's probably because you created a wrong app type in Azure. A very common error is that you select a wrong value in point 2.c from our guide. Ensure that you have selected "Public client/native (mobile & desktop)". If you select "Web" there, you will get the error you're describing.

Kind regards.
 
Hello,

I recreated the app-registration to be sure it is the correct app type "Public client/native (mobile & desktop)".
But we still get the same error.
Do you have an other idea as a solution of our problem?
 
Hello,

I recreated the app-registration to be sure it is the correct app type "Public client/native (mobile & desktop)".
But we still get the same error.
Do you have an other idea as a solution of our problem?
Can you share a screenshot of how you created your app in Azure? Particularly what you see in Home > App Registrations > Your app > Redirect URIs.
 
Sorry, it was our fault: we used the wrong URL We used something different in the "api"-part of the url . After i changed the url to "https://my-pbx.example.com:5001/api/oauth2crm" it works.
 
  • Like
Reactions: edossantos
Status
Not open for further replies.

Latest Posts

Forum statistics

Threads
112,323
Messages
591,894
Members
165,472
Latest member
arneg