This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(233.6, 90%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
Our STT services is showing some latency issues for a given API Key. When we updated to new API Keys, the service appears to work fine, but how can we prevent this? Is there a way to find out if STT service has operational issues?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(166.4, 22%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESC%3C/text%3E%3C/svg%3E)
Hello @Srini,
If the Azure resource is publicly accessible, such as a Speech Service endpoint using an API key, there is a potential risk of unauthorized access. This can lead to increased API usage, which might exceed rate limits or cause throttling, resulting in slower response times. These delays can also stem from server-side issues or service interruptions.
To mitigate the issue here are some steps to follow,
Periodically rotating API keys helps mitigate the risk of exposed or misused credentials. This is a basic security hygiene practice.
Store API keys in Azure Key Vault by assigning the Key Vault Administrator role for management and Key Vault Secrets User role for secure, controlled access.
Reference - Learn how to use Azure Key Vault.
Use the Metrics tab of your resource to identify unusual spikes or patterns in API usage that may indicate misuse or overconsumption.
Configure your Speech Service or resource to be accessible only within a VNet. Use Point-to-Site (P2S) or Site-to-Site (S2S) VPN to access securely.
Check Azure Service Health or the Azure Status page for backend issues. Use the Metrics tab to view SLA availability and latency over time.
Enable Diagnostic Settings on the resource to send logs to Log Analytics, Storage Account, or Event Hub. Diagnostic settings in Azure Monitor
Use Log Analytics Workspace to create custom queries and alerts based on specific metrics or activity logs.
I Hope this helps. Do let me know if you have any further queries.
Thank you!
Following up to see if the above suggestion was helpful. And, if you have any further query do let us know.
Thank you!
I hope the latency issue in East US has been resolved for you. If you're still experiencing any problems or need further assistance, please don't hesitate to let us know.
Thank you!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(6.4, 61%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
Hi @Srini,
I believe this issue was related to the East US region outage that occurred recently. The issue has now been mitigated, and services should be back to normal. Please let me know, if you are still facing any delays. You can refer to the official outage update here: https://status.azure.com/en-us/status/history/.
Thank you.