Recovering a deleted Team and its data

A Team is a Microsoft 365 group wearing a Teams client. That single fact explains almost everything about recovering one: you do not restore the Team, you restore the group, and the Team follows. The full mechanics of the group side are in restoring a deleted Microsoft 365 group; this runbook is the Teams-specific procedure, including the cases where "the Team is gone" means something other than deletion.

Step 0: find out what actually happened

"Our Team disappeared" has four common causes, and only one of them is deletion.

1. The user was removed from the Team. Search for the Team in the Teams admin center. If it exists with members, the user was removed — a membership problem, not a recovery.
2. The Team was archived. Archived teams drop out of the user's main list into Hidden teams or Archived. Teams admin center → Teams → filter by Archived. Unarchive and it is back instantly, with nothing lost.
3. The group expired. Group expiration policy deletes the group after the renewal period passes unnoticed. This is deletion, but with a specific cause to fix afterwards.
4. Someone deleted it. An owner clicked Delete team, or an admin removed the group.

The Unified Audit Log settles this in one search: filter on the group name for TeamDeleted, GroupRemoved or Delete group, which gives you the who and when. If the Team was created less than a day ago and vanished, also check whether the creation ever completed — a Team provisioning failure looks like a deletion to the user.

Step 1: check the 30-day clock

Deleted groups are soft-deleted for 30 days. Look in Entra admin center → Groups → Deleted groups, or Teams admin center → Teams → Deleted teams (which is the same list, filtered). If it is there, you have a restore. If it is not, go to the section on the far side of the window below.

Step 2: restore the group

From the Teams admin center, select the deleted team and choose Restore. From Entra: Deleted groups → select → Restore. From PowerShell:

Get-MgDirectoryDeletedItemAsGroup -All | Where-Object DisplayName -eq "Project Falcon"
Restore-MgDirectoryDeletedItem -DirectoryObjectId "group-id"

Check the mail address and deletion date before restoring, not just the display name. Teams get recreated with the same name more often than you would expect.

Step 3: wait, and set expectations

This is the step that generates the follow-up ticket. The group, its SharePoint site, files and mailbox come back within minutes. The Team itself can take up to 24 hours to reappear in the Teams client. In practice it is often faster, but tell the requester "tomorrow" and let it be a pleasant surprise.

While waiting you can confirm the Team is linked to the group: Get-MgGroup -GroupId "group-id" -Property resourceProvisioningOptions should show Team. If it does not, the object you restored was a plain Microsoft 365 group that never had a Team, and creating a new Team from the existing group is the fix.

If the Team has not appeared after 24 hours and the provisioning option is present, open a support case. This does occasionally need Microsoft to nudge the Teams back-end, and it is one of the few Teams issues where support genuinely resolves things.

What returns

• Standard channels, their conversation history, tabs, pinned items and files.
• Private channels, each with its own SharePoint site. Private channel sites are restored alongside the parent, though they can lag the parent by a while.
• Shared channels, with their own sites and their cross-team membership.
• Planner plans, the group calendar, the group mailbox, Loop workspaces attached to the group.
• Apps and bots installed to the Team, subject to whatever the app itself does with its own back-end data.
• Meeting recordings stored in the channel's Files.

What does not

• Files or messages deleted before the Team was deleted are governed by their own recycle bins and retention, not by the group restore.
• Chat in meetings scheduled from the channel is part of the channel and returns; but private 1:1 chats between members were never part of the Team and are unaffected either way.
• If a retention policy for Teams channel messages disposed of messages during the deleted period, they are not restored.
• Pending guest invitations.

The far side of 30 days

The group is permanently gone. The Team's chat history — which lives in the group mailbox and in the Teams substrate — is gone with it, and no Microsoft support path restores it. What may still exist:

• The SharePoint site, in SharePoint admin center → Deleted sites, on its own 93-day clock. Restoring it gets files, versions and the channel folder structure back, orphaned from any group. You can create a fresh Team and copy content across, or connect the restored site to a new group. Either way, channel conversations are not part of this.
• Retained channel messages. If a Teams retention policy covered channel messages, the messages are held and discoverable in eDiscovery for the retention period, even though the Team is gone. You can export them; you cannot put them back into a Team.
• Backup. Microsoft 365 Backup does not cover Teams messages; third-party products that claim to should be checked against how they restore chat — most rehydrate into a new Team in a read-only or "imported" form rather than as native history.

Special cases

• Team deleted, group still there. Rare, but possible via Graph: the Team is removed and the group persists. Creating a Team from the existing group (New-Team -GroupId) is the fix; channels and history are not recoverable in that case because they were removed with the Team object.
• Owner deletes a Team by accident, repeatedly. Restrict who can delete teams by removing the Delete team ability at the owner level? You cannot — owners can always delete their team. What you can do is make owners aware that deletion is a 30-day soft delete, and reduce the number of owners to people who understand that.
• Expired group. After restoring, renew the group, and fix the expiration notification path so the next expiry email goes to a human who reads it.

Preventing the next one

Turn on the Teams deletion audit alert (an alert policy on TeamDeleted) so you know the day it happens rather than on day 31. Keep at least two owners per Team. And if channel history matters to the business, put a retention policy on Teams channel messages — it is the only thing that survives the 30-day boundary.