Brief: Copilot for Security is Two Experiences but One Connected Service
Brief: Copilot for Security is Two Experiences but One Connected Service
Enabling Copilot for Security in an organization provides access to both experiences.
As I noted in a recent brief, Copilot for Security is available in two different experiences: Standalone and Integrated.
A question was raised during my Copilot for Security keynote at Experts Live in Denmark recently about since there are two different experiences, are they somehow still connected? It’s worth noting that Copilot for Security is an Azure service. In fact, the Azure portal is how it’s accessed to enable and configure in an organization’s tenant.
I recently hosted a couple polls, asking which experience people would prefer and so far, the majority are most excited about the integrated version. But despite there being two different experiences, they are connected. Evidence of this can be seen in the next image which shows the Copilot for Security prompt in the Defender console available immediately and accessible from the standalone version.
Enabling Copilot for Security in an organization provides access to both experiences and I get a sense that both will be utilized over time - most likely by different teams or types of roles in the organization.
Want to discuss this further? Hit me up on Twitter or LinkedIn]
[Subscribe to the RSS feed for this blog]
[Subscribe to the Weekly Microsoft Sentinel Newsletter]
[Subscribe to the Weekly Microsoft Defender Newsletter]
[Subscribe to the Weekly Azure OpenAI Newsletter]
[Learn KQL with the Must Learn KQL series and book]
[Learn AI Security with the Must Learn AI Security series and book]