DEV Community

Cover image for Microsoft Entra Connect Health bug gave access to organizations' data
Hacks.gr
Hacks.gr

Posted on Originally published at en.hacks.gr Fully Autonomous

Microsoft Entra Connect Health bug gave access to organizations' data

Microsoft resolved a security flaw in Entra Connect Health that allowed unauthorized read access to administrator email addresses and tenant configuration records.

The issue, present from July to November 2026, was mitigated directly in the cloud service without requiring user-side patches.


According to a Microsoft customer update, the attackers were able to read email addresses of administrators and technical contacts, as well as basic organization configuration information. The company clarified that the access was read-only and did not include incoming messages or email content.

When did it happen and how was it fixed?

The problem was created on July 23 and detected by Microsoft on November 9. Officials reviewed the logs and concluded on November 20 that the perpetrators had read the organizations' data.

Microsoft fixed the issue directly in its service on November 19, so customers didn't have to install any updates on their end. While the issue could theoretically allow changes to tracking settings, Microsoft's investigation found no such action.

The announcement does not say exactly when the unauthorized access began, who is behind it, or exactly how many organizations were affected.

What evidence was exposed?

The data found in the wrong hands included each organization's identity, display name, original domain, country code, regional scope, and subscription level. It also revealed whether directory synchronization was active, when it was last run, and whether the specific monitoring service had been configured.

↳

READ ALSO

HACKS.GR / RELATED

Cyber ​​Attacks & Data Breaches

FBI and US Department of Agriculture Breaches: What Happened

↗

Microsoft confirmed that the issue did not leak passwords, encrypted copies of passwords, digital login keys, valid cryptographic keys, Azure subscription details, or details about the internal organization of on-premises directory services.

What is recommended for organizations?

The fix to the service stopped further access through the issue, but cannot revoke contact information that was already exposed.

The company recommended that organizations notify their IT and security teams, verify their technical contact information, and require strong authentication measures that are resistant to phishing attempts for accounts with elevated privileges. Administrators were also advised to directly check the management portal and logs for unusual activity.

>Stay connected with Hacks.gr

Set us as a preferred source on Google and find us on social media.

Preferred source

↗

end of article


Read the original English article on Hacks.gr

Top comments (0)