Microsoft’s scheduled Nov. 16, 2026, changes to default trust for eMudhra root certificates put update delivery on the enterprise operating agenda. The immediate question is not simply which certificate authorities a platform trusts, but how that decision reaches the software a business runs.

The company’s Nov. 10 Trusted Root Program announcement says affected certificates will lose default trust once the updates reach a device. It warns that dependent certificates may fail validation unless another trusted certification path exists. That is a conditional compatibility consequence, not evidence of a widespread outage.

Product schedules are not endpoint confirmations

Microsoft’s Nov. 12 cross-product schedule distinguishes delivery routes. Windows devices that can reach its automatic certificate-update endpoint are to receive the trust changes automatically. Edge and WebView2 use a separate PKI Metadata component; Microsoft says those applications check for updates every 10 hours and shortly after launch.

The same schedule makes some changes dependent on other software releases. It lists .NET container updates as upstream certificate packages change, while placing the SDK’s trust-bundle update in December. A shared starting date therefore does not mean every application receives an identical update at once.

Microsoft also flags Windows devices that do not receive automatic trust updates. Its guidance says organizations managing those systems need an update process that delivers the changed certificate lists, rather than assuming online-device servicing covers them.

Linux packages and images need separate attention

The Azure Linux team’s Nov. 11 implementation notice describes updated certificate packages scheduled for Nov. 16. For image-based deployments, it identifies virtual-machine or container images tagged 20261116 or later. The document separates updating packages from selecting a refreshed image rather than treating either route as proof of the other.

For operators, that distinction turns a vendor calendar into a deployment-record question: which package or image is actually in use? The notice supplies a release marker, not an inventory of any customer’s running systems.

Firefox illustrates another update boundary

Mozilla’s October explanation provides historical context. It described Firefox’s centrally distributed OneCRL blocklist separately from the trusted certificate list in NSS. Mozilla said the NSS change also mattered for applications using its trust store without receiving Firefox’s OneCRL updates.

That account does not establish a new Firefox rollout on Nov. 16. It shows why an organization cannot infer the state of every certificate-dependent application from one browser’s update status. Microsoft’s current schedule and Mozilla’s earlier explanation describe different delivery mechanisms, not a single synchronized switch.