> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/vendor-specific-data-sources-and-connectors/microsoft/microsoft-security-automation-and-collection.md).

# Microsoft Security Automation and Collection

Use Microsoft Security Automation and Collection data with Cortex XSIAM.

{% hint style="warning" %}
**Important**

This connector is only available for tenants that onboarded after July 26, 2026. For tenants that onboarded before this date, use Marketplace to access the standalone integration. For more information, see [Marketplace](/cortex-xsiam/configure-cortex-xsiam/marketplace.md).
{% endhint %}

Integrate with Microsoft products.

This connector includes the following sub-capabilities (Marketplace integrations link to PAN DEV for more information):

* [Azure Security Center v2](https://xsoar.pan.dev/docs/reference/integrations/azure-security-center-v2): Unified security management and advanced threat protection across hybrid cloud workloads. This sub-capability is available with any active Cortex XSIAM or Cortex AgentiX license.
* [Azure Sentinel](https://xsoar.pan.dev/docs/reference/integrations/azure-sentinel): Microsoft Sentinel is a scalable, cloud-native solution that provides: Security information and event management (SIEM) Security orchestration, automation, and response (SOAR). This sub-capability is available with any active Cortex XSIAM or Cortex AgentiX license.
* [Microsoft 365 Defender](https://xsoar.pan.dev/docs/reference/integrations/microsoft-365-defender): Microsoft 365 Defender is a unified pre- and post-breach enterprise defense suite that natively coordinates detection, prevention, investigation, and response across endpoints, identities, email, and applications to provide integrated protection against sophisticated attacks. This sub-capability is available with any active Cortex XSIAM, Cortex Cloud, Cortex Cloud Runtime Security, Cortex XDR, or Cortex AgentiX license.
* [Microsoft Defender Advanced Threat Protection](https://xsoar.pan.dev/docs/reference/integrations/microsoft-defender-advanced-threat-protection): Microsoft Defender for Endpoint (previously Microsoft Defender Advanced Threat Protection (ATP)) is a unified platform for preventative protection, post-breach detection, automated investigation, and response. This sub-capability is available with any active Cortex XSIAM or Cortex AgentiX license.
* [Microsoft Defender for Cloud Apps Event Collector](https://xsoar.pan.dev/docs/reference/integrations/microsoft-defender-for-cloud-apps-event-collector): This sub-capability is available with any active Cortex XSIAM license.
* [Microsoft Defender for Cloud Event Collector](https://xsoar.pan.dev/docs/reference/integrations/microsoft-defender-for-cloud-event-collector): XSIAM collector for Microsoft Defender for Cloud alerts. This sub-capability is available with any active Cortex XSIAM license.
* [Microsoft Graph](https://xsoar.pan.dev/docs/reference/integrations/microsoft-graph): This sub-capability is available with any active Cortex XSIAM, Cortex Cloud Posture Security, Cortex Cloud, Cortex Cloud Runtime Security, Cortex XDR, or Cortex AgentiX license.
* [MicrosoftCloudAppSecurity](https://xsoar.pan.dev/docs/reference/integrations/microsoft-cloud-app-security): Microsoft Cloud App Security is a multimode Cloud Access Security Broker (CASB). It provides rich visibility, control over data travel, and sophisticated analytics to identify and combat cyber threats across all your cloud services. Use the integration to view and resolve alerts, view activities, view files, and view user accounts. This sub-capability is available with any active Cortex XSIAM or Cortex AgentiX license.
* [MicrosoftDefenderThreatIntelligence](https://xsoar.pan.dev/docs/reference/integrations/microsoft-defender-threat-intelligence): Use the Microsoft Defender Threat Intelligence integration to query enriched threat intelligence data such as articles, threat actor profiles, WHOIS records, and host-related infrastructure. This sub-capability is available with any active Cortex XSIAM or Cortex AgentiX license.
* [O365 Defender SafeLinks](https://xsoar.pan.dev/docs/reference/integrations/o365-defender-safe-links): Provides URL scanning and rewriting of inbound email messages in mail flow, and time-of-click verification of URLs and links in email messages and other locations. This sub-capability is available with any active Cortex XSIAM, Cortex Cloud, Cortex Cloud Runtime Security, Cortex XDR, or Cortex AgentiX license.

To configure this connector, follow the steps outlined in the configuration wizard.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/cortex-xsiam-data-sources/vendor-specific-data-sources-and-connectors/microsoft/microsoft-security-automation-and-collection.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
