Microsoft has released Security Updates (SUs) for vulnerabilities found in:
Exchange Server Subscription Edition (SE)
Exchange Server 2019
Exchange Server 2016
SUs are available for the f...
Updated Jun 11, 2026
Version 3.0
Blog Post
I had a quick question about the note on scripts. We understand that some built‑in scripts may no longer work and are being moved to GitHub, and that deeper fixes may only come with a future Cumulative Update.
In our environment, we rely heavily on custom PowerShell scripts in addition to Microsoft-provided ones. To help us plan properly, could you please clarify the main reason behind this change? For example, is it due to security hardening, changes to the Exchange component, or a broader shift away from bundling scripts with the product?
We want to make sure we understand the potential impact early — if several scripts stop working after deployment, it could make day-to-day operations challenging.
Any guidance on what types of scripts might be affected, and how we can validate or adapt them in advance, would be very helpful.
Thanks again for your support.
Nino_Bilic
Microsoft
MicrosoftThe script discussion was in the context of CVE-2026-45583 - Security Update Guide - Microsoft - Microsoft Exchange Server Remote Code Execution Vulnerability which specifically mentions public folder scripts and to get them from here: https://aka.ms/PublicFolderScripts. We are not making changes to scripting generally speaking (that would break your scripts). For many of our own scripts, however, it can really makes sense to host them on GitHub and let them auto-update as that allows us to take care of whatever needs to be taken care of without having to wait on things like Cumulative Updates etc. or require people to install updates.