A Bing service that gives you enhanced search details from billions of web documents.
The requests go to the Bing Speech host shown in the error, not a supported Azure Speech REST endpoint for an Azure resource. A 400 from its synthesis path, or a service-unavailable page from its consumer voices path, does not establish an Azure Speech resource outage.
Create or select a Speech resource, note its region, and replace the Bing host with the matching regional text-to-speech endpoint. Use /cognitiveservices/v1 for synthesis and /cognitiveservices/voices/list for voice discovery. Send the resource key in Ocp-Apim-Subscription-Key, or use a bearer token scoped to the same endpoint. Synthesis requires Content-Type: application/ssml+xml, X-Microsoft-OutputFormat, User-Agent, and valid SSML.
Test voice discovery first, then submit minimal SSML. A 401 indicates invalid authorization, often a key, token, endpoint, or region mismatch; for a 400, recheck required parameters, headers, and SSML. If the application hard-codes the Bing consumer host, update the integration; Azure configuration cannot redirect requests sent elsewhere.