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:
- 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:
If the response doesn't return any value, it means the service principal is missing.https://graph.microsoft.com/v1.0/servicePrincipals?$filter=appid eq '{resourceID value}'
- Admin Consent URL: You can also create an Admin Consent URL to submit the required permissions. It looks like:
Make sure to replacehttps://login.microsoftonline.com/{Tenant_ID}/adminconsent?client_id={Application_ID}
{Tenant_ID}
with your tenant ID and{Application_ID}
with the application ID of the Azure Communication Services. - 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>
- 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.