Prerequisites¶
Alation Cloud Service Applies to Alation Cloud Service instances of Alation
Customer Managed Applies to customer-managed instances of Alation
Enhanced Connector Enhanced connectors add extended capabilities and require a separate entitlement in addition to your Alation platform license.
Before installing and configuring the Azure Data Explorer OCF connector, ensure that network connectivity is in place and that you have a Microsoft Entra ID (Azure AD) service account (service principal).
Configure Network Connectivity¶
Ensure that the Alation host (for customer-managed deployments) or the Alation Agent/Connector Manager host (for Agent-based connections) can reach the Azure Data Explorer cluster endpoint.
Allow outbound connectivity from Alation to the Azure Data Explorer cluster endpoint on the required port (typically TCP 443 for HTTPS-based connectivity).
If your environment uses a firewall or proxy, ensure that the required hostnames are allowed and that SSL/TLS inspection (if used) is compatible with your connectivity requirements.
Create a Microsoft Entra ID Application¶
Microsoft Entra ID token authentication requires a Microsoft Entra ID application registration (service principal) that Alation can use to request access tokens. See Create a Microsoft Entra ID application registration for instructions on how to create an app registration in Azure Data Explorer.
Collect the following values for configuration in Alation:
Tenant ID — Microsoft Entra ID directory identifier.
Client ID — application (client) ID of the app registration.
Client secret — secret value generated during the app registration.