The recovery scope
| Source access | What to expect |
|---|---|
| Direct user or guest shares | Match the recipient and restore supported Read or Edit access on the destination item. |
| Group shares | Choose user-level restoration or preserve group shares for mapping to destination groups. |
| Specific-people links | Supported recipients can be restored through direct permissions; an expiring link needs review. |
| Organization or anyone links | A new destination link may be created when explicitly allowed and permitted by Microsoft policies. |
| Inherited or standard site access | Usually skipped as an individual file grant; inspect the parent or site-level access instead. |
Migrate the content first
ShareRestore does not copy the files, recreate a library, rebuild Teams conversations, or move mailboxes. It finds the migrated destination content and applies the access changes you reviewed.
Teams channel files are SharePoint content. Treat the relevant SharePoint site as the content scope; a successful file-access restore does not mean Teams membership, chats, or the rest of a Team were migrated.
Review exceptions instead of assuming equivalence
- A new tenant has different account IDs and link addresses. Source identities must be mapped or explicitly excluded.
- Destination sharing rules still apply. A blocked domain or disabled external sharing cannot be fixed by approving the same batch again.
- Unsupported roles, missing recipients, ambiguous matches, and expiration controls can require review or block an entry.
- Restoring a group share does not create the group or synchronize its membership. Confirm the destination group already has the intended members.
Old links and new access are different
An old source URL is not made into a destination URL. For link recovery, use the exported link map to find newly created destination links. For specific-people conversion, access may be preserved through direct permissions rather than a replacement link of the same type.