Azure bot services down in India

Hi Cloud Admin,

Based on what is reported in this thread and by other users, this looks like a temporary Azure Bot Service platform issue, not a problem with your bot code or configuration.

Multiple users have reported the same behavior at the same time, including errors like redirect responses and 401 failures from the Microsoft.BotService resource provider. This has been seen not only in India but also in other regions such as Europe, which usually indicates a backend service issue rather than anything specific to one subscription or bot setup.

When this happens, a few quick checks can help confirm it is a platform-side issue.

First, check the Azure Status and Azure Service Health pages. Not every Bot Service issue shows up immediately on the public status page, but it is still the best place to see if there is any ongoing or recently resolved incident impacting Azure services in your region. [azure.stat....microsoft]

Second, open your Bot Service resource in the Azure portal and try basic actions like loading the configuration blade or accessing channels. If the portal itself is slow or failing for Bot Service, that further confirms the issue is on the service side and not related to your bot logic.

Third, avoid making changes while the issue is happening. Redeploying the bot, regenerating keys, or changing authentication usually does not fix service outages and can create extra confusion once the platform recovers.

In similar past cases, users reported that Bot Service started working again once the backend issue was resolved, without any changes needed to the bot itself.

For general understanding of how Azure Bot Service normally works and what to expect during outages, this overview page is helpful. https://dotnet.territoriali.olinfo.it/azure/bot-service/bot-service-overview

If you are seeing the same errors as others and portal operations are also affected, the best approach is to wait for the platform to stabilize and retry later. Most community members in similar situations confirmed their bots resumed normal operation once the service issue was fixed.

Hope this helps and avoids unnecessary troubleshooting on your side.

Thankyou!