Brief: Standalone and Embedded Copilot for Security Experiences

The Standalone and Embedded experiences for Copilot for Security cater to different usage scenarios

The Standalone and Embedded experiences for Copilot for Security cater to different usage scenarios. Here’s some suggestions for where each may make sense in your organization.

Standalone Experience:

• Accessed through a dedicated portal.

• Ideal for users who prefer a focused environment dedicated to security operations.

• Offers a comprehensive view of security insights and actions in one place.

• The standalone experience better enables organizations using non-Microsoft security tools to run Copilot for Security alongside.

Embedded Experience:

• Integrated within other Microsoft security products.

• Suitable for users who want to leverage Copilot capabilities without leaving their familiar product environment.

• Provides context-specific insights and actions related to the product it’s embedded in.

When to Use Each:

• The Standalone experience is best when you need a centralized, immersive portal for security operations.

• The Embedded experience may be used when you want to enhance your workflow within existing Microsoft security products with Copilot’s AI capabilities.

---

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]