Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 272/272 feeds/APIs · 469/469 docs · 7/9 advisories · checked 14:23 UTC Customize Public modeDiscuss ChangeIntel on Discord

Secure Boot certificate deployment guide and tools

From Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

Microsoft asks admins to prevent or fix an issue. Read what it asks below and check the linked documentation; whether your tenant is affected is not known here.

What the notice says

Microsoft’s text, safely structured

Use the newly published guide and tools to start updating your organization’s expiring Secure Boot certificates. As the 2011 certificate authorities (CAs) start expiring in June 2026, 2023 CAs are required. Updated CAs allow Secure Boot to continue preventing malware early in the startup sequence. New resources are available for you to start monitoring, deploying, and troubleshooting Secure Boot CAs. These include the deployment playbook, new registry keys, Windows Event Log, and Windows Configuration System (WinCS) APIs.

When will this happen

  • The deployment guide, new registry keys, and WinCS are available today.
  • The 2023 Secure Boot CAs are rolling out gradually as part of Windows monthly updates starting with the October 2025 security update.
  • Additional tools will be available soon.
  • The 2011 CAs start expiring beginning in June 2026.

How this will affect your organization

Devices manufactured before 2012 and those that don’t already have new certificates need to be updated with the 2023 CAs. We recommend taking measures well before the 2011 CAs start expiring.

What you need to do to prepare

If your organization sends diagnostic data and lets Microsoft manage your updates, your devices will automatically get updated CAs with the monthly Windows updates. You can also opt in to let Microsoft determine high-confidence devices that will get these CAs first.

If you prefer to deploy these CAs yourself, follow the deployment playbook to monitor, deploy, and troubleshoot Secure Boot updates. You can use new registry keys, Windows Event Log, and WinCS to do so.

Additional information

  • Find the deployment playbook in the updated Secure Boot certificate updates: Guidance for IT professionals and organizations.
  • Learn how to use new registry keys to monitor, deploy, and troubleshoot Secure Boot CAs.
  • Learn how to use new Windows Configuration System (WinCS) APIs to deploy Secure Boot CAs.
  • Learn how to use Windows Event Log to monitor Secure Boot CA updates.
  • Bookmark Windows Secure Boot certificate expiration and CA updates as the landing page to the most up-to-date information.

What changed

Between archive captures, newest first

The archive supplies one version of this notice.

Learn more

Links from the notice and their documentation checks

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
  • 4 linked pages have not been read yet.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 27 Oct 14:23 UTC · 272 of 272 readable · 270 fully read · documentation 469/469 current