Troubleshooting Microsoft Teams appointments stuck in draft state — technical guide
Why your Teams appointments are stuck in draft — and how to fix it
If calendar appointments created in Microsoft Teams keep surfacing as drafts rather than published, confirmed events, you’re dealing with one of a handful of well-known integration issues — all fixable. Here’s how to diagnose and resolve them.
What’s actually happening
Teams relies on the Microsoft Teams Meeting Add-in embedded in Outlook to write calendar events back to Exchange. When that pipeline breaks — due to a sync delay, permission mismatch, or a stale add-in state — appointments stop making it past the draft stage. The event exists locally but hasn’t been committed to the Exchange mailbox or dispatched to invitees.
Root causes at a glance
Invite not sent
The meeting was created but the Send button was never clicked — the event only exists as a local draft.
Calendar sync delay
Teams and Exchange are out of step. Usually self-resolves within a few minutes; a forced refresh helps.
Missing delegate rights
Scheduling on someone else’s behalf without the correct delegate mailbox permissions blocks commit.
Stale or disabled add-in
The Teams Meeting Add-in in Outlook may have become disabled, corrupt, or out-of-date.
Step-by-step resolution
- 01 Open the draft and click Send. This is the fix in the majority of cases. Open the appointment from the calendar, verify the recipient list, and hit Send rather than Save & Close.
- 02 Wait and refresh. If the event shows as draft immediately after sending, allow 2–3 minutes for Exchange replication and pull-to-refresh the calendar view.
- 03 Verify the Teams Meeting Add-in is active in Outlook. Navigate to File → Options → Add-ins → COM Add-ins → Manage and confirm Microsoft Teams Meeting Add-in for Microsoft Office is checked.
- 04 Force an Office update. Go to File → Office Account → Update Options → Update Now. Outdated add-ins are a frequent culprit after Insider or Current Channel rollouts.
- 05 Clear the Teams cache. Fully quit Teams, clear the local cache directory, then relaunch.
- 06 Sign out and back in. If the cache clear doesn’t resolve it, sign out of Teams, restart, and re-authenticate. This forces a fresh token and re-syncs the Exchange connection.
Clearing the Teams cache
On Windows, close Microsoft Teams completely first — check Task Manager to confirm no Teams process is running — then clear the following directory:
Delete all contents of this folder.
Do not delete the folder itself.
On macOS the equivalent path is:
Checking delegate permissions
If you’re booking on behalf of another mailbox, the mailbox owner needs to grant you Editor or Delegate access on their calendar through Outlook:
When to escalate
If none of the above resolves the issue across your organisation, the problem is likely upstream. Check the Microsoft 365 Service Health Dashboard in the admin centre for active incidents tagged under Microsoft Teams or Exchange Online. Calendar-related incidents (often tagged EX or TM) can cause widespread draft behaviour until Microsoft deploys a fix.
For persistent per-user issues, run the Microsoft Support and Recovery Assistant (SARA) — it automates diagnosis of Teams and Outlook calendar integration failures and can reset the add-in state without manual cache clearing.
