People, guests & groups

Restore access for a guest who is not in the destination yet

Keep an external collaborator's email or map them to a different existing destination account.

Quick answer

For an eligible external recipient, Keep access for the same external email can reuse a destination guest or create one during approved restore execution. Microsoft sends an invitation if the guest is new.

Your next step

Confirm the external email is still authorized and review the invitation and permission changes before approving the batch.

Choose one of three outcomes

DecisionUse it when
Map to a destination accountThe recipient should use a specific existing destination member or guest account.
Keep access for the same external emailThe source recipient is external and should keep using that external identity.
Do not restore this identity's accessThe recipient's access is no longer authorized or is intentionally outside the migration scope.

When a new guest is created

  1. Save the external-email decision and prepare the batch again. This step records the decision; it does not invite the person or grant access.
  2. Review the proposed destination files, email, and access levels.
  3. Approve the batch. During execution, ShareRestore looks for an existing destination identity with the external email.
  4. If one exists, it is reused. Otherwise ShareRestore requests a Microsoft Entra B2B guest invitation and Microsoft sends its invitation email.
  5. ShareRestore waits for the guest to become resolvable for SharePoint, applies the approved access, and checks the resulting permission.

If Microsoft blocks the guest

  • The destination connector must have the required guest-invitation permission and administrator consent.
  • Tenant external-collaboration settings, cross-tenant rules, blocked domains, and SharePoint site sharing settings still apply.
  • Ask the destination administrator to review the exact policy or permission error. ShareRestore cannot override those controls.
  • An existing guest can take time to resolve in SharePoint. Check the run detail before retrying or manually creating another guest.

If the destination email is different

Use Map to a destination account and select the existing destination identity. Keep access for the same external email intentionally preserves the source external email; it is not an email-renaming option. Groups cannot use this guest-preservation decision.

Continue with the next relevant guide.

Need help with your project?

Send the exact error and your project, batch, or run reference so we can investigate.

Get support