Users and groups Coming soon
Entra ID → another tenant
Coming soon. This tool is built and shows on its menu, but it does not open in a released build yet. This page describes it as it will ship.
Reads the users, guests and groups of one Microsoft 365 organisation and plans how each will look in another. You review the plan row by row, then create the ones you choose in the destination, with their memberships and licences.
Makes changes. It creates users, guests, groups, memberships and licences in the destination tenant only after you choose Run and confirm. The source tenant is only ever read.
What does it do?
- Each person and group gets a proposed status: Create, Invite, Exists, Skip or Conflict. Nothing is made until you run it.
- Anyone already in the destination with the same user name or email is marked Exists, so a second copy is not made.
- A possible match by name is marked Conflict, so you can choose that person or group, or create a new one.
- Rewrite rules change the source domain into a destination domain for new user names. Only domains verified in the destination can be chosen.
- The Licences tab maps each source licence to a destination licence and shows free seats, seats needed and seats left after the run.
- New users get a first password they must change when they sign in, saved to a file at the end of the run.
How it runs
- Connect both tenants. Sign in to the source, then to the destination. They must be different Microsoft 365 organisations.
- Review the plan. Check each row's status, destination user name, licence and usage location. The Why column explains each proposal and anything that blocks a row.
- Set rules and licences. Add rewrite rules for user names, and choose which licence each source licence becomes. To edit many rows at once, use Export CSV, change the file, then Import CSV.
- Save the plan. Save plan keeps your decisions for this pair of tenants. Nothing is created yet.
- Run. ShareMaster checks your sign-in can make what you ticked, shows what it will create, and asks first. It reads back each item as it is made. Guests are invited without Microsoft's invitation email.
- Save the first passwords. Save the new users' passwords to a file before you leave. They are shown only once.
What do you need?
- Source: a sign-in that can read the directory, such as Global Reader.
- Destination: a User Administrator or Global Administrator. The check before the run names any role that is missing.
- The Clone Master plan, or the trial.
What will it not do?
- Users synced from on-premises are created as cloud-only accounts.
- Distribution lists, mail-enabled security groups and role-assignable groups are listed only, never created.
- Groups that belong to a team are left to Copy a team.
- A dynamic group's rule is copied with the domains rewritten, not evaluated. Read it before you create it.
- A guest with no email address cannot be invited.
- Undo, from Past Entra ID migrations, takes back only what that run created. A stopped run resumes when you choose Run again, without making duplicates.