Connections & discovery

Connect the source and destination tenants

Authorize the correct Microsoft 365 tenants and understand who must complete each connection.

Quick answer

Each project needs a verified source connection and destination connection. A tenant administrator must approve the requested connector access for their tenant.

Your next step

Open the project and check both tenant cards before starting a scan.

App sign-in and tenant connections have different purposes

Your ShareRestore sign-in identifies your workspace and customer account. The project connections authorize the source and destination Microsoft 365 tenants. Being signed in to ShareRestore does not by itself connect either tenant.

The source connector reads the source. The destination connector inventories destination content and applies approved restore operations. Review the requested access in Microsoft's consent screen.

Connect each side

  1. Create or select the project in Projects.
  2. On the source tenant card, choose Connect source. In Microsoft, select an administrator for the intended source tenant and complete the consent flow.
  3. Return to ShareRestore and confirm the source tenant shown is correct and the connection is verified.
  4. Repeat with Connect destination using an administrator for the destination tenant.
  5. Start scanning only when both connections are suitable for the work you intend to do.

Check the connected tenant, not just the account name

An administrator can have access to several tenants. Verify the tenant identity shown after consent rather than assuming the email address proves the right tenant was selected.

If you chose the wrong tenant, use Reconnect or change source tenant or Reconnect or change destination tenant. Changing a tenant can invalidate earlier scan and mapping work; scan and prepare the correct scope again.

If you cannot grant consent

  • Ask the administrator for that tenant to complete the connection link.
  • If Microsoft reports missing privileges, do not keep approving with the same non-admin account.
  • If a connection succeeds with a warning, read the warning and resolve the affected capability before relying on it.
  • Never put an administrator password, client secret, or certificate key in a support ticket.

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