> 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-cloud-runtime-security/cortex-cloud-data-sources-and-connectors/cloud-posture-and-runtime-security-data-sources/how-to-onboard-microsoft-365.md).

# How to onboard Microsoft 365

**Overview**

You can add Microsoft 365 as a third-party data source in Cortex Cloud Data Security.

{% hint style="warning" %}

### Danger

* You have generated a Globally Unique Identifier (GUID), also known as a Universally Unique Identifier (UUID). You will need this ID for the tenant you want to use for the Microsoft 365 instance.
* In order to use Microsoft 365, you must be registered with Microsoft Azure.
  {% endhint %}

**Configuration**

1. Navigate to **Settings** → **Data Sources & Integrations**.
2. On the **Data Sources & Integrations** page, click **+ Add New**.
3. On the **Add Data Sources or Integrations** page, search for **Microsoft 365**, then hover over it and click **Add**.
4. On the **Microsoft 365** integration instance settings page, do the following:
   1. In the **Display Name** field, enter a name for your Microsoft 365 integration instance.
   2. In the **Tenant ID** field, enter a tenant ID.
   3. In the **Region** list, select a region.
5. Click **Next**.

**Authorization**

1. On the **Microsoft 365 Instance** screen, if you are an administrator, click the **click to authorize** link.
2. If you do not have administrator permissions, follow the instructions on screen and click **Close**.

The **Microsoft 365** instance should now appear on the **Data Sources** screen under **3rd Party Data Sources**.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-cloud-runtime-security/cortex-cloud-data-sources-and-connectors/cloud-posture-and-runtime-security-data-sources/how-to-onboard-microsoft-365.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.