We are excited to announce the general availability of Exchange Server Subscription Edition (SE). This release continues Microsoft’s long tradition of enabling customers to provide enterprise email s...
Updated Aug 06, 2025
Version 5.0
Blog Post
Upgraded 2 servers from fully patched Exchange 2019 to Exchange SE. ECP and OWA have HMA authentication configured. After the update, both servers have broken ECP and unhealthy ECP.Proxy and MRS.Proxy healthchecks. In logs - 401 Unauthorized. The same was on the previous CU for Ex2019.
I recreated the ECP virtual directory to fix (probably switching to forms and then back to HMA will fix this issue too). But it is frustrating...
What I did to fix my servers:
Get-EcpVirtualDirectory -Server XXX | Remove-EcpVirtualDirectory
New-EcpVirtualDirectory -Server XXX -InternalUrl "https://XXX/ecp" -ExternalUrl "https://XXX/ecp"
Get-OwaVirtualDirectory -Server XXX | Set-OwaVirtualDirectory -AdfsAuthentication $false -BasicAuthentication $false -FormsAuthentication $false -DigestAuthentication $false
Get-EcpVirtualDirectory -Server XXX | Set-EcpVirtualDirectory -AdfsAuthentication $false -BasicAuthentication $false -FormsAuthentication $false -DigestAuthentication $false
Get-EcpVirtualDirectory -Server XXX | Set-EcpVirtualDirectory -OAuthAuthentication $true
Get-OwaVirtualDirectory -Server XXX | Set-OwaVirtualDirectory -OAuthAuthentication $true
iisreset
Get-HealthReport XXX
- LukasSMSFT
Microsoft
This is a known issue with Exchange Server 2019 CU15, as documented in the “Known Issues” section of the Released: 2025 H1 Cumulative Update for Exchange Server | Microsoft Community Hub blog post.
Since Exchange 2019 CU15 is code-equivalent to Exchange Server SE RTM, we were unable to address this issue within that release. However, a fix is planned and will be released in future update.
