Microsoft Purview

Question

We have an active Microsoft Purview account, and diagnostic settings are configured. However, the Microsoft Purview data connector is not currently connected. Could you please let us know the reason for this? Additionally, the connector does not display any option or link to establish the connection.

Answer 1

Hi Adele Vance,
If your Purview account already has Diagnostic Settings configured but the Microsoft Purview data connector does not show a “Connect” option, this is expected behavior in many scenarios.

Diagnostic settings already export the data
In Purview, logs and audit events are exported through Azure Diagnostic Settings to supported destinations such as Log Analytics Workspace, Event Hub, or Storage Account. Once diagnostic settings are configured, data is automatically streamed and a separate connector activation is not required.

Some integrations rely on diagnostics instead of manual connectors
Services such as Microsoft Sentinel consume Purview logs that are already being exported through diagnostic settings. Because of this architecture, the portal may not display a separate “Connect” option for the connector.

Permissions may affect connector visibility
The connector configuration option may not appear if the user does not have the required roles such as Global Administrator, Purview Administrator, or Data Connector Administrator.

Please verify the following:

Navigate to Purview Account → Monitoring → Diagnostic Settings and confirm logs are enabled.

Ensure logs are being sent to the configured destination (Log Analytics / Event Hub / Storage).

1. Verify that the user configuring the connector has the required administrative permissions.

Reference links:
https://learn.microsoft.com/purview/data-gov-classic-audit-logs-diagnostics
https://learn.microsoft.com/azure/sentinel/data-connectors/microsoft-purview
https://learn.microsoft.com/purview/compliance-manager-connectors

Hope this helps. If you have any follow-up questions, please let me know. I would be happy to help.

Please do not forget to "up-vote" wherever the information provided helps you, as this can be beneficial to other community members.

Answer 2

The Microsoft Purview data connector in Microsoft Sentinel shows as not connected when one or more of the required prerequisites or configuration steps for ingestion are not fully completed.

Based on the documented integration flow, verify the following points:

1. Prerequisites and solution installation
   • Ensure a Microsoft Sentinel workspace is onboarded and a Microsoft Purview account is created and onboarded.
   • Confirm that the Microsoft Purview solution is installed in the Log Analytics workspace used by Microsoft Sentinel. The solution includes the data connector, workbook, and analytics rules. If the solution is not installed, the connector experience and connection options will not be fully available.
2. Diagnostic settings from Purview to the Sentinel workspace
   • In the Azure portal, open the Microsoft Purview account and go to Diagnostic settings.
   • Confirm there is an active diagnostic setting that:
     • Selects the DataSensitivityLogEvent log category.
     • Uses Send to Log Analytics workspace as the destination.
     • Points to the same subscription and Log Analytics workspace that Microsoft Sentinel is using.
   • If diagnostic settings are not configured exactly this way, the connector will not receive data and will appear as not connected.
3. Run a Purview scan to generate data
   • Diagnostic settings send events only after a full scan is run, or when changes are detected during an incremental scan.
   • In Microsoft Purview, run a full scan of the relevant data sources. After the scan completes, wait 10–15 minutes for logs to start appearing in Microsoft Sentinel.
   • If no scans have been run, or scans have not completed, the connector will not show incoming data and may appear as not connected.
4. Permissions
   • The user configuring the connector must have:
     • Microsoft Purview Owner or Contributor on the Purview account (to configure diagnostic settings and the connector).
     • Microsoft Sentinel Contributor on the Sentinel workspace (to enable the data connector, view the workbook, and create analytics rules).
   • If these roles are missing, the connector UI may not show options or links to establish or manage the connection.

If all of the above are correctly configured and the solution is installed, the connector should show as connected once data starts flowing from Purview via diagnostic settings. The absence of a “Connect” option typically indicates either the solution is not installed in Sentinel or the user lacks the required roles to manage the connector.

---

References:

• Integrate Microsoft Sentinel and Microsoft Purview
• Start ingesting Microsoft Purview data in Microsoft Sentinel