One view of a hybrid Microsoft estate: on-premises Exchange, Entra and Azure Arc
CVE-2025-53786 showed how an on-premises Exchange server can reach Microsoft 365. How hybrid SMBs and public bodies can see and govern both halves in one place.
One server, two environments
On August 7, 2025, CISA issued Emergency Directive 25-02 for CVE-2025-53786, a flaw in Microsoft Exchange hybrid configurations. CISA described it as a post-authentication vulnerability that “allows an attacker to move laterally from on-premises Exchange to the M365 cloud environment.” An attacker first needed administrative access to the on-premises Exchange server. From there, the trust that lets the on-premises server and Exchange Online work together could be turned against the cloud tenant.
Federal agencies had until 9:00 AM EDT on Monday, August 11, 2025 to act. The steps CISA listed are a useful map of what a hybrid organization has to keep track of:
- Run Microsoft’s Exchange Server Health Checker to inventory every Exchange server and its update level
- Disconnect servers that could not take the April 2025 hotfix updates, including end-of-life servers
- Install the latest cumulative update and the April 2025 hotfix, which adds support for a dedicated Exchange hybrid application in Entra ID
- Move from the old shared service principal to that dedicated application, then reset the shared principal’s credentials
CISA also highly recommended disconnecting the last Exchange server after moving to Exchange Online.
Two months later, on October 14, 2025, support for Exchange Server 2016 and 2019 ended. Microsoft offered an optional six-month Extended Security Update program for organizations still finishing their migration.
Why this is a hybrid problem, not an Exchange problem
Many small businesses, school districts, towns and counties run this way: Microsoft 365 for mail and files, Entra ID for sign-in, and a handful of servers that never moved. A file server, a line-of-business application on Windows Server, a hybrid Exchange server kept for management, a domain controller synchronizing to Entra.
Each half usually has its own owner and its own tools. The cloud tenant has secure score, Conditional Access and alerts. The servers in the closet are patched by whoever remembers, and are often invisible from the cloud console. The Exchange flaw sat exactly in the seam between the two: a server most people had stopped thinking about, holding a trust relationship with the tenant everyone was watching.
The goal people describe as a “single pane of glass” is really a governance goal. One list of every server and cloud resource, one set of rules they are measured against, and one place where someone is accountable for the gaps.
What Microsoft’s tools can and cannot show you
Azure Arc is Microsoft’s way of bringing servers outside Azure into the same management plane. In Microsoft’s words, Arc-enabled servers let you “manage Windows and Linux physical servers and virtual machines hosted outside of Azure, on your corporate network or with another cloud provider.” Each connected machine becomes an Azure resource with its own resource ID, so it can be tagged, grouped and governed like a cloud resource.
Once a server is connected, Microsoft’s documentation lists what it can use:
- Govern: Azure Policy and machine configuration, to check settings against a standard
- Protect: Microsoft Defender for Endpoint through Microsoft Defender for Cloud, and Microsoft Sentinel
- Configure: Azure Update Manager for operating system updates, and Azure Automation
- Monitor: Azure Monitor Agent and VM insights
Two limits matter. Arc is for machines outside Azure; Azure virtual machines are managed natively instead. And a connected server that stops sending its heartbeat for 45 days can move to an expired state, after which it cannot be managed through Arc until an administrator disconnects and reconnects it. A view is only as good as the agents reporting into it.
Arc is one option. Many SMBs already have an MSP’s remote management tool on every server, and that can be the inventory instead. What matters is that one list covers both halves and somebody reviews it.
Pointers for a hybrid estate
- Write down every server that talks to the tenant. Entra Connect servers, hybrid Exchange servers, AD FS, and anything holding an app registration or certificate trusted by Entra. These are the servers where an on-premises compromise becomes a cloud compromise.
- Retire what you can. If mailboxes are in Exchange Online and the last Exchange server is kept only out of habit, plan its removal with your MSP. One fewer bridge is one fewer thing to patch.
- Check the hybrid configuration itself, not just the patch level. The April 2025 fix only helped organizations that also moved to the dedicated hybrid application.
- Put the servers on the same scorecard as the tenant. Whether through Arc and Defender for Cloud or your MSP’s tooling, measure patch level, endpoint protection and configuration for the closet servers with the same rigor as the cloud.
- Track end-of-support dates as risks with owners. Exchange 2016 and 2019 were a known date for years. Windows Server versions and line-of-business applications have dates too.
Who does what
Leadership, or for public bodies the IT director and the governing board, decides which on-premises systems stay and accepts the risk of each one in writing. Your IT team or MSP connects servers to the chosen management plane, applies updates and fixes the hybrid configuration. Application owners confirm what each remaining server is for and when it can be retired.
Where outside help fits
Hybrid Microsoft estates get complicated because they grow one decision at a time, and each tool shows only its half. CyberIntelPro leads the architecture work: which servers bridge to the cloud, what the target design looks like, and what your MSP or IT team must change, in what order. Hudson Valley CISO governs it over time, with a risk register of the systems you keep and the owners who sign off on them. Security Medic frames the same work for towns, school districts and utilities, including briefings for boards and councils.
Want to talk it through? Book a free 30-minute call with Security Medic Consulting.
Sources
- CISA, ED 25-02: Mitigate Microsoft Exchange Vulnerability, August 7, 2025.
- Microsoft Exchange Team Blog, Support for Exchange Server 2016 and Exchange Server 2019 ends today, October 14, 2025.
- Microsoft Exchange Team Blog, Announcing Exchange 2016 / 2019 Extended Security Update program, updated April 15, 2026.
- Microsoft Learn, Azure Arc-enabled servers overview, February 26, 2026.