Update your on-premises data gateway to avoid sign-in problems

Microsoft is rolling out security-related sign-in changes for the Microsoft identity platform. Microsoft rolls out these changes gradually, and the exact timing varies by tenant. Your gateway can be affected at any point during this rollout, so if you're on an older build, update it now rather than waiting.

Important

Microsoft completes enforcement across all tenants by August 31, 2026. Update affected gateways before then to avoid interruptions.

What you might experience

On older builds, interactive sign-in might not complete when you install, configure, recover, update, or manage a gateway. Sign-in flows that open a browser are most at risk. Normal gateway operation that doesn't require a new interactive sign-in might continue.

Who should update

Update your gateway if you manage an on-premises data gateway and any of the following conditions are true:

  • Your gateway isn't on a May 2026 or later release.

  • Your gateway is on a January–April 2026 release but is below the patched build:

    Release Patched build
    January 3000.302.7
    February 3000.306.5
    March 3000.310.3
    April 3000.314.6

  • You see an update notification or banner.

  • You experience sign-in problems while installing, configuring, recovering, updating, or managing a gateway.

May 2026 and later releases all include the fix. On January–April 2026 releases, you're only protected on the build listed in the preceding table. To check your version, go to Currently supported monthly updates.

How to update

Update from the gateway management experience when prompted, or download and run the latest installer:

Note

You need gateway admin permission to update a gateway.

Update a gateway cluster

For clusters, update members one at a time to reduce disruption:

  1. Disable one gateway member.
  2. Wait about 30 minutes for active work to drain.
  3. Update the member.
  4. Re-enable the member.
  5. Repeat the steps for each remaining member until all members are updated.

If sign-in is already failing

  1. Download and run the latest standard mode gateway installer.
  2. Complete the update.
  3. Try signing in again.

If the issue continues, contact Microsoft Support and include your gateway version, environment type, and the step where sign-in fails.

Why this update is needed

Microsoft is updating gateway sign-in to align with current Microsoft identity security requirements. Gateway releases before May 2026 (and unpatched January–April 2026 builds) might not support the updated sign-in method. This limitation can interrupt sign-in during gateway setup and management. Updating to a current version restores and protects sign-in.

Related content

  • Last updated on