Description
The OneTrust connector for Microsoft Sentinel provides the capability to have near real time visibility into where sensitive data has been located or remediated across across Google Cloud and other OneTrust supported data sources.
- Declared status
- 1
- Declared author / publisher
- OneTrust
Declared sources
Metadata from the source file. No dependencies inferred from KQL.
Data types
Declared permissions
read and write permissions are required.
Workspace
Workspace
Microsoft Entra
Permission to create an app registration in Microsoft Entra ID. Typically requires Entra ID Application Developer role or higher.
Microsoft Azure
Permission to assign Monitoring Metrics Publisher role on data collection rule (DCR). Typically requires Azure RBAC Owner or User Access Administrator role
Connector instructions
Content published in the repository. Refer to the original file for all parameters.
1. Create ARM Resources and Provide the Required Permissions
This connector reads data from the tables that OneTrust uses in a Microsoft Analytics Workspace. If OneTrust's data forwarding option is enabled then raw event data can be sent to the Microsoft Sentinel Ingestion API.
Deploy OneTrust connector resources
2. Push your logs into the workspace
Use the following parameters to configure the your machine to send the logs to the workspace.
Tenant ID (Directory ID)
Entra App Registration Application ID
Entra App Registration Secret
Data Collection Endpoint Uri
Data Collection Rule Immutable ID
OneTrust Metadata Stream Name
Related content
Links established from declared identifiers and solution manifests.
Source provenance
GitHubDisplayed values come from files in Azure/Azure-Sentinel. They describe the published template, not your workspace configuration.
- Commit
629d1d3↗- Source identifier
OnetrustPush
GSTEP / CATALOG TRACKING
Added to catalog : 16 Sept 2026 · 05:49 UTC
Last change observed : 16 Sept 2026 · 05:49 UTC