Microsoft Entra Connect Health API Flaw Exploited: Attackers Read Admin Emails, Tenant IDs and Sync Status for Four Months Before a 19 November Server-Side Fix

Cyber · 2026-11-22 · By H.A

Microsoft Entra Connect Health API Flaw Exploited: Attackers Read Admin Emails, Tenant IDs and Sync Status for Four Months Before a 19 November Server-Side Fix

Microsoft says an attacker abused a Connect Health API bug introduced on 23 July 2026 to read tenant metadata including administrator email addresses, and although no customer patch is needed, the leak hands attackers a ready-made spear-phishing list.

Microsoft is notifying organisations that an attacker exploited a flaw in the Microsoft Entra Connect Health API to read tenant-level metadata, including the email addresses of administrator and technical contact accounts. The vulnerability sat in the service for almost four months before Microsoft found it. Microsoft fixed it on its own servers on 19 November 2026, so customers have nothing to patch. They do have a phishing problem to plan for.

What Happened

According to the customer notice, which administrators have shared publicly and Microsoft has confirmed to the press, the timeline is:

The notice states: "On 20 November 2026, we concluded our investigation and determined that unauthorized read-only access to tenant-level metadata associated with your organization had occurred." It adds: "We did not identify any unauthorized configuration changes."

A Microsoft spokesperson said the company "deployed a fix on November 19, 2026, and have notified impacted customers through Azure Service Health", and declined to give more detail. Microsoft has not said how many tenants were affected, who exploited the flaw, or when the abuse started. No CVE identifier has been published. That is common for cloud-only flaws fixed entirely on Microsoft's side, but it means the incident will not appear in normal vulnerability feeds.

Some administrators said they received the notice for their own tenant. Managed service providers reported notices for several customer tenants at once, which suggests the exposure was not limited to a handful of organisations.

What Connect Health Is

Microsoft Entra Connect Health is the monitoring part of Microsoft's hybrid identity stack. Organisations install an agent on their on-premises identity servers, which can be Entra Connect Sync, AD FS or AD DS domain controllers. The agent reports alerts, performance data, sync errors and usage analytics to the Entra admin center. It requires an Entra ID P1 licence. In practice it is used mostly by larger organisations that still run on-premises Active Directory alongside Microsoft 365.

That makes the customer list itself valuable. Any tenant with Connect Health onboarded is a confirmed hybrid identity environment, and attackers have repeatedly targeted Entra Connect servers and their sync accounts to move from on-premises AD into the cloud.

What Was Exposed

According to Microsoft's notice, the API returned:

Microsoft says the flaw did not expose passwords, password hashes, authentication tokens, valid cryptographic keys, on-premises server or Active Directory topology, or Azure subscription information. The investigation also found that the bug could have allowed changes to Connect Health monitoring configurations. Microsoft says it saw no such changes.

Why It Matters

On its own, this is a read-only metadata leak. Combined with other data, it is a ready-made targeting list. An attacker now holds, for an unknown number of organisations:

That is enough for well-targeted spear-phishing, device-code phishing, fake "Microsoft support" calls or fake outage notices addressed to exactly the people with Global Administrator rights. Fake Microsoft 365 service notices quoting real incident IDs have already been used to phish admin logins this month. Attackers who know who holds the keys, and that the victim has an on-premises sync server worth reaching, can skip much of their reconnaissance.

The fact that an expired certificate from a retired service was still being returned is also worth noting. It does not appear usable, but it shows that old secrets were left in storage long after their service was retired. Security teams should check their own environments for the same mistake.

What To Do Now

Microsoft says no software update or customer remediation is required. Even so, if you received the Service Health notice, or you run Connect Health and are unsure, these steps are sensible:

Microsoft has also published read-only PowerShell scripts that show the kinds of tenant metadata involved. They use the Az.Accounts module (2.17.0 or later) and read access to Connect Health:

Install-Module Az.Accounts -MinimumVersion 2.17.0 -Scope CurrentUser
.\SelectConnectHealthTenant.ps1      # prompts for tenant ID, signs in
.\GetTenant.ps1                      # tenant-level Connect Health configuration
.\GetTenantPksCertificateDetails.ps1 # decodes stored certificate metadata in memory
.\GetServiceMonitoringConfigurations.ps1

The scripts show current values, not a record of what the attacker actually read. Treat the output as a list of what was potentially exposed.

The Bigger Picture

This is the latest in a run of server-side identity flaws at Microsoft that customers could neither detect nor fix themselves. The open questions are who was querying the API, how many tenants were affected, and whether the access began soon after 23 July. Until Microsoft answers them, any organisation running Connect Health should assume its admin contacts are on someone's target list and harden accordingly.

Sources

COMPUTE NODE · · --:--:--

Fresh cybersecurity news,
daily threat intelligence.

Daily cyber news, live threat intel and exploited CVEs.

Everything in one place

Self-hosted, hardened, and yours.

RUN IT

Local AI console

Chat with a model on your own hardware via Ollama or any OpenAI-compatible server. No cloud, no key.

DEFEND

Cyber threat feed

Automatic daily intel from CISA KEV, NVD & GitHub advisories, a live cyber threat map, and your own notes.

NEWS

News & videos

Articles and updates on pentesting, AI, and cyber — with embedded video, including YouTube. Post your own.

DIRECTORY

Registry

Runtimes, models, MCP servers, agents, and a full security & pentest tooling section.

PUBLISH

Posts

Write, edit, publish, and share articles backed by a real database and your account.

COMMUNITY

Forum

Threads and replies across categories from Models to Hardware to Security.

CODE

Repos

Curated AI and security GitHub repos, plus a shelf for pinning your own.

DOWNLOAD

Skill packs

Agent starters, RAG scaffolds, and defensive security & VAPT report templates.

Registry

Runtimes, models, MCP servers, agent frameworks, and a security & pentest tooling section — all links out to the real projects.

Local AI console

Talk to a model running on your own machine through Ollama or an OpenAI-compatible server — your prompts and the model's replies always go straight from your browser to your local model, never through a Reef server. Attach files for context, and pick up saved chats where you left off.

Type /image a prompt in the box below to generate
Not connected

Local AI hardware benchmark

A spec-based compatibility advisor — tells you which local models your hardware can run well, which will be slow, and which to skip. Connect to Ollama below for a real, measured speed test instead of an estimate.

1. Your hardware

2. Live check against your local model server (optional)

If a local model server is running, this cross-references the table above with what you've actually got loaded — and runs a real, measured speed test instead of an estimate.

AI Database

A browsable catalog of AI models across providers — context windows, pricing, and capabilities.

Loading…

Cyber threat feed

Latest threats pulled automatically every day from CISA's Known-Exploited-Vulnerabilities catalog and NVD — plus threat intel you post yourself.

⇩ Export STIX
Loading threat feed…

Cyber threat map

Attacks happening right now, all over the world.

Connecting…
LIVE · MAURITIUS TIME--:--:--
attack route, country to country attack route into Mauritius attacker reported worldwide
Loading live data…
attackers reported per minute · click to rewindnow

Top attack routesweb

Attackers based inlast hour

Networkslast hour

Click any dot, feed row or table row to see that IP's profile.

Mauritius

Who attacks Mauritius

Loading…

Web attacks malicious requests to Mauritian websites that were blocked
Network DDoS floods meant to knock Mauritian servers offline

    Mauritius · last 24 h

    How Mauritius is attacked

    Network-level attacks (DDoS) aimed at Mauritius, by method. They try to knock servers and networks offline by sheer volume.

    • Loading…

    The ports or services these floods aimed at aren't published.

    Mauritius · last hour

    Attackers located in Mauritius

    0attackers located in Mauritius were reported in the last hour

    This counts attacks coming from Mauritius, not attacks on it: IPs in Mauritius that servers elsewhere reported for attacking them. Usually zero or one; when it rises, it's often a hacked local server or router.

    Worldwide today

    What attackers are knocking on

    Ports most targeted across a worldwide network of sensors .

    Worldwide today

    Most active attackers

    Ranked by how many separate sensors they hit. Click a row for its profile.

    IPCountryNetworkSensors hitReports
    What you're looking at
    Blue routes

    Share of attack traffic from one country to another. Thicker, faster streams carry more. Particles show volume, not one per attack.

    Every 15 min · published 1–2 h behind
    Amber flashes

    An attacking IP that servers around the world reported in the last minute, placed where the IP is. Its targets aren't published, so there's no line.

    Every minute · shown about 1 min behind
    Locations

    IP locations are approximate (city level at best) and show where the machine is hosted, not who controls it.

    Approximate · city level at best

    News

    Articles, guides and updates on pentesting, AI, and cybersecurity — with embedded video. Add your own, including YouTube.

    Loading…

    Posts

    Loading…

    Loading posts…

    Forum

    Questions, answers, and talk about running AI locally.

    Loading forum…

    GitHub repositories

    Curated AI and security repos, plus your own pinned shelf.

    Command board

    One-liners, configs, and advice worth keeping — shared by everyone here.

    ⚠ Commands are shared with all users. Never include credentials, tokens, or internal hostnames. Review anything before you run it.
    Loading commands…

    Skill packs

    Starter files served from the API — AI agent scaffolds plus defensive security & VAPT reporting templates. Click to download.

    Loading skills…

    Your watchlist

    Follow threat actors, malware, CVEs and vendors — we tell you when a new report, CVE record or exploitation alert mentions them.

    Threat Library

    Threat actors, malware and tools — their attack techniques, Reef Sentinel coverage and indicators of compromise.

    Loading…

    Threat Intelligence

    Curated threat write-ups, advisories and analysis — with cover media.

    Loading…

    Tutorials

    Step-by-step guides for running local AI, using the console, and tracking threats. Admins can add their own.

    Loading…

    Downloads

    Direct links to the official homepage/download page for well-known cybersecurity, penetration-testing, and local-AI software. Always verify checksums/signatures from the vendor before running anything.

    Loading…

    Privacy Policy

    Loading…

    Terms & Conditions

    Loading…

    Help & FAQ

    Answers to common questions about Reef Sentinel, plus a formatting guide for posts, articles, and comments.


    Formatting guide

    Commands you can type into the body of a post, comment, or reply — no HTML needed. Comments and short replies only support bold, italic, and inline code.

    Contact us

    Questions, feedback, or a security disclosure? Reach us directly, or send a message and we'll get back to you by email.

    Loading…

    Send a message

    VAPT Report Generator

    Build an engagement, add findings with a live CVSS calculator, and generate a branded, print-ready report.

    Recon Toolkit

    Investigate any domain, IP, URL, file hash, email or CVE in one search, plus breach and password checks, hash identification and a payload cheatsheet.

    Outage Monitor

    Is Microsoft 365, Facebook, Google, AWS or ChatGPT down? Live status of the big tech services from their official status pages, every incident with its full timeline, and how long each one took to fix.

    Website Checker

    Reads a website's HTTP response headers to identify its framework and server, shows any known CVEs for the exposed versions with details, and recommends what to do.

    Control panel

    Manage everything shown on the site — news & videos, posts, homepage headlines, and subscribers. Admin only.

    Overview
    Content
    Site
    Account & Security

    Email settings

    SMTP on ports 25/465/587 is blocked outbound by some hosts (e.g. DigitalOcean droplets by default) — Resend and Brevo send over their HTTPS API instead, so they work even then. Only the selected provider is used to send; the others stay saved but idle, so you can switch back any time without losing settings.

    Get a key from resend.com/api-keys. Uses the "From address" below as the sender — it must be on a domain you've verified with Resend.

    Get an API key (not an SMTP key) from app.brevo.com/settings/keys/api. Uses the "From address" below as the sender — it must be a verified sender in your Brevo account.

    "From address" and "Site name/URL" are shared by SMTP, Resend, and Brevo — they control what recipients see, regardless of which provider is active.

    Send a test email

    Sends through whichever provider is currently active above. Save your settings first if you just changed them.

    SIGNAL LOST

    We couldn't find this page

    The page may have been moved or deleted, or the address was mistyped.