An Azure service that provides a hybrid, multi-cloud management platform for APIs.
The existing evidence cannot distinguish resource throttling from temporary backend capacity, so preserve the failed-response metadata, correlate Azure Monitor and Service Health for the exact UTC windows, and open a Speech resource support request without resubmitting the recording.
What the current evidence establishes
- Low usage does not exclude a service-capacity 429. Fast transcription and batch transcription share an S0 limit of 600 requests per minute, but Microsoft documents that Speech can return 429 while a workload remains within quota when autoscaling has not yet supplied enough compute. Increasing quota does not resolve that condition.^1^
- One Total Call plus one Blocked Call identifies the rejected request, not its underlying cause.
BlockedCallsmeans calls that exceeded a rate or quota limit. Its available dimensions areApiName,OperationName,Region, andRatelimitKey.^2^ - UK South supports fast transcription. The regional availability table explicitly marks
uksouthas supported.^3^ - The published material does not identify an Albanian-specific fast-transcription capacity restriction in UK South. Therefore, the repeated
sq-ALpattern is useful evidence for Microsoft Support, but it does not by itself prove locale-specific saturation. - There is a prior public report matching S0, UK South,
sq-AL, and isolated 429 responses, but no corresponding publicly confirmed regional incident was identified.^4^
Checks that require no new transcription
- Break down the existing metrics
- Azure portal → Speech resource → Monitoring → Metrics.
- Set each affected UTC interval narrowly around the request.
- Add Blocked Calls, Total Calls, Client Errors, and Server Errors where available.
- For
Blocked Calls, use Apply splitting for:-
ApiName -
OperationName -
Region -
RatelimitKey
-
- Export or capture the chart and dimension values. Metric filtering and splitting are intended to identify which segment contributed to a result.^5^
- Review subscription-specific health history
- Azure portal → Service Health → Service issues.
- Filter for Azure AI/Speech, UK South, and the affected subscription.
- Check both active and resolved events covering:
- 19 and 26 October 2026
- 8 and 12 November 2026
- Record any tracking ID, UTC start/end time, impacted region/resource, and issue updates.
- Check Resource Health
- Speech resource → Resource health → Health history.
- Review the same UTC windows.
- Review previously enabled diagnostic logs
- If a diagnostic setting was already active, query or export the records for the exact timestamps.
-
Microsoft.CognitiveServices/accountssupportsRequestResponse,Audit, andTracelog categories.^8^ - If diagnostics were not enabled at the time, enabling them now will help future failures but will not reconstruct old request records.
- Preserve client-side evidence already captured
- Exact UTC timestamp, including milliseconds and timezone.
- HTTP status, complete response body, and all response-header names and values except secrets.
- Resource name and resource ID, region, pricing tier, operation, API version, locale, audio size/duration/format, and authentication method.
- Application-generated trace or correlation ID, if one was attached.
- Evidence that no concurrent fast or batch transcription calls occurred.
Escalation
From the Speech resource, select Support + Troubleshooting and create a technical support request. Include the four failure timestamps, metric exports with dimensions, full sanitized 429 responses, Service/Resource Health findings, and the successful English request as a control case. Azure Support can perform service-side correlation that customer-visible metrics cannot.^9^
Ask Support to determine explicitly whether each request was rejected by:
- the resource’s shared fast/batch request-rate quota;
- an internal
RatelimitKey; - Speech autoscaling or regional backend capacity;
- model/locale-specific capacity for
sq-ALin UK South.
No warm-up call or unrestricted retry is required for this investigation. For future authorised attempts, Microsoft recommends bounded retries for 429, but that is an operational mitigation rather than proof of the cause.^10^
References
- Quotas and Limits for Azure Speech - Foundry Tools | Microsoft Learn
- Supported metrics for Microsoft.CognitiveServices/accounts
- Supported regions for Azure Speech
- Azure Speech Fast Transcription repeatedly returns HTTP 429 despite very low usage — UK South, S0 - Microsoft Q&A
- Analyze metrics with Azure Monitor metrics explorer
- Azure Service Health FAQ
- Resource Health overview
- Supported logs for Microsoft.CognitiveServices/accounts
- Create an Azure support request
- Use the fast transcription API - Speech service - Foundry Tools | Microsoft Learn