Cost to build a Microsoft Teams app

Building a Microsoft Teams app in 2026 typically costs $8,000 to $200,000+ depending on scope. A simple notification bot lands at $8,000 to $20,000, a full-featured app with tabs and messaging extensions sits at $25,000 to $70,000, and an enterprise-grade multi-tenant app with AAD SSO, Graph API integrations, and Microsoft Store distribution runs $80,000 to $200,000 or more.

The price spread is wide because "Teams app" covers everything from a Friday standup reminder bot to a HIPAA-bound clinical workflow surface used by 40,000 nurses. The three biggest cost drivers are the surface count (bot, tab, messaging extension, meeting extension), tenancy model (single-tenant vs multi-tenant), and whether you publish to the Microsoft Teams Store or stay sideloaded inside a single org.

What actually counts as a "Teams app"

Microsoft uses one app manifest for what are really four different products glued together. You can ship any subset:

• Bots. Conversational surface built on the Bot Framework SDK. Pings users in 1:1 chats, group chats, or channels. Reactive (responds to commands) or proactive (notifies on events).
• Tabs. An iframe that hosts a web app inside Teams. Personal tabs (just for the user) or channel tabs (shared with the team).
• Messaging extensions. The shortcut menu in the message compose box. Lets users search your data, paste rich cards, or trigger actions without leaving Teams.
• Meeting extensions. In-meeting side panels, stage view, or pre-meeting tabs. Useful for polls, transcripts, agenda apps.

A bot-only app skips the React tab build entirely. A tab-only app skips Bot Framework. Most "full" Teams apps ship a bot plus one tab plus a messaging extension, which is where the $25,000 to $70,000 range lives.

Cost breakdown by approach

Approach	Cost	Timeline	Pros	Cons
US full-time hire	$160,000–$220,000/yr loaded	8–14 weeks to ship v1	Deep ownership, knows your domain	Hard to find Teams + Graph API experience; long ramp
Microsoft Partner agency	$40,000–$180,000 fixed bid	10–20 weeks	Knows the cert process, has Store-published apps	High markup; change orders are expensive
Freelancer (Upwork/Toptal)	$50–$180/hr	6–14 weeks, variable	Cheap for prototypes	Few have shipped a Store-listed app; AAD config slows them down
Toptal	$80–$180/hr	1–2 weeks to match	Pre-vetted, US-friendly hours	Premium pricing; weekly minimums
Cadence	$500–$2,000/wk	48-hour trial, then ship	Every engineer is AI-native (Cursor, Claude Code, Copilot daily), weekly billing, replace any week	Less suited to fixed-bid enterprise procurement

A Microsoft Partner agency wins when you need a logo-stamped "Microsoft AppSource certified" engagement and your buyer is procurement. Everyone else is paying for the certification, not the code.

The three pricing tiers, in detail

Tier 1: Simple notification bot ($8,000 to $20,000)

The MVP shape: a bot that posts into a channel when something happens in your SaaS. Linear ticket assigned, Stripe charge failed, PagerDuty incident triggered. Maybe a couple of slash commands (/status, /help).

What you pay for:

• Bot Framework SDK scaffolding (Node or .NET). Microsoft's Yeoman generator or the Teams Toolkit VS Code extension scaffold a working bot in under an hour.
• A webhook endpoint hosted on Azure Functions, AWS Lambda, or Render. Roughly $5 to $40/month.
• Bot registration in Azure (Azure Bot Service is $0.50 per 1,000 messages on the standard channel).
• An app manifest, two icons (192×192 color, 32×32 outline), and a sideload-ready zip.
• A single-tenant AAD app registration for the team using it.

You can ship this in two to three weeks with a mid-tier engineer at $1,000/week, plus maybe a week of senior review for the AAD config. Total: $3,000 to $5,000 in engineer time, plus $2,000 to $10,000 in tooling, contingency, and a small design polish pass. Real-world projects land around $12,000 when you include a basic admin dashboard outside of Teams.

The most common gotcha at this tier: teams underestimate how much time goes into adaptive card design. A poorly laid out card is the only thing the user ever sees. Budget 20% of the spend on card UX, not as an afterthought.

Tier 2: Full app with tabs and messaging extensions ($25,000 to $70,000)

This is the typical "we want a real Teams presence" build. Bot + personal tab + channel tab + messaging extension, often hooked to your existing SaaS via OAuth or API key.

What changes from tier 1:

• You're now hosting a React or Next.js tab app. The tab loads inside an iframe, which means CSP headers, theme detection (light, dark, high-contrast), and SSO via the Teams JS SDK.
• Microsoft Teams Toolkit becomes mandatory rather than optional. It handles AAD registration, env switching, and local debugging via the dev tunnel. Without it you're hand-rolling ngrok and AAD apps, which adds two to three weeks.
• The messaging extension needs a search command, an action command, or both. Each has its own auth flow and rate-limit story.
• Adaptive Cards 1.5+ for rich responses. You'll spend real time on the Card Designer at adaptivecards.io and accept that the in-Teams render is never identical to the preview.
• Storage. Microsoft recommends Azure Table Storage or Cosmos DB for low-latency state; in practice teams use Postgres on Render or Supabase and pay the small extra latency cost.

A senior engineer at $1,500/week, working four to eight weeks, gets you the core. Add a mid engineer for the tab UI and you're looking at $15,000 to $30,000 in engineer cost, plus another $10,000 to $40,000 for design, QA across desktop / web / mobile clients, and the inevitable "the meeting extension behaves differently on iPad" debugging.

Teams desktop, Teams web, Teams mobile (iOS), and Teams mobile (Android) are four separate render targets with subtle differences in iframe behavior. Test on all four. Most agencies skip mobile QA and the client finds the bugs in production.

If you're sizing a similar internal-tool budget, our breakdown of HubSpot integration costs tracks the same shape: the integration itself is cheap, the surface polish and auth edge cases are where the money goes.

Tier 3: Enterprise multi-tenant app with AAD SSO and Graph API ($80,000 to $200,000+)

Now you're publishing to the Microsoft Teams Store (formerly AppSource), supporting hundreds or thousands of tenants, and reading from Microsoft Graph (calendars, mail, files, presence, org chart).

What lives at this tier:

• Multi-tenant AAD app registration. Admin consent flow, per-tenant token storage, token refresh, tenant-isolated data partitioning. This alone is two to four weeks of senior engineering done right.
• Graph API integrations. Each Graph scope (Calendars.Read, Mail.Send, Files.ReadWrite.All, Sites.Manage.All) needs admin consent, justification text for the Store reviewer, and a careful audit log. Some scopes require Microsoft 365 certification on top of Store review.
• App submission to Microsoft Partner Center. The Store review process takes roughly five to ten business days for a first submission and rejects on small issues: missing privacy policy, generic icons, unclear data handling. Plan for two to three rounds.
• Microsoft 365 certification (optional but common for enterprise buyers). Adds another four to eight weeks of security review, penetration test evidence, and data flow diagrams. Worth doing if your enterprise sales motion needs it.
• Compliance posture. SOC 2, GDPR data residency, and often FedRAMP or HIPAA depending on the buyer. Touches your hosting choice, your logging stack, and your SLA.
• Webhook lifecycle for Graph change notifications. Subscriptions expire every 4,230 minutes (about 70 hours). You'll write a renewal worker.

A two-engineer team (one lead at $2,000/week, one senior at $1,500/week) shipping over 12 to 20 weeks lands the build at $42,000 to $70,000 in engineer cost. Add design, QA, security review, the cert audit, and contingency, and the all-in number sits at $80,000 to $200,000+.

The single biggest cost spike at this tier is AAD. Multi-tenant consent prompts confuse admins, tokens expire in unexpected ways, and the admin consent endpoint behaves differently for delegated vs application permissions. Budget a full sprint for AAD edge cases alone.

For broader context on enterprise-grade SaaS economics, the same scope cliff shows up in our accounting SaaS cost breakdown: the first $50,000 builds the product, the next $150,000 makes it sellable to a regulated buyer.

Feature-by-feature cost map

Feature	Build cost	SaaS alternative
Bot scaffolding (Bot Framework SDK)	$1,500–$4,000	N/A, you build it
Adaptive card design (10 cards)	$2,000–$6,000	Card Designer is free
Tab UI (React, 3 routes)	$4,000–$12,000	N/A
Messaging extension (search)	$3,000–$8,000	N/A
Single-tenant AAD SSO	$1,500–$4,000	N/A
Multi-tenant AAD SSO + admin consent	$6,000–$18,000	N/A
Graph API integration (per scope)	$2,000–$8,000	N/A
Microsoft Store submission + rework	$3,000–$10,000	N/A
Microsoft 365 certification	$15,000–$40,000	N/A
Hosting (Azure or Render)	$40–$400/month	Same
Bot messages (Azure Bot Service)	$0.50 per 1,000 messages	Same

Authentication is the line item people underprice. A "just add login" ticket in Teams means: AAD app registration, Teams SSO token exchange, on-behalf-of flow to call Graph, fallback for guest users, and clear handling of consent revocation. That's a sprint of work, not an afternoon.

How to cut cost without cutting quality

Five moves that have shipped real Teams apps for less:

• Skip surfaces you don't need. Most Teams apps don't need a meeting extension or a channel tab. A bot plus a personal tab covers 80% of use cases at half the cost.
• Use Teams Toolkit from day one. It handles AAD, dev tunnels, manifest validation, and environment swapping. Teams that hand-roll this lose two to three weeks.
• Buy the auth. Don't write multi-tenant token storage from scratch. Use the MSAL libraries, accept their state model, and don't fight it.
• Sideload first, Store second. Validate the product inside one or two friendly tenants for three months before paying the certification tax. The Store unlocks distribution, not validation.
• Use AI-native engineers. Every engineer on Cadence ships with Cursor, Claude Code, and Copilot in their daily flow, vetted on prompt-as-spec discipline before they unlock bookings. Bot Framework boilerplate and adaptive card JSON are exactly the pattern-matching work that AI tooling collapses from days to hours.

If you're weighing build vs buy for adjacent integration work, our piece on referral program cost trade-offs walks the same logic: pick the path that doesn't need a rewrite later, even if it costs more up front.

The fastest path from idea to shipped Teams app

A three-step plan that works for most companies:

1. Spec the surfaces. Write a one-pager: which of bot / tab / messaging extension / meeting extension you actually need, single-tenant or multi-tenant, and which Graph scopes (if any). This document is the spec your engineer codes against.
2. Build the MVP in your own tenant first. Use Teams Toolkit, sideload into your own Teams org, get five real users actively using it. Three weeks for tier 1, eight to twelve weeks for tier 2.
3. Decide on Store distribution last. If sideloaded usage proves the product, then pay the certification and submission cost. If not, kill it before you spend $30,000 on cert.

If you don't already have a Teams-fluent engineer in your team, the fastest path is booking a senior on Cadence at $1,500/week with a 48-hour free trial. The Bot Framework, Teams Toolkit, and Graph API surface area is exactly the kind of pattern-dense work where an AI-native engineer compresses the timeline by 40 to 60%.

For pure cost comparison against other common integration builds, the Calendly clone build breakdown is a useful reference point: same kind of multi-surface, multi-auth, multi-platform cost stack.

Try Cadence for your Teams app build. Book a senior or lead engineer in 2 minutes, use them for 48 hours free, and replace them any week if the fit isn't right. We've placed engineers on Teams app builds shipping in three weeks instead of three months.

FAQ

How long does it take to build a Microsoft Teams app?

A simple notification bot ships in two to three weeks. A full app with tabs and messaging extensions takes eight to twelve weeks. An enterprise multi-tenant app with Microsoft Store certification takes four to seven months, mostly because of AAD edge cases and the Store review cycle (five to ten business days per submission round, and most apps need two to three rounds).

Do I need to publish to the Microsoft Teams Store?

No. You can sideload an app into a single tenant indefinitely. Store publication unlocks distribution to other tenants and lets you run a paid app via Microsoft commercial marketplace, but adds four to twelve weeks of submission work. Sideload first to validate the product, then decide on Store later.

What tech stack should I use?

Microsoft's official stack is TypeScript + Node.js for bots, React + TypeScript for tabs, and Teams Toolkit for VS Code as the build / debug harness. The Bot Framework SDK ships in Node, .NET, and Python; Node has the largest community and the most up-to-date samples. For hosting, Azure App Service or Azure Functions are the path of least friction with AAD, but Render, Vercel, or AWS Lambda work fine if you handle the AAD config yourself.

How much does Microsoft 365 certification cost?

The certification itself is free, but the engineering work to prepare for it (security documentation, penetration test evidence, data flow diagrams, and remediation of findings) usually adds $15,000 to $40,000 in engineer time and four to eight weeks of calendar time. It's worth doing if you sell into regulated enterprises; skip it for SMB-only distribution.

Can I build a Teams app without learning AAD?

Not really. Even a single-tenant bot needs an AAD app registration and a bot registration in Azure. The good news: Teams Toolkit handles 80% of the AAD config for you in dev, and the remaining 20% (admin consent, scope definitions, redirect URIs) is a one-time setup. Multi-tenant apps are a different conversation: budget a full sprint for AAD if you've never shipped a multi-tenant app before.