What a Teams App Actually Is
A Microsoft Teams app — sometimes called a Teams add-in — extends Teams with one or more building blocks: tabs (web pages embedded in a channel or chat), bots (conversational assistants built on the Bot Framework), message extensions (actions and search you trigger from the compose box), and meeting apps (panels that run inside a Teams meeting). Most Teams apps are just web apps wrapped in a Teams manifest, which means you can often reuse the same front end you already have. The pieces that make a Teams app feel native are single sign-on with the user's Microsoft 365 account and Microsoft Graph access to their files, calendar, and chats.
Key Takeaways
Four building blocks
Tabs, bots, message extensions, and meeting apps — mix and match to fit the workflow.
Built on web tech + Bot Framework
Tabs are web apps; bots use the Microsoft Bot Framework. Both are reusable across surfaces.
Teams Toolkit speeds setup
Microsoft's Teams Toolkit scaffolds the manifest, auth, and hosting so you skip boilerplate.
SSO with Entra ID
Users sign in with the Microsoft 365 account they already use — no separate login.
Microsoft Graph integration
Read and act on calendar, files, chats, and org data through one API.
Org or store distribution
Publish to your organization's app catalog or list publicly on the Teams Store.
Choosing the Right Teams App Type and Architecture
Pick the building block by the job. Use a tab when people need a full screen to work in — a dashboard, a form, an embedded product view. Use a bot when the interaction is conversational or event-driven, like approvals, reminders, or notifications pushed into a channel. Use a message extension when users want to pull something into a conversation, such as inserting a record or searching your system without leaving the chat. Use a meeting app when the value happens live during a call — agendas, polls, note capture.
Underneath, the architecture is consistent: a web/back-end you host, an Entra ID app registration for authentication, single sign-on to identify the user, and Microsoft Graph for their Microsoft 365 data. Governance matters too — plan how the app gets approved, who can install it, and which permissions admins must consent to.
Build the web app once, surface it everywhere
Design your front end so the same screens can run as a Teams tab and as an Office add-in task pane. With a little planning around auth and layout, one codebase can serve Teams, Outlook, and the web — which roughly halves the cost of being everywhere your users are.
Teams apps meet users where they already spend their day. Start with the single building block that removes the most friction, wire up SSO and Graph cleanly, and expand once adoption proves the value.
Whether you need a tab, a bot, or a full multi-surface Teams app with SSO and Microsoft Graph, our team builds and ships custom Teams apps end to end. See our page to learn more.Office Add-in development services
Microsoft Teams app building blocks compared
| Type | Best for | Requires Bot Framework |
|---|---|---|
| Tab | Full-screen dashboards, forms, embedded apps | No |
| Bot | Conversational flows, approvals, notifications | Yes |
| Message extension | Search and insert actions from the compose box | Yes |
| Meeting app | Live agendas, polls, note capture during calls | No |
Frequently asked questions
What is a Microsoft Teams app?
A Teams app extends Microsoft Teams with custom functionality — tabs (embedded web pages), bots (conversational assistants), message extensions (compose-box actions), and meeting apps. Most are standard web apps wrapped in a Teams manifest.
How does authentication work in a Teams app?
Teams apps use single sign-on via Microsoft Entra ID (Azure AD), so users are automatically identified with the Microsoft 365 account they are already signed into. Your back-end exchanges that token for Microsoft Graph access to their data.
Can a Teams app and an Office add-in share the same front-end code?
Yes. With careful planning around layout and authentication, the same web app can run as a Teams tab and as an Office add-in task pane, letting one codebase reach multiple Microsoft 365 surfaces.
How do I deploy a Teams app to my organization?
Publish it to your organization's Teams app catalog through the Teams admin center — no Microsoft store review needed. For public distribution, submit to the Teams Store, which has its own review process.
Meet users where they already work
Microsoft Teams app development turns Teams from a chat tool into a place where your workflows actually run. Tabs, bots, and message extensions each solve a different problem — choose deliberately. Orfys builds and ships custom Teams apps with SSO and Graph integration.