Teams error Authorization_RequestDenied: Authorization request denied when creating a bot
Last verified against Microsoft Learn - Status codes from bot conversational APIs
Authorization_RequestDeniedWhat error Authorization_RequestDenied means
You never got as far as running a bot: creating the Azure Bot resource failed with Authorization_RequestDenied. Microsoft's general troubleshooting FAQ explains that "Permission to create Azure AI Bot Service bots are managed through the Microsoft Entra ID portal. If permissions aren't properly configured in the Microsoft Entra ID admin center, users will get the Authorization_RequestDenied exception when trying to create a bot service."
Creating a bot creates or uses a Microsoft Entra app registration, so the person creating it needs the right to register applications in the directory. Two directory settings decide that. Under App registrations, Users can register applications must be Yes. And if you are a guest in the directory, guest permissions limit what you can do unless an administrator relaxes them. The FAQ's first diagnostic step is to check whether your user type in Microsoft Entra ID is Guest.
This is directory policy, not a bug in your template or code. Retrying the same deployment won't change the outcome; either the settings change, or someone who already has the rights creates the registration and gives you the app ID.
What it looks like
Code: Authorization_RequestDenied
// Raised when creating an Azure AI Bot Service resource without
// permission to register applications in Microsoft Entra IDWhy it happens
- The directory setting Users can register applications is No.
- You are a guest user in the directory, and guest permissions are limited.
- Your organization restricts app registration to specific admin roles.
- You are deploying into a different directory than your usual one, where you have fewer rights.
How to fix Teams error Authorization_RequestDenied
- 1In the Azure portal, check your User type under Microsoft Entra ID > Users; if it says Guest, that is likely the cause.
- 2Ask a directory administrator to set Users can register applications to Yes, or to grant you a role that can register applications.
- 3If you are a guest, ask the administrator to adjust guest user permissions, or have a member account create the bot.
- 4Alternatively, have an admin create the app registration and supply its app ID and credentials when you create the Azure Bot.
How to stop it recurring
Agree with your directory administrators on who creates bot app registrations before the project starts, and document the app IDs and owners. In locked-down tenants, a pre-created app registration handed to developers avoids this error entirely and keeps app registration rights narrow.
Official reference: Microsoft Learn - Status codes from bot conversational APIs. See all Teams error codes or the Teams limits and quotas.
Related codes
- 401 BotNotRegistered: BotNotRegistered - no registration foundNo registration found for this agent.
- 401 Unauthorized (invalid app ID / password): Invalid Microsoft App ID or passwordAADSTS7000215: Invalid client secret provided.
- 403 NotEnoughPermissions: NotEnoughPermissions - operation requires rights the bot lacks*scenario specific
Error Authorization_RequestDenied - quick answers
What does Teams error Authorization_RequestDenied mean?
You never got as far as running a bot: creating the Azure Bot resource failed with Authorization_RequestDenied . Microsoft's general troubleshooting FAQ explains that "Permission to create Azure AI Bot Service bots are managed through the Microsoft Entra ID portal.
How do I fix Teams error Authorization_RequestDenied?
1. In the Azure portal, check your User type under Microsoft Entra ID > Users; if it says Guest, that is likely the cause. 2. Ask a directory administrator to set Users can register applications to Yes, or to grant you a role that can register applications. 3. If you are a guest, ask the administrator to adjust guest user permissions, or have a member account create the bot. 4. Alternatively, have an admin create the app registration and supply its app ID and credentials…
Stop debugging Teams by hand
Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.