> 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/xsoar-migration-guide/cortex-xsoar-8-saas-migration/migrate-from-cortex-xsoar-6-to-cortex-xsoar-8-saas-using-the-pre-migration-and-migration-wizard/step-3.-run-user-acceptance-tests-uat-using-the-migration-wizard/integration-instance-configuration-changes.md). # Integration Instance Configuration Changes Integration instances are copied to Cortex XSOAR 8. During the UAT phase, to avoid any conflicts, the following are disabled: * Integration instances that send emails or other notifications (such as Slack or MS Teams) * Long-running integration instances * Fetching for integration instances * Mirroring for integration instances is ignored, and mirroring capability is disabled To test your integrations, temporarily enable them to verify connectivity and that mail configurations work properly. You should disable integrations after testing. For integrations that use external communication, such as sending emails, verify that you have added the Cortex XSOAR 8 IP Addresses to your firewall before testing. Both sets of IP addresses (Cortex XSOAR 6 and Cortex XSOAR 8) should remain in your firewall's allow list until migration is complete. {% hint style="info" %} ### Note * Integration instances are still active on the Cortex XSOAR 6 instance and may be affected by any action you take using integration instances in Cortex XSOAR 8. Integration instances created in Cortex XSOAR 8 during the UAT phase remain after the switchover date. If an integration instance differs between Cortex XSOAR 6 and 8 and you resync data at the switchover date, the Cortex XSOAR 6 values replace the Cortex XSOAR 8 values. If you do not resync data, the values in Cortex XSOAR 8 remain. * Integrations using deprecated content may not be migrated. You should update the deprecated content in Cortex XSOAR 6 before the start of the UAT phase so that the integration instance is migrated. For example, the Demisto REST API should be replaced by the Core REST API. If you do not do so, in Cortex XSOAR 8, update the content from Marketplace, and then create the integration instance. * If you have a custom (BYOI) integration that receives incoming traffic enabled on a custom port, your environment cannot be migrated at this time. {% endhint %} **Reconfigure integrations** The following integrations need to be reconfigured by updating the URL and updating the client that accesses them to be URL-based only. If you use an IP for access, you must use an engine. | Integration | Description | Comments | | ---------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | SAML | SAML authentication is part of the Cortex XSOAR platform. |

Note

As a part of the migration, the SAML integration is converted to the SSO settings on the platform level. In Cortex XSOAR 8, you need to Configure Single Sign-On Using SAML 2.0.

| | LDAP Authentication | Available in Cortex XSOAR 6. Currently not available in Cortex XSOAR 8. | | | Microsoft Teams | To use the rerouting configuration in Cortex XSOAR 8, you must use the Microsoft Teams content pack 1.4.43 or higher, and recreate the [Demiso Bot in Microsoft Teams](https://xsoar.pan.dev/docs/reference/integrations/microsoft-teams#create-the-demisto-bot-in-microsoft-teams). | For more information about Microsoft Teams and how to reconfigure it, see [Microsoft Teams](https://xsoar.pan.dev/docs/reference/integrations/microsoft-teams). | | [DUO](https://xsoar.pan.dev/docs/reference/integrations/duo#two-factor-authentication-with-duo-v31-and-up) | Not supported. | | **Core Rest API Integration** If you are using the [Core REST API](https://xsoar.pan.dev/docs/reference/integrations/core-rest-api) integration, review and test the integration instance (go to **Settings & Info** → **Settings** → **Integrations** → **Instances**, search for Core REST API, and click the **Settings** button). * In the **Core Server URL** field, the host address was modified to your Cortex XSOAR 8 FQDN. * In the **API Key** field: API keys are not migrated during the UAT. During the switchover, a new API key is generated, matching the permissions in the Cortex XSOAR 6 instance. If you would like to test the integration during the UAT, you will need to generate a new API key and configure the instance to use it. To ensure it is working correctly, test the integration instance. {% hint style="info" %} ### Tip We recommend testing this integration instance during the UAT phase. {% endhint %} --- # 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/xsoar-migration-guide/cortex-xsoar-8-saas-migration/migrate-from-cortex-xsoar-6-to-cortex-xsoar-8-saas-using-the-pre-migration-and-migration-wizard/step-3.-run-user-acceptance-tests-uat-using-the-migration-wizard/integration-instance-configuration-changes.md?ask=&goal= ``` `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.