- What happened: Microsoft mitigated a flaw in the Entra Connect Health cloud monitoring API (active July 23 β Nov 19, 2026) that allowed attackers to read tenant metadata, including administrator and technical contact email addresses, Tenant IDs, display names, initial domains, and license tiers.
- What was NOT exposed: No passwords, password hashes, authentication tokens, or on-premises Active Directory topologies were exposed, and no customer patch is required.
- Why you must act today: Armed with verified M365 admin emails + exact tenant IDs and license tiers, threat actors can craft hyper-convincing spear-phishing lures (fake Service Health alerts, fake billing notices, AiTM login pages). Enforce Phishing-Resistant MFA (FIDO2/Passkeys) on every privileged role and audit admin sign-ins immediately.
On November 19β20, 2026, Microsoft disclosed and mitigated a backend security vulnerability in the Microsoft Entra Connect Health cloud API. While Microsoft resolved the flaw server-side with zero customer patching needed, the operational risk is just beginning: threat actors now hold clean lists of verified Microsoft 365 administrator email addresses paired with exact tenant names, Tenant IDs, and license tiers.
Combined with active credential-harvesting campaigns exploiting November's Exchange Online outage (EX1550543), every organization should treat privileged admin accounts as high-priority spear-phishing targets this week.
This response runbook provides a live-tested Microsoft Graph PowerShell audit script to inventory all active privileged role holders, verify whether each admin has phishing-resistant authentication methods registered, and inspect recent admin sign-ins for anomalies.
1. Live-Tested PowerShell Audit: Inventory Privileged Admins & Check FIDO2 / Passkey Readiness
Run this read-only Microsoft Graph script to list every active directory role holder in your tenant, check whether they have a phishing-resistant method (FIDO2 / Passkey / Windows Hello for Business / CBA) registered, and flag high-risk gaps:
<#
.SYNOPSIS
Audit-PrivilegedAdminsPhishingResistance.ps1
Live-tested on the LAB 365 Dev Tenant using Microsoft Graph SDK v2.
#>
Connect-MgGraph -Scopes "Directory.Read.All", "UserAuthenticationMethod.Read.All", "AuditLog.Read.All" -NoWelcome
$roles = Get-MgDirectoryRole
$report = [System.Collections.Generic.List[PSCustomObject]]::new()
foreach ($role in $roles) {
$members = Get-MgDirectoryRoleMember -DirectoryRoleId $role.Id
foreach ($m in $members) {
if ($m.AdditionalProperties['@odata.type'] -ne '#microsoft.graph.user') { continue }
$upn = $m.AdditionalProperties['userPrincipalName']
$methods = Get-MgUserAuthenticationMethod -UserId $m.Id -ErrorAction SilentlyContinue
$types = $methods | ForEach-Object { $_.AdditionalProperties['@odata.type'] -replace '#microsoft\.graph\.', '' }
$hasPhishingResistant = ($types -match 'fido2|windowsHelloForBusiness|x509Certificate').Count -gt 0
$report.Add([PSCustomObject]@{
RoleName = $role.DisplayName
UserPrincipalName = $upn
PhishingResistantMFA = $hasPhishingResistant
RegisteredMethods = ($types -join ", ")
})
}
}
$report | Sort-Object PhishingResistantMFA, RoleName | Format-Table -AutoSize
$report | Export-Csv -Path ".\Admin-PhishingResistance-Audit.csv" -NoTypeInformation -Encoding utf8
Verified Live Lab Role Snapshot (LAB 365 Dev Tenant):
Global Administrator : 7 member(s)
Purview Workload Content Admin : 3 member(s)
Attribute Definition Administrator : 2 member(s)
Attribute Assignment Administrator : 1 member(s)
Exchange Recipient Administrator : 1 member(s)
2. Hunt for Suspicious Admin Sign-Ins via Microsoft Graph
Check whether any privileged administrator account experienced failed sign-ins, unfamiliar IPs, or token anomalies over the past 14 days:
$since = (Get-Date).AddDays(-14).ToString("yyyy-MM-ddTHH:mm:ssZ")
$adminUpns = $report.UserPrincipalName | Select-Object -Unique
foreach ($upn in $adminUpns) {
$signIns = Get-MgAuditLogSignIn -Filter "userPrincipalName eq '$upn' and createdDateTime ge $since" -Top 25
$risky = $signIns | Where-Object { $_.Status.ErrorCode -ne 0 -or $_.RiskLevelDuringSignIn -notin @("none", "hidden") }
if ($risky) {
Write-Host "`n[!] Alert: $($risky.Count) failed/risky sign-in(s) for $upn" -ForegroundColor Yellow
$risky | Select-Object CreatedDateTime, AppDisplayName, IpAddress,
@{N='Country';E={$_.Location.CountryOrRegion}},
@{N='ErrorCode';E={$_.Status.ErrorCode}} | Format-Table -AutoSize
}
}
3. Four Mandatory Hardening Steps Following the Exposure
- Enforce Phishing-Resistant MFA for All Admin Roles: Deploy the built-in Conditional Access policy requiring Phishing-resistant MFA (FIDO2 / Passkeys / CBA) for all directory rolesβsee our Entra ID Passkey Registration Campaign Runbook.
- Eliminate Mailboxes on Dedicated Admin Accounts: Cloud admin accounts (
[email protected]) should hold zero Exchange Online license so they can never receive phishing emails in the first place. - Move Standing Admins to PIM (Just-In-Time): Keep permanent Global Administrators to 2 break-glass accounts; convert all day-to-day admins to PIM-eligible with justification and FIDO2 activation.
- Update Technical Contact Addresses: Review Microsoft 365 Admin Center → Settings → Org settings → Organization profile and route technical notifications to a monitored, Defender-protected distribution list with strict impersonation rules (see our Post-Outage Defender KQL Hunting Guide).
π¬ Reader Comments & Feedback
Did this runbook help, or did Microsoft change a cmdlet or UI menu? Share your feedback below.
Leave a Comment or Report an Update