Microsoft Purview will integrate with ChatGPT Enterprise to enable discovery and governance of AI interactions. Organizations can use Purview solutions to manage sensitive information within these interactions. Public Preview begins mid-December 2024, with General Availability details to follow. Preparation requires an Azure account, Enterprise Purview account, and ChatGPT Enterprise plan.
Organizations can use the unified Microsoft Purview portal to connect Purview to their ChatGPT Enterprise workspaces, enabling them to discover, collect, and store user interactions in the scope of Purview capabilities and policies.
With Purview solutions, organizations can effectively discover and govern these interactions. For instance, you can review all AI interactions and sensitive information detected in the Data Security Posture Management (DSPM) for AI solution. Also, you can use eDiscovery, Data Lifecycle Management (DLM), Communication Compliance (CC), and Insider Risk Management (IRM) solutions to govern this data.
This message is associated with Microsoft 365 Roadmap ID 401125.
When this will happen:
Public Preview: We will begin rolling out mid-December 2024 and expect to complete by mid-January 2025.
We will communicate the plan for General Availability in a future post.
How this will affect your organization:
When this feature is available in the Purview portal, you can use the new connector in the Purview Data map called ChatGPT Enterprise to connect to your ChatGPT workspace.
This change is available for configuration by default.
What you need to do to prepare:
To get started, you will need a Microsoft Azure account with an active subscription, an active Enterprise Purview account, and a ChatGPT Enterprise plan for your organization. This integration also requires you to have configured single sign-on of Microsoft Entra ID with your ChatGPT Enterprise workspace.
If you haven't started using it yet, we recommend you familiarize yourself with the Purview Data map.
Learn more:
This rollout will happen automatically by the specified date with no admin action required before the rollout. Review your current configuration to determine the impact for your organization. You may want to notify your admins about this change and update any relevant documentation.