Could not grant admin consent. Your organization does not have a subscription (or service principal) for the following API(s): Azure Communication Services

Admin CHUS 0 Reputation points
2025-04-30T14:57:43.7433333+00:00

On one of my Tenant can't grant admin consent for Teams.ManageCalls and Teams.ManageChats.

I receive the error:

Could not grant admin consent. Your organization does not have a subscription (or service principal) for the following API(s): Azure Communication Services

I try all solution proposed in this Q&A and nothing work for me

Azure Communication Services
Azure Communication Services
An Azure communication platform for deploying applications across devices and platforms.
1,129 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Prabhavathi Manchala 1,050 Reputation points Microsoft External Staff
    2025-04-30T17:20:48.6733333+00:00

    Hi Admin CHUS,

    Hey! It looks like you're running into a bit of a roadblock with granting admin consent for the Teams APIs in Azure Communication Services. The error message you're seeing suggests that your organization doesn't have a service principal set up for the required API.

    Here are a few steps you can try to resolve this issue:

    1. Check for the Service Principal: You can verify if the service principal exists in your tenant by using the Graph API. Replace {resourceID value} with the app ID for the Azure Communication Services API:
         https://graph.microsoft.com/v1.0/servicePrincipals?$filter=appid eq '{resourceID value}'
      
      If the response doesn't return any value, it means the service principal is missing.
    2. Admin Consent URL: You can also create an Admin Consent URL to submit the required permissions. It looks like:
         https://login.microsoftonline.com/{Tenant_ID}/adminconsent?client_id={Application_ID}
      
      Make sure to replace {Tenant_ID} with your tenant ID and {Application_ID} with the application ID of the Azure Communication Services.
    3. Use PowerShell: If the service principal is missing, you can use PowerShell to create it, but you’ll first need the Application.ReadWrite.All permission. Here’s a quick example of how to connect:
         Connect-AzAccount New-AzADServicePrincipal -ApplicationId <Your_Application_ID>
      
    4. Review Azure Portal: Log into the Azure portal and go to Microsoft Entra ID. Navigate to Enterprise applications and verify that the service principal for Azure Communication Services appears there.

    Please accept as "Yes" if the answer provided is useful, so that you can help others in the community looking for remediation for similar issues.

    Let me know if you have any further Queries.


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.