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 wrongly published in some tenants. Microsoft now states that it did not reach its intended audience. In my opinion, the cause is probably related to the number of E5 or E7 licenses in your tenant.
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 issue.
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