web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Customer experience | Sales, Customer Insights,... / AADSTS500011: The reso...
Customer experience | Sales, Customer Insights,...
Suggested Answer

AADSTS500011: The resource principal named XXXX.api.crm4.dynamics.com was not found in the tenant named XXXXX. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You might

(0) ShareShare
ReportReport
Posted on by Alessandro Graps 2,664

I tried to execute the CALL at D365 CRM Online API. I am using Postman.But when I tried to Get new Access Token, I have the following error:

"AADSTS500011: The resource principal named XXXX.api.crm4.dynamics.com was not found in the tenant named XXXXX. This can happen if the application has not been installed by the administrator of the tenant or consented to by any user in the tenant. You might have sent your authentication request to the wrong tenant."

Here the steps that I followed:

  1. Create new App registration on Azure Active Directory 

    pastedimage1635153238858v1.png

     pastedimage1635153238859v2.png

     

    pastedimage1635153238859v3.png

     pastedimage1635153238859v4.png

  2. Configure Environment on PostMan 

    pastedimage1635153238859v5.png

  3. Configure Authorization

     pastedimage1635153238860v6.png

  4. Click On "Get New Access Token"

  5. I have this error

     pastedimage1635153238860v7.png

How can I solve the issue?

Thanks

Alessandro

I have the same question (0)
  • Suggested answer
    PerezAguiar Profile Picture
    PerezAguiar Microsoft Employee on at

    Hey!

    At the moment you've configured the first 2 parts:

    - Application user within Azure

    - Postman connection.

    However the error message indicates that this "user" (or application user) doesn't exist in dynamics and doesn't have permissions.  You seem to be missing an intermediate step where you add the application user to Dynamics and provide access.  This is documented on https://docs.microsoft.com/en-us/power-platform/admin/manage-application-users 

    Regards

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the March Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
ManoVerse Profile Picture

ManoVerse 184 Super User 2026 Season 1

#2
11manish Profile Picture

11manish 125

#3
CU11031447-0 Profile Picture

CU11031447-0 100

Last 30 days Overall leaderboard

Featured topics

Hide selecting Contact for potential customer when creating quote

Product updates

Dynamics 365 release plans