Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources or documents need attention: 253/260 feeds/APIs · 416/439 docs · checked 17:40 UTC Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Entra: Security hardening to prevent user account takeover in Microsoft Entra Connect Sync

Action date

114d ago Act by , as Microsoft's metadata states

What the notice says

Microsoft's text, with its sections, lists and tables; source markup removed

Introduction

Microsoft is strengthening security in Microsoft Entra Connect Sync to prevent user account takeover through hard match abuse. These updates improve the integrity of identity mapping between on-premises Active Directory and Microsoft Entra ID and expand audit visibility for administrators.

When this will happen

  • Enforcement of this change will begin on July 1, 2026.
  • General Availability (Worldwide, DoD, GCC, GCC High): Rollout begins in early July 2026 and completes by late September 2026.

How this affects your organization

Who is affected

Organizations that use Microsoft Entra Connect Sync to synchronize user identities from on-premises Active Directory to Microsoft Entra ID

What will happen

How hard match works

When Microsoft Entra Connect adds new objects from Active Directory, it compares the object’s sourceAnchor value with the OnPremisesImmutableId of an existing cloud-managed user. If these values match, a hard match occurs and the cloud object is taken over by Microsoft Entra Connect Sync.

Security hardening changes

  • Microsoft Entra will block Entra Connect from updating OnPremisesObjectIdentifier once it has been mapped to a synced user object.
  • This prevents unauthorized remapping of an existing cloud user to a different on‑premises identity.
  • Blocked operations will return:

“Hard match operation blocked due to security hardening. Review OnPremisesObjectIdentifier mapping.”

  • Audit logs will now include changes to:
  • A new Microsoft Graph API will support controlled recovery scenarios that require legitimate remapping.
  • No changes occur to user experience unless a remapping attempt is blocked.
  • OnPremisesObjectIdentifier
  • DirSyncEnabled

What you can do to prepare

  • Review updated Entra Connect security hardening guidance.
  • Use audit logs to identify users where OnPremisesObjectIdentifier has recently changed and remediate before enforcement.
  • Test the new Microsoft Graph API–based recovery flow for legitimate remapping scenarios.
  • Update internal operations documentation and notify identity management teams.

Learn more

Compliance considerations

No compliance considerations identified. Review as appropriate for your organization.

What changed

Between the versions this installation saw, newest first

This installation has seen one version of this notice, first on 22 Oct 2026. Later changes will show here.

Linked documentation

Microsoft pages the notice links to

This site links to Microsoft's pages instead of copying them. Installations inside an organization can keep a copy for comparison.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
  • Versions before 22 Oct 2026: this installation first saw the notice after Microsoft posted it.
  • 2 linked pages have not been read yet.
  • Some history or links were left out of the website export to keep it within its size limits.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 22 Oct 17:40 UTC · 253 of 260 readable · 251 fully read · documentation 416/439 current