Share via

Teams bot not receiving messages when using a self-hosted Bot Framework without Azure Bot resource

Callihan Memory 75 Reputation points
2026-01-13T10:01:15.8566667+00:00

I’ve registered an application in Microsoft Entra ID and built a bot using the Bot Framework SDK (botbuilder). The bot is hosted on my own infrastructure and authenticates successfully using the App ID and client secret from Entra ID. I did not provision an Azure Bot resource.

The Teams app manifest is correctly configured with personal scope only, and the app installs in Microsoft Teams without errors. The bot service is reachable, and authentication appears to be functioning as expected.

Despite this, the bot never receives incoming activities from Teams, no messages or events are delivered to the configured endpoint.

Is it possible to configure a Teams messaging endpoint (for example, /api/messages) to receive messages without creating an Azure Bot resource

Microsoft Teams | Development
Microsoft Teams | Development

Building, integrating, or customizing apps and workflows within Microsoft Teams using developer tools and APIs

0 comments No comments

Answer accepted by question author

Steven-N 25,305 Reputation points Microsoft External Staff Moderator
2026-01-13T11:38:59.4066667+00:00

Hi Callihan Memory

Thank you for reaching out to Microsoft Q&A forum

Regarding you question: Is it possible to configure a Teams messaging endpoint (for example, /api/messages) to receive messages without creating an Azure Bot resource?

Based on my research, you cannot bypass Azure Bot registration. Microsoft Teams requires a bot to be registered with the Azure Bot Framework Service (via an Azure Bot resource or a Bot Channel Registration) in order to deliver messages to your bot’s endpoint. Simply having a Teams app manifest with your bot’s App ID is not enough. The Teams client routes all bot messages through the Bot Framework Service (hosted in Azure), which uses the bot’s registration to look up the correct HTTPS endpoint for your bot.

As far as I know, this registeration is necessary, because the Teams app manifest does not contain your bot’s actual HTTP address, it only references the bot’s App ID. So, when a user sends a message to your bot in Teams, Teams contacts the Bot Framework Service (using the App ID) to forward the message.

That said, if your bot isn’t registered there, the service doesn’t know where to send the request. In other words, registering the bot with Azure (Bot Framework) is mandatory for the Teams channel to function. This is by design for security and routing purposes

In case you are finding the workaround for this: Unfortunately, there is no supported workaround to get a Teams bot working without some form of Bot Framework registration. In the past, developers could register a bot through the legacy Bot Framework portal or Teams App Studio (which behind-the-scenes still created an Azure Bot registration). Today, you must use the Azure Bot Service for any production Teams bot integration.

For your information: https://www.neilwithdata.com/teams-bot-without-azure

Note: Microsoft is providing this information as a convenience to you. These sites are not controlled by Microsoft, and Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please ensure that you fully understand the risks before using any suggestions from the above link.

Best regards


If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".     

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread. 

Was this answer helpful?

1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.