> 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/data-security-documentation/cortex-data-security-data-sources-and-connectors/vendor-specific-data-sources-and-connectors/microsoft/microsoft-office-365/microsoft365-legacy/migrate-to-new-microsoft-365-connector.md).

# Migrate to new Microsoft 365 connector

Migrate from the legacy **Microsoft365** connector to the new [**Microsoft 365**](/data-security-documentation/cortex-data-security-data-sources-and-connectors/vendor-specific-data-sources-and-connectors/microsoft/microsoft-office-365/microsoft-365-new.md) connector to take advantage of improved performance, enhanced remediation capabilities, and unified Microsoft 365 configuration.

#### Why migrate? <a href="#why-migrate" id="why-migrate"></a>

By upgrading to the new connector, you benefit from:

* **Faster and more efficient scanning** with improved performance and reliability.
* **Enhanced remediation capabilities**, including:
  * Delete
  * Change public sharing
  * Quarantine
* **Microsoft Information Protection (MIP) label write support**, enabling automatic application of sensitivity labels directly from Cortex Cloud.
* **Unified Microsoft 365**, providing holistic security across identities, AI agents, security configurations, and Microsoft 365 applications such as Microsoft Teams, SharePoint, and OneDrive through a single configuration experience.

#### Migration steps <a href="#migration-steps" id="migration-steps"></a>

**Task 1. Remove the existing Microsoft365 Connector**

1. ​Remove your existing Microsoft 365 connector to prepare for the migration.
   * **Note:** Removing the connector clears the Microsoft 365 assets and objects previously discovered by the existing connector from the Data Security inventory. No data is deleted from your Microsoft 365 environment. The new connector automatically rediscovers and repopulates these assets during ingestion.
2. Wait approximately **24 hours** for the cleanup process to complete before proceeding to the next step.

**Task 2. Install the new Microsoft 365 Connector**

Install the new Microsoft 365 connector by following the configuration guide. For more information, see [Microsoft 365](/data-security-documentation/cortex-data-security-data-sources-and-connectors/vendor-specific-data-sources-and-connectors/microsoft/microsoft-office-365/microsoft-365-new.md).

**Task 3. Monitor Data Ingestion**

The new connector begins ingesting existing and new Microsoft 365 data using Microsoft APIs. Depending on the size of your environment, the initial synchronization may take **a few days to several weeks**. We recommend monitoring the ingestion progress with the **Palo Alto Networks team** until your environment reaches full coverage.


---

# 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/data-security-documentation/cortex-data-security-data-sources-and-connectors/vendor-specific-data-sources-and-connectors/microsoft/microsoft-office-365/microsoft365-legacy/migrate-to-new-microsoft-365-connector.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.