On 24 September, Microsoft published MC1478465 to some tenants, announcing that Security Copilot is part of the Microsoft 365 E5/E7 plan. The message was published to the wrong tenants. Microsoft now states it didn’t reach its intended audience. In my opinion, the cause is probably related to the number of E5 or E7 licenses in your tenant.
*************
Updated 22 October 2026:
Microsoft has removed the message MC1478465 from the affected tenants. If the message was previously in your tenant, it’s no longer available.
Updated 9 November 2026:
Microsoft has now published the message MC1540324, stating that Security Copilot was provisioned on 4 November.
*************
You may have already noticed this case: Security Copilot wasn't auto-provisioned in your tenant, as communicated and documented.
If you received message MC1478465 and have Microsoft 365 E5 or E7 licenses in your tenant, you can verify this case easily.
- Open the Security Copilot portal at securitycopilot.microsoft.com with a Security Administrator.
- If you see the initial capacity setup, the auto-provisioning process didn't run, and the MC was published by mistake.
You cannot solve the situation.
Try opening a Microsoft support case to report the issue and attach the following information.
- Your tenant ID
- A copy of the initial Message Center post MC1478465 confirming your tenant should be eligible.
- A screenshot from your Microsoft 365 E5 and E7 license(s).
Someone from the product group may then manually start provisioning Security Copilot, but they may now reject the request after the updated Message Center post.
No comments yet