Movewise

Movewise / Migrate enterprise applications

Migrate enterprise applications between tenants

Move the apps people sign in to, the apps your developers registered, and the SAML apps from the gallery, with who can use them. New in Movewise 0.3.0.

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

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

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.

Try Movewise free

Windows 10 or 11. Open source, MIT licensed. The built-in demo needs no tenant at all.