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,... / Permission issues
Customer experience | Sales, Customer Insights,...
Answered

Permission issues

(1) ShareShare
ReportReport
Posted on by MS-04120740-0 2
Hello Team,
 
I want to test / execute ms dynamics crm incident api in my client application. This requires setting up Client App for authentication.
 
I was able to configure app credentials. However when i am using token generated for incidents API, it throws error
{
"error": {
"code": "0x80072560",
"message": "The user is not a member of the organization."
}
}
 
Is it because of API permissions is set as Delegated Permissions? API permissions is disabled (Attached screenshot)
 
Please advise.
 
thanks
Screenshot 2024-1...

Your file is currently under scan for potential threats. Please wait while we review it for any viruses or malicious content.

Categories:
Microsoft Dynamics CRM
I have the same question (0)
  • Verified answer
    Amit Katariya007 Profile Picture
    Amit Katariya007 10,409 Moderator on at
    The error message The user is not a member of the organization often indicates a mismatch or an issue with the user context used to generate the access token. Based on your description and the mention of Delegated Permissions, here are potential causes and steps to resolve them:
     
    Possible Causes and Solutions:
     
    1. Delegated vs. Application Permissions:
    Delegated Permissions require a user context and are used when an application acts on behalf of a signed-in user. The token is tied to the user's identity.
     
    Application Permissions allow the application to act as itself without requiring a user. These are typically used for server-to-server communication.
     
    Solution: If you are implementing a server-to-server integration, ensure you configure Application Permissions in Azure AD for your app. Update the API permissions in your Azure AD app registration to include the necessary Application permissions for the Dynamics 365 API (e.g., Organization.ReadWrite.All).
     
    2. User Not Part of the Organization:
    The user associated with the token may not be licensed or configured in the Dynamics 365 organization.
     
    Solution: Verify that the user exists in the Dynamics 365 instance and has the required security roles to access the incident entity.
     
    3. Incorrect Token Scope:
    The scope in the token request might not match the required permissions.
    Solution: Ensure the token request uses the correct resource URL for Dynamics 365:
     
    https://<yourorganizationname>.crm.dynamics.com/.default
     
    Replace <your-organization-name> with your actual Dynamics 365 organization name.
     
    4. API Permissions Not Granted:
    The app might not have been granted admin consent for the requested permissions.
     
    Solution:
    Go to Azure AD → App Registrations → Select your app → API Permissions.
    Click Grant admin consent for the permissions.
     
    5. Environment URL Configuration:
    If the token is generated for a different environment or region, the API call will fail.
     
    Solution: Ensure you are generating the token for the correct Dynamics 365 environment URL.
     
    6. Disabled User Account:
    The user associated with the token might be disabled in Dynamics 365.
     
    Solution: Check the user status in Dynamics 365 under Settings → Security → Users and ensure the user is enabled.
     
    Testing the Fix:
    Once you've made the changes:
    1. Generate a new token after updating the permissions or user context.
     
    2. Test the token using a tool like Postman or directly in your client application.
     
    Below is an Example Token Request for Application Permissions:

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 April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
Muhammad Shahzad Shafique Profile Picture

Muhammad Shahzad Sh... 69 Most Valuable Professional

#2
ManoVerse Profile Picture

ManoVerse 66 Super User 2026 Season 1

#3
11manish Profile Picture

11manish 45

Last 30 days Overall leaderboard

Featured topics

Hide selecting Contact for potential customer when creating quote

Product updates

Dynamics 365 release plans