Four steps, apart from the policies
Applications has its own place in the sidebar, beside Migrations, and uses the tenants signed in on Connect: Choose apps, Map users & groups, Pre-flight and Deploy. The users, groups and owners of the chosen apps are matched in the destination the same way as for policies, by email, username, name or mail nickname, and anything with no match is chosen by hand or left out.
What moves
- Enterprise apps, such as Zoom, Slack or Miro: another organization's app, created in the destination for the same app ID. Its settings come with it (assignment required, visible to users, notes, home page, sign-on URL), with its owners and every user and group assigned to it, each keeping its app role. An app the destination already has can be skipped or updated in place; nothing is taken away from it.
- App registrations, the source's own apps: recreated with a new app ID, with their redirect URIs, app roles (with the same role IDs), optional claims, exposed API scopes and requested permissions, and an application ID URI made from the new app ID. Every new app ID is listed when the run finishes, so you can change anything that signs in with the old one.
- Gallery apps: made again from the same gallery template, then set up as they were in the source: entity ID, reply and logout URLs, and app roles.
- SAML single sign-on: the sign-on mode and relay state, claims mapping policies and the claims on the Attributes & Claims page. Each SAML app gets a new signing certificate, because the old one's private key can't be exported, and pre-flight lists every app whose vendor needs the new certificate or federation metadata.
Policies find the apps migrated for them
An app registration has a new app ID in the destination, so a Conditional Access policy that names it would point at nothing. Movewise keeps a map of every app it migrated, from the old app ID to the new one. On Map dependencies, a policy's app is matched to its migrated copy as Migrated by Movewise and the policy is rewritten with the new app ID. An app the destination doesn't have yet has a Migrate it in Applications button, which opens Applications with that app ticked, and policy pre-flight lists the policies still pointing at missing apps. Migrate the apps first, then the policies.
What Movewise never does
- It never grants admin consent. The API permissions an app was granted in the source are listed in pre-flight, for an admin to review and grant in the destination.
- It never copies secrets. Client secrets and certificate private keys can't be exported, and are listed under Set up by hand, with provisioning (SCIM) settings, Application Proxy connectors and password-based sign-on.
- It only removes what it made. Rolling back an app run deletes the apps the run created (Entra ID keeps them in deleted apps for 30 days), puts back the settings of apps it updated, and removes only the owners and assignments it added.
Before you start
In the destination, the account needs Application Administrator, Cloud Application Administrator or Global Administrator, and Movewise asks for three more Microsoft Graph permissions there: Application.ReadWrite.All, AppRoleAssignment.ReadWrite.All and Policy.ReadWrite.ApplicationConfiguration. The app registration guide lists what each is used for. The built-in demo has sample apps of every kind, and a Conditional Access policy that uses one of them, so the whole flow can be tried without a tenant.