What happens if Microsoft has an outage during migration?

PowerSyncPro Migration Agent keeps retrying until Microsoft restores service, then the migration carries on.

When a device moves to Microsoft Entra joined, and Microsoft Entra ID (formerly Azure AD) is unavailable, this is what happens:

1. The device leaves the source Active Directory or Entra tenant.

2. The device shows users that a migration is under way. You control this with three runbook options, available in PowerSyncPro 3.2 or later:

   Lock screen background image. The lock screen shows a "migration in progress" image. Use the default image or your own branded one.

   Legal notice. A user who tries to sign in sees a warning with your caption and text, telling them the migration is not finished.

   Prevent Login. Sign-in is blocked for the users known to use the device, so they stay off a half-migrated machine.

   See Migration in progress lock screen and legal notice for setup.

3. PowerSyncPro Migration Agent attempts the Entra join. If the join fails, it reports the failure to the orchestration server.

   The same applies when the target is Active Directory. If the domain join fails, PowerSyncPro Migration Agent retries until the problem is fixed. This covers a wrong or expired password on the domain join account. Update the password in the runbook, and the agent picks up the new password on its next attempt and completes the join.

4. It retries on a Fibonacci back-off schedule, settling at one attempt every hour.
5. When Microsoft restores service, the join succeeds and the migration carries on.

Intune enrolment works the same way. PowerSyncPro Migration Agent triggers enrolment at logon. If enrolment fails, it retries every hour until it succeeds.

Retries run at least once an hour. Anything in your environment that depends on the Entra join or Intune enrolment should resolve within an hour of Microsoft restoring service.

During the Microsoft 365 outage of 12 to 13 November 2026, Microsoft listed Intune device enrolment, check-in and compliance as intermittently affected (incident MO1550821).