"Connection Error" Issue During HTTP Calls to Custom Neural Voice Endpoint

Question

Hello, We are experiencing an issue with our Azure Speech Studio configuration, specifically with the endpoint of our Custom Neural Voice. We are using an HTTP request via curl with all parameters properly configured (API keys, region, and validated endpoint). However, at random intervals and without apparent reason, we receive a "Connection Error" in response to our calls. Details:

• The issue appears to be random, and we have verified the following:
  • API keys are valid.
    • The region matches the one configured in Azure.
      • Logs and log storage for the Azure Speech resource are enabled.
      • Despite these verifications, we are unable to determine whether the issue originates on our side or with the Azure endpoint.

Questions for Support:

1. Additional Endpoints for Diagnostics:
   • Are there other endpoints or tools we can use to precisely diagnose requests made to our Custom Neural Voice service ?
     • Is there a way to directly trace requests in Azure to identify the exact moment when the error occurred ?
     1. Detailed Logs:
        • Could you check if specific errors or limitations (e.g., quotas, timeouts, etc.) were logged for our resource at the time the error occurred ?
          • Is there a dedicated endpoint for health or connectivity checks for the Custom Neural Voice service ?
          1. Real-Time Support:
             • Is it possible to obtain real-time assistance to monitor the usage and responses of our Custom Neural Voice endpoint ?

We appreciate your help in identifying the source of the issue and in preventing such connection errors in the future. Additional Information:

• Azure Speech Resource Name: Bayard-cognitive-services
• Region: westus2
• Specific time when the error occurred: 10 January 2025, 22:35 (FR Paris time)

Best regards

Answer 1

Try to enable diagnostic settings on your Azure Speech resource to log all incoming requests and their status codes. These logs can be routed to:

• Azure Monitor Logs
• Storage Accounts
• Event Hubs These logs can provide insights into when and why requests failed.

Azure Cognitive Services don’t explicitly provide a "health check" endpoint for Custom Neural Voice. However, you can test basic connectivity using the standard Speech-to-Text or Text-to-Speech endpoints as a proxy diagnostic.

You can always open a support request in the Azure Portal and include:

• Request IDs
• UTC timestamps of errors
• Resource details (name and region)
• Logs and repro steps.