Integration of Copilot Agent With Azure CLU(Language Services) with the help of Microsoft Entra ID

(0) Share

Report

Posted on by AP-26110715-0

I wanted to Connect Copilot agent with Azure Language services(CLU) so for that currently we have two options: One is to connect with API Key which is Working Absolutely fine; While another option is to connect with Microsoft Entra ID which is not working at all.
After Establishing the connection we are getting below Error: Error Message: The connector 'Azure Cognitive Service for Language' returned an HTTP error with code 500. Inner Error: Internal server error Error Code: ConnectorRequestFailure Conversation Id: f342af2e-6159-4585-b17f-f871c866374b Time (UTC): 2025-11-26T07:25:24.953Z

Please help. We've also tried giving Cognitive Services for Language role to the Account but still not working.

Categories:

General

I have the same question (0)

All responses (1)

Answers (0)

Suggested answer

sannavajjala87 123 on at

Like (0)

Report
Integration of Copilot Agent With Azure CLU(Language Services) with the help of Microsoft Entra ID

The Entra ID option uses OAuth and requires proper RBAC roles, resource permissions, and API scopes. A 500 error usually means the connector cannot obtain a valid token or the resource isn’t configured for delegated access.

Fix checklist:

Verify prerequisites:

CLU resource must be in the same tenant and region as Copilot Studio.

Assign Cognitive Services Contributor or Owner role to the Entra ID account.

Check API permissions:

In Azure AD App Registration, ensure https://cognitiveservices.azure.com/.default scope is granted and admin consented.

Authentication settings:

Use “Authenticate with Microsoft” in Copilot Studio and confirm the correct subscription/resource is selected.

Clear stale state:

Remove the failing connection, sign out/in, and recreate it.

If still failing:

Capture Conversation ID and raise a support ticket—500 errors often indicate backend connector issues.

Tip: API Key works because it bypasses OAuth; Entra ID requires full RBAC + consent flow. If you need immediate continuity, stick with API Key until Microsoft resolves the Entra ID connector bug.

Was this reply helpful? Yes No