Action failed due to a bad request to Cognitive Services. Please check your input parameters

Hi Venkata Satya Suneel Kumar Sikhakollu,
This error usually indicates a misunderstanding or invalid parameters that are being sent from ACS at the concluding point of Azure Cognitive Services, especially speech services

Verify speech service sector and closing points, you are using:

var cognitiveServiceEndpoint = "https://eastus2.api.cognitive.microsoft.com/";

and make sure that: Speech Services Resource is actually posted in eastus2 - which your screenshot confirms

The endpoint matches, shown in the speech services Azure portal.

The endpoint URL does not have any followed slashes or type.
Get Speech endpoint from Azure

You mention the "cognitive service user" role. This is correct. However, make sure that the role is assigned on the correct scope, which should be Speech service resources(speech-analysis-demo)

Role: Cognitive services user

Principal: Managed Identity of Your ACS Resource

That error message suggests invalid or incomplete recognize settings. The request passed request to include the CallAutomationClient.CreateRecognizeSpeechOptions() is involved: cognitiveServicesEndpoint (Correct)

locale (e.g., "en-US")

speechConfig or other necessary settings
sample example:

var recognizeOptions = new CallMediaRecognizeSpeechOptions(targetParticipant, "en-US")
{
    CognitiveServicesEndpoint = new Uri(cognitiveServiceEndpoint),
    // Include any required configuration for silence detection, etc.
};

If there are network restrictions in speech services, your ACS may be blocked. confirm:

Speech Resource allows traffic from reliable Microsoft services or configures the private closing point correctly if necessary.
Connect Azure Communication Services with Azure AI services
if you have any further concerns or queries, please feel free to reach out to us.

Hi @Alekhya Vaddepally

I tried all above ways but still it didn't work for me. Please find the below screenshots for reference

Speech Endpoint:

Speech IAM - Cognitive Services User:

I verified with speech endpoint and key its working individual but not with ACS. Am i missing any. Please let me know if i want to provide any additional information to fix it.

Hi Venkata Satya Suneel Kumar Sikhakollu,
The cause of 8565 error in this context is the missing or wrong managed identity linkage between ACS and speech service.

When using ACS with cognitive services, ACS uses its managed identity to certify. The role of cognitive service user should be assigned to ACS-managed identity-not on the user or app-speech resource.

Your speech resource is in the East US2. Ensure that your ACS resource is also deployed in an area that supports this integration. Some mismatched authentications in areas may cause failures.

check you are setting the cognitiveServicesEndpoint correctly in your code, like below example:

var callOptions = new RecognizeOptions
{
    CognitiveServicesEndpoint = new Uri("https://eastus2.api.cognitive.microsoft.com/")
};

If there is any mismatch in syntax or endpoint formatting, the request may fail quietly.
if you have any further concerns or queries, please feel free to reach out to us.

Hi @Alekhya Vaddepally

No luck same issue, i already done this all earlier only. Still unable to connect speech to services. I have removed EastUS2 and created new speech service with EastUS but same issue. ACS is deployed in Global region only we can't choose EastUS region. I'm able to connect Speech Service independently without any issue. From ACS its unable to connect.

Is it possible to connect with privately to troubleshoot this?

Thanks & Regards,

Suneel Kumar SVS.

Hi Venkata Satya Suneel Kumar Sikhakollu,

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.