Skip to content

Movewise 0.3.0

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 26 Oct 13:32
v0.3.0
af25425
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Unsigned test build: Windows SmartScreen warns when the installer runs (choose More info, then Run anyway). Try it against test tenants. Built from af25425.

New

  • Applications in the sidebar, beside Migrations, with its own steps: Choose apps, Map users & groups, Pre-flight and Deploy. It uses the tenants signed in on Connect.
  • Enterprise apps: other organizations' apps, such as SaaS apps, are created for the same app ID with their settings, owners, and user and group assignments, each keeping its app role. An app already in the destination can be skipped or updated in place.
  • App registrations: your own apps are recreated with a new app ID, with their redirect URIs, app roles, optional claims, exposed API scopes and requested permissions. Every new app ID is listed when the run finishes.
  • Gallery apps and SAML single sign-on: apps added from the gallery are made again from the same template and set up as before: entity ID, reply URL, relay state, app roles and claims, with a new signing certificate. Pre-flight lists each app whose vendor needs the new certificate or metadata.
  • Apps and policies together: Map dependencies matches policies to the apps Movewise migrated (Migrated by Movewise) and uses their new app IDs. An app that isn't in the destination yet has Migrate it in Applications.
  • Roll back an app run: apps the run created are deleted (Entra ID keeps them for 30 days), and apps it updated are put back as they were.
  • Nothing is granted for you: Movewise never grants admin consent; API permissions are listed for an admin to grant. Client secrets, certificates, provisioning (SCIM), Application Proxy and password-based sign-on are listed under Set up by hand.

Changed

  • The destination needs three more Microsoft Graph permissions: Application.ReadWrite.All, AppRoleAssignment.ReadWrite.All and Policy.ReadWrite.ApplicationConfiguration. An admin may be asked to consent to them on the next sign-in to the destination, and an app registration set up by hand needs them added (see docs/app-registration.md).
  • Creating and changing apps needs Application Administrator or Cloud Application Administrator in the destination, or Global Administrator.
Assets 8
Loading