Migration software
Microsoft365DSC
Suggested in one of our migration playbooks, mainly for Microsoft 365. Here is what it handles, how it treats key settings, and other tools for the same jobs.
What does Microsoft365DSC handle?
The limits of the built-in tools that Microsoft365DSC gets around, as covered in our playbooks.
Move users between Entra tenants
- Conditional Access does not travel with the usersOpen-source project that clones a tenant's configuration over another one (Conditional Access is the AADConditionalAccessPolicy resource). The project notes that tenant-specific values are not always moved into variables, so review the generated files and test in report-only mode before you apply them.
- Conditional Access policies do not travel, and the exported files hold old-tenant IDs.Open-source tool that clones tenant settings, including Conditional Access. Review the generated files and test in report-only mode.
How does Microsoft365DSC handle key settings?
From the settings checklists in our playbooks: what Microsoft365DSC carries across.
| Setting | How it handles it | Playbook |
|---|---|---|
| Conditional Access policies | Open-source tool that clones tenant settings, including Conditional Access, from one configuration file. Review the generated files and test in report-only mode. | Move users between Entra tenants |
Which tools do the same jobs as Microsoft365DSC?
Other tools our playbooks suggest for the same migrations.
We write these notes from the vendor documentation cited in each playbook. Tools cannot pay to be included or to change them. Check the vendor's current documentation and terms before you buy.