UPDATE July 14, 2026: Please see our release blog post for July 2026 Security Update, which, once installed, removes our recommendation to keep CVE-2026-42897 mitigation in place: Released: July 2026...
in our case (Exchange SE), the auto applied mitigation changed the web.config for the owa virtual directory in a way that it leaves the URL-Rewrite Module inaccessible from the IIS Manager (for the owa tree). Trying to verify the settings (IIS-Manager -> Server -> Sites -> Default Website -> owa -> URL Rewrite) results in this Error-Message:
Hitting OK shows a blank configuration of URL Rewrite module.
Further inspections shows, that calendar sharing via .html and .ics in OWA does not work any more and results in Error 500 when clicking the links to the html/ics documents in OWA.
Checking the file in the error message (web.config) the structure of this XML-File looks like this:
Question to the MS Team: is this correct and is the mitigation still working (even though IIS-Manager complains)? Or is action required here?
For me this looks like the rewrite rule was inserted in the wrong place. It looks like these lines between the open and closing tags of "system.webServer" on the bottom of the file should go below configuration/location/system.webServer (and the indentation of the added lines reinforces the assumption):
thank you for reaching out to us, you're correct. We observed the same as well, the script may be adding a duplicate section within the web.config file in "<ExchangeInstallPath>\v15\frontend\httpproxy\owa" where a duplicate entry for the section “<system.webserver>” was added at the end of the file, causing HTTP 500 errors while accessing ICS-published calendars and calendar.html like:
The duplicate <system.webserver> section can be found near the end of the web.config file, like:
Moving the "<rewrite>" section back to to the right location at the beginning of the file like:
and removing the duplicates “<system.webserver>” and “</system.webserver>” from the part at the end followed by an IISRESET fixes the issue.
This is still a workaround, please expect a full-fledged security update as stated in the blog article above addressing this known issue shortly.
Thank you for bringing this issue to our attention.