Running Microsoft Teams?

Teams bot silent or Graph webhooks expired? We bring it back.

Microsoft Teams is a serious platform for anyone writing bots, tabs or Graph integrations against it, and a frustrating one for anyone who inherited an app built two tenant revisions ago. We work through the Bot Framework, the Graph API, the manifest and the admin center until the message arrives in the right channel again.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

teams-bot.log

still broken

What it is

Microsoft Teams at a glance

Microsoft Teams is Microsoft's collaboration suite, first released in 2017 as the successor to Skype for Business, and now the default chat and meetings tool across most organizations that use Microsoft 365. It bundles chat, calls, meetings, channels, shared files through SharePoint and OneDrive, and a developer platform built on Azure Bot Service, the Microsoft Graph and the Teams JS SDK.

The platform is powerful and the complexity is proportionate. A Teams app can combine a bot, a messaging extension, tabs, meeting apps, Adaptive Cards and Graph subscriptions, each with its own identity model, consent flow and admin policy. Most integrations do not break because the code is wrong; they break because the tenant changed, a subscription expired, or a scope was removed from the manifest during the last release.

Type
Chat, meetings and collaboration platform
First released
2017
License
Proprietary, licensed via Microsoft 365 plans
Maintained by
Microsoft Corporation
Typically used for
Team chat, meetings, bots, Adaptive Cards, Graph integrations, channel-scoped apps

The honest version

Microsoft Teams pros and cons

No technology is all upside. This is where Microsoft Teams earns its place and where it tends to cause trouble.

Where Microsoft Teams is strong

  • Bundled with Microsoft 365Most enterprises already pay for it, so adoption is often free in budget terms and the admin team already has the training.
  • Deep Microsoft Graph integrationCalendars, mail, SharePoint files and user directory data are all reachable from the same auth and permission model, which lowers the cost of a cross-surface integration.
  • Meetings, chat and calls under one roofThe same client handles 1:1 messages, group chats, channel conversations, live meetings and phone calls, which simplifies the user story even when the admin side is complex.
  • Adaptive Cards are a real UI languageA bot can render structured interactive content inside a message, and the same card format works on Teams, Outlook and third-party hosts, so the rendering code is reusable.
  • Compliance features baked ineDiscovery, retention policies, DLP and audit logs are enterprise-grade and tightly bound to the same identity model as the rest of M365.
  • App catalog and tenant policiesAdmins can approve a specific app version, scope it to a group, and block side-loading for the rest of the organization without touching code.

Where Microsoft Teams bites

  • The developer story has three overlapping SDKsBot Framework, Teams JS and Microsoft Graph have overlapping responsibilities, different auth flows and docs that reference each other awkwardly. A new engineer takes real time to get oriented.
  • Graph change notifications expireSubscriptions must be renewed on a strict schedule, and a missed renewal silently loses events. Nobody notices until a downstream system falls behind, which is usually at the worst time.
  • Tenant admin can block everythingA tenant policy change can disable your app overnight, and the error the user sees is often a generic consent prompt rather than a clear admin message.
  • Messaging extensions have a hard 15-second budgetCompose extension queries must return within fifteen seconds. Any upstream slowness and the user sees a broken UI.
  • Upgrading the manifest schema is fiddlySchema versions keep moving, deprecating fields you relied on. Validating a change locally never catches everything the App Studio or Developer Portal will.
  • Guest access rules are a mazeExternal federation, guest users, shared channels and B2B invitations interact in ways that neither the admin UI nor the docs make easy. The integration that works for internal users breaks for guests in subtle ways.

Sound familiar?

Common Microsoft Teams problems we fix

The Microsoft Teams problems that bring people to us, and what you have once each one is fixed.

BotFrameworkAdapter: 401 Unauthorized

The bot stopped receiving messages

A client secret that expired in Azure AD, a new tenant that was never consented to the app, or a messaging endpoint URL that was changed without updating the Bot Channels Registration.

Bot authenticated and delivering

Subscription expired: 42 events lost

Graph change notifications stopped firing

A subscription that reached its expirationDateTime without being renewed by the worker, often because the worker has been quietly crashing for a week.

Subscriptions renewed on schedule

Graph throttled: 429, retry-after 30

Our Graph integration is being throttled

A backfill or scheduled job hitting per-application and per-tenant limits without honoring Retry-After. The symptom is missing data, not an obvious failure.

Throughput smoothed, throttles respected

AADSTS50011: Reply URL mismatch

SSO redirect loops after a tenant change

A reply URL that was correct in one environment and not updated in Azure AD after a rename, or a multi-tenant app that is not listed in the home tenant's enterprise applications.

SSO redirects clean

composeExtension/query took longer than 15s

Messaging extensions time out

A compose extension that calls a slow third-party API synchronously. Teams closes the invoke after fifteen seconds and the user gets an error.

Extensions answer inside the budget

Policy blocked external app installation

Users cannot install the app

A tenant that recently restricted third-party apps, or a custom app that was not approved in the admin center under the new policy.

App approved and installable

manifest: version 1.14 schema validation failed

The new manifest version will not sideload

A field renamed or removed in the schema version you targeted, or a mix of 1.13 and 1.14 constructs that only shows up when the Developer Portal validates it.

Manifest clean and installable

What we do

Microsoft Teams help, from bot to tenant

Pick up the phone for one broken subscription, or pass us the whole Teams platform footprint.

Rescue
Bot silent, subscription expired, SSO looping, or an app the admin center just quarantined. We move fast and write up the cause after the fire is out.
Bots, tabs and messaging extensions
Built against the current manifest schema, with the identity model actually understood rather than copied from a sample repo that is two years old.
Microsoft Graph integrations
Change notifications with lifecycle-aware renewal, delta queries that handle missed pages, and throttling behavior that actually reads Retry-After.
SSO and tenant admin
Enterprise application registration, admin consent flows explained to the real admin, and the app set up so a tenant policy tweak does not disable it the next morning.
App submission and governance
Getting the custom app through the tenant catalog or the public Partner Center, with the manifest, privacy content and testing it actually needs.
Managed Tech
Subscription renewals watched, manifest schema deprecations tracked, policy changes in the tenant surfaced before they break the bot. Continuous rather than one-shot.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Microsoft Teams alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Microsoft Teams questions

Something else? Call+1 737 727 7327

Why has our Teams bot stopped receiving messages?

The common causes are an Azure AD client secret that expired, a messaging endpoint URL that was changed without updating the Bot Channels Registration, or a manifest that references a different app ID than the one the bot is authenticating as. The Bot Framework logs will usually say 401 Unauthorized or 403 Forbidden, and the fix is almost always on the Azure side rather than in the bot code itself.

How do we keep Microsoft Graph subscriptions alive?

Subscriptions have a short, resource-dependent maximum lifetime and must be renewed before expirationDateTime. The usual mistake is a cron that expects the subscription to live forever. The fix is a worker that lists subscriptions, renews each one well before expiry, and alerts if a renewal fails rather than leaving a quiet gap.

Why does our Teams messaging extension time out?

Teams enforces a fifteen-second budget on invoke activities, and any upstream API that takes longer will push the extension past that limit. The right pattern is to cache the slow data ahead of time, return a lightweight first response and update the card asynchronously, rather than blocking on the slow call during the invoke.

Our admin blocked our custom Teams app. What can we do?

Tenant admins can restrict third-party apps, require approval of custom apps, or scope installation to specific groups. The fix is usually a conversation with the admin rather than a code change: submitting the app for approval through the Teams admin center and showing what it does with which permissions. We can prepare the submission and walk the admin through the review.

How do we handle SSO inside a Teams tab?

Teams tabs can exchange a client-side token for a Graph token via getAuthToken and on-behalf-of, which avoids a second login prompt inside the tab. The common failure is a reply URL mismatch in Azure AD or missing admin consent for the requested scopes. We set the app registration up correctly and keep it working through tenant renames and secret rotations.

How much does Microsoft Teams help cost?

The quote is free. Send us the manifest and a description of what is going wrong, and we return a scope and a fixed price before we touch the Azure or admin center side.

Free estimate

Microsoft Teams giving you trouble?

Bots, tabs, meeting apps, Graph subscriptions and admin center policies. We work on the whole Microsoft 365 developer surface.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.