🔥Building a Teams Bot with AI Capabilities - Part 2 - Register and Testing in Azure w/ Teams Developer Portal🔥

aka, json juggling, manifest mangling, error exasperation

This blog series focuses on presenting complex DevOps projects as simple and approachable via plain language and lots of pictures. You can do it!

These articles are supported by readers, please consider subscribing to support me writing more of these articles <3 :)

This article is part of a series of articles, because 1 article would be absolutely massive.

• Part 1: Create an Azure Bot and App Registration

• Part 2 (this article!): Register Bot in Teams with Teams Developer Portal

Hey all!

In the last article we covered how to register a Teams Bot resource in Azure, and link it to an App Registration, which grants it permissions and the ability to look up information. You would think, since you’ve registered a Teams Bot resource, and linked it to the Teams “channel”, that your Bot is now present in your Teams app. You’d be wrong.

Instead, there’s one more (surprisingly complex, poorly documented) step.

Testing your Bot in Teams, and then submitting it to your Org for use!

There’s a few different ways to do this - via the Teams App, or via the Teams Developer Portal. Regardless, we’re going to need a Manifest .

If you don’t care about reading how we built it, and would rather just read the code, it’s open-sourced here. Happy building!

https://github.com/KyMidd/TeamsAIBot