June 8 – June 15, 2026

Act by

• 15 Jun 2026 — Older Sentinel repositories (content-as-code) Source Control API versions become unsupported after today. CI/CD tooling that creates or manages repo connections must move to API version 2025-09-01, 2025-06-01, or 2025-07-01-preview; existing connections keep operating. If your team deploys analytics rules and playbooks from GitHub or Azure DevOps, confirm the pipeline is on a supported API version. (Microsoft Learn)
• 1 Jul 2026 — The advanced-hunting AIAgentsInfo table retires and is replaced by AgentsInfo, a unified schema covering all agent types (Copilot Studio, Microsoft Foundry, Microsoft 365 Copilot, third-party, and endpoint-discovered agents). AIAgentsInfo stays accessible until this date. Update any custom detections, hunting queries, or workbooks that reference the old table before it goes away. (Microsoft Learn — What's new in Defender XDR)
• 1 Jul 2026 — Account-entity naming standardization takes effect. Sentinel resolves Account Name by precedence and defaults to the UPN prefix (the part before "@"). Analytics rules, automation rules, playbooks, workbooks, and hunting queries that rely on strict full-UPN matching break unless updated — regardless of whether you have migrated to the Defender portal. Audit your queries for hard-coded full-UPN account matches now. (Microsoft Learn)
• 1 Jul 2026 — Unified RBAC migration groundwork before the Defender-portal cutover (heads-up). Legacy Sentinel Azure roles do not carry into the Defender portal, so plan URBAC migration to avoid permission gaps; Workspace Manager deprecation pushes MSSPs toward CI/CD via GitHub or Azure DevOps. (Microsoft Learn)

What changed

June Patch Tuesday landed on 9 June 2026 and was Microsoft's largest ever, addressing roughly 200 CVEs (tracker counts range 198–208) with about three dozen rated Critical — the Critical set is dominated by remote-code-execution bugs, including multiple in Office and eleven in the Remote Desktop client. Microsoft flagged six zero-days: five publicly disclosed before patch day — a Windows Collaborative Translation Framework (CTFMON) elevation-of-privilege bug (CVE-2026-45586, "GreenPlasma"), two BitLocker security-feature bypasses (CVE-2026-45585 "YellowKey" and CVE-2026-50507 "Bitskrieg"), an HTTP.sys HTTP/2 denial-of-service flaw (CVE-2026-49160, "HTTP/2 Bomb"), and a Cloud Files driver EoP — plus at least one exploited in the wild. Trackers disagree on which: BleepingComputer cites an Exchange Server spoofing bug (CVE-2026-42897) that runs arbitrary JavaScript in Outlook Web Access when a crafted mail is opened, while Tenable flags a Defender for Endpoint EoP (CVE-2026-41091, "RedSun") later added to CISA's KEV. SharePoint took 23 fixes and Exchange 7, and there is a separate critical HTTP.sys RCE (CVE-2026-47291) alongside the disclosed DoS. On a Microsoft estate the practical work is confirming Defender-delivered updates roll out through MDE, watching endpoint patch compliance in vulnerability management, and prioritizing internet-facing OWA/Exchange, SharePoint, and HTTP.sys hosts. (BleepingComputer)

Defender XDR added threat-intelligence enrichment on entity pages (preview). IP address, domain, URL, and file entity pages now carry a Threat Intelligence Insights tab that surfaces Microsoft Threat Intelligence data — reputation scores, attributed threat reports, infrastructure relationships, and sandbox analysis — inline in the investigation. For an analyst this removes a context switch: the reputation and attribution lookup you would otherwise run in a separate TI tool now sits on the entity you are already pivoting through. (Microsoft Learn — What's new in Defender XDR)

Four advanced-hunting schema tables reached general availability in Defender XDR this month: DisruptionAndResponseEvents (automatic attack-disruption block and policy events) and the multicloud trio CloudAuditEvents, CloudDnsEvents, and CloudProcessEvents fed from Defender for Cloud. GA means these are stable enough to build production detections and scheduled hunts on rather than one-off queries — disruption events let you audit what attack disruption actually did, and the cloud tables extend KQL hunting into audit, DNS, and process activity across cloud workloads. (Microsoft Learn — What's new in Defender XDR)

In Defender Vulnerability Management the reworked exposure score went GA, and a new Microsoft Secure Score recommendation, "Reduce unnecessary inbound internet exposure on internet-facing devices," shipped alongside it. The new score model factors in exploit-prediction data (EPSS) and asset context such as internet-facing status and criticality, so prioritization tilts toward vulnerabilities that are both likely to be exploited and on assets that matter. Paired with the internet-exposure recommendation, this gives a SOC a sharper worklist the same week a record Patch Tuesday lands with internet-facing HTTP.sys and Exchange bugs to triage. (Microsoft Learn — What's new in Microsoft Defender for Endpoint)

Microsoft brought Selective Response Actions to GA in Defender for Endpoint. During onboarding you can now scope which high-impact response actions (isolation, live response, and similar) are permitted on Tier-0 systems and other high-value assets, so an automated or analyst-triggered containment cannot inadvertently take down a domain controller or critical server while still allowing full protection elsewhere. Useful guardrail if your automation or SOAR playbooks fire response actions broadly. (Microsoft Learn — What's new in Microsoft Defender for Endpoint)

On the identity side, Entra's June release notes extend Conditional Access to AI-agent user accounts (preview). Admins can now target individual agents or dynamically group them via Custom Security Attributes, gate on Agent Risk, and require compliant devices or trusted network conditions for agents running on managed endpoints (including Windows 365 for Agents). This carries the same Zero Trust controls SOC and IAM teams already apply to human accounts onto autonomous agents — the population that connectors like the Sentinel Agent Identities asset connector are now surfacing for investigation. (Microsoft Learn — What's new in Microsoft Entra)

Entra also made tenant Backup and Recovery generally available. Always-on by default, it takes a daily snapshot of critical directory objects — users, groups, applications, service principals, managed identities, Conditional Access policies, named locations, agent IDs, and auth/authorization policy — with 7-day retention on P1/P2, plus difference reports and recovery jobs. For a SOC this is a concrete recovery path after a malicious or accidental directory change (rogue CA policy edits, mass group tampering): you can diff against a known-good snapshot and restore rather than rebuild by hand. (Microsoft Learn — What's new in Microsoft Entra)

Two smaller Entra hardening changes shipped the same month: jailbreak/root detection in Microsoft Authenticator went GA (secure by default, no admin config — rooted or jailbroken devices are blocked from adding or using work/school accounts), and AD group enforcement entered preview, letting you designate provisioned AD groups so membership changes are only accepted through the Entra provisioning service and out-of-band edits are blocked. Both close small abuse paths — a tampered authenticator device and drift-based privilege changes in on-prem groups. (Microsoft Learn — What's new in Microsoft Entra)

Microsoft Sentinel's June updates added two hunting-side previews. Behavior results can now be linked to incidents in advanced hunting: query results from the UEBA BehaviorInfo table can be attached to a new or existing incident, with alert metadata and entities auto-populated from the behavior record — a direct path from a UEBA anomaly to an actioned incident. Separately, a graph tool collection in the Sentinel MCP server lets you explore relationships across identities, devices, threats, and signals as a graph to spot coverage and configuration gaps. (Microsoft Learn)

Worth knowing

This June Patch Tuesday is worth treating as a scheduling event, not just a checklist. At a record ~200 CVEs it is too large to push in one wave, so rank by exposure: internet-facing first (the exploited Exchange OWA spoofing bug and both HTTP.sys flaws, the DoS and the separate critical RCE), then the widely reachable server-side bugs (23 SharePoint CVEs, the rest of Exchange), then client-side RCE in Office and the eleven Remote Desktop client fixes that need a crafted server or relay to land. The BitLocker bypasses (YellowKey, Bitskrieg) matter most for physically exposed or lost devices. Because Microsoft ships several of these through Defender-delivered channels, verify rollout in MDE and use the new EPSS-plus-context exposure score to sequence the long tail rather than patching alphabetically. (MSRC Security Update Guide)

Outside Patch Tuesday this was a quiet week for dated announcements — the Sentinel, Defender XDR, and Entra blogs published nothing between 9 and 15 June, and the month's feature wave (the Agent Identities asset connector, ASIM's schema additions, and non-human-identity protection in Defender) begins landing from 16 June, so those fall into the following week's brief. The items above come from the June release notes, which are month-granular rather than day-stamped. (Microsoft Learn)

Keep the Defender-portal migration on your radar while the week is calm. Microsoft Sentinel in the Azure portal is slated to be supported in the Defender portal only starting July 2026, with remaining Azure-portal customers automatically redirected — now weeks, not months, away. Combined with the 1 July account-entity naming change and the unified RBAC gap noted in Act by, the practical message is that detection logic, automation, and role assignments all need a pass before the cutover; a quiet week is a good time to run that audit rather than doing it under redirect pressure. (Microsoft Learn)