Connect Azure Data Explorer (Kusto) to Alation's data catalog with automated metadata extraction. Extract Clusters, Databases, Tables, and Columns using Azure trusted authentication. Supports SSL and HTTPS, selective extraction by Cluster or Database, and full extraction for enterprise-scale ADX deployments.
The Azure Data Explorer RDBMS OCF Connector, developed by Logan Data, enables Alation users to automatically extract and catalog metadata from Azure Data Explorer (ADX) clusters, bringing Databases, Tables, and Columns into Alation's unified data intelligence platform as fully searchable, trusted data assets.
Azure Data Explorer is Microsoft Azure's fully managed, high-performance analytics service built for real-time analysis of large volumes of streaming and batch data. It uses the Kusto Query Language (KQL) and is widely used for log analytics, IoT telemetry, application monitoring, and business intelligence. By connecting ADX to Alation through this OCF connector, data analysts, business analysts, and data stewards gain the ability to find, understand, and trust ADX data assets from within Alation's catalog, without needing direct access to the ADX Web UI or writing KQL.
Built on Alation's Open Connector Framework (OCF) with a containerized SDK, this connector uses two distinct Azure REST API tiers to extract metadata accurately and completely:
Azure Resource Manager APIs (management.azure.com) for Cluster and Database-level metadata including connection URIs and storage configuration
Kusto REST APIs (api.kusto.windows.net) for Table and Column metadata via KQL management queries (.show tables, .show table schema)
Object mapping - what gets extracted and how it appears in Alation:
Cluster.Database mapped to Alation Schema: with database name, PersistentStorage value (mapped to Alation Description), and Connection URI (e.g. https://.eastus.kusto.windows.net)
Table mapped to Alation Table: with table name
Column mapped to Alation Column: with column name and data type
Authentication and security:
Azure Trusted Authentication (recommended): Azure Entra ID OAuth 2.0 client credentials flow using client_id and client_secret, the Microsoft-recommended approach for service-to-service connectivity to ADX
SSL/TLS enforced: ADX accepts HTTPS connections exclusively, ensuring all metadata extraction traffic is encrypted in transit
Extraction capabilities:
Selective extraction: apply filters at the Cluster or Database level to scope catalog updates to specific ADX resources, configured via the toggle in Alation's connector settings page
Full extraction: catalog all Databases and their Tables and Columns across all accessible ADX clusters in a single run
Known limitation: the Azure Clusters List API returns all clusters within one Azure subscription per tenant, clusters from different Azure organizations require separate connector configurations. Use selective extraction to filter to the clusters in use.
Near real-time synchronisation between Azure Data Explorer and Alation ensures analysts are always working with current schema information. A log view of extraction status is visible directly on the connector settings page in Alation.
Compatibility: Alation On-Premise and Alation Cloud Service. Azure subscription with Kusto cluster access and Azure Entra ID service principal required.
Highlights
Complete Azure Data Explorer metadata in Alation, including Clusters, Databases, Tables, and Columns. Full schema catalog with connection URIs, storage properties, and column types mapped to Alation for unified search, curation, and governance across ADX data assets.
Azure Entra ID trusted authentication with SSL and HTTPS security. Uses OAuth 2.0 client credentials flow, Microsoft's recommended approach for ADX service connectivity, with HTTPS enforced. No plaintext credentials. Fully compatible with enterprise Azure AD policies.
Selective and full extraction with Cluster and Database-level filters. Scope catalog updates to specific ADX clusters or databases, or run a full extraction across all resources, configurable directly from Alation's connector settings page.
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
Pricing is based on the duration and terms of your contract with the vendor. This entitles you to a specified quantity of use for the contract duration. If you choose not to renew or replace your contract before it ends, access to these entitlements will expire.
Additional AWS infrastructure costs may apply. Use the AWS Pricing Calculator to estimate your infrastructure costs.
This listing has one pricing dimension: the Azure Data Explorer RDBMS OCF Connector, sold as a contract. You buy the connector as a single unit rather than choosing among tiers or instance sizes. Pricing does not scale by usage or data volume. The connector extracts database metadata (clusters, databases, tables, and columns) from the source system into the data catalog platform. It runs one direction only, moving artifacts into the catalog. Because there is a single unit, your cost is set by the contract term rather than by consumption.
Top-of-mind questions for buyers
What counts as one connector unit for billing on this listing?
One unit is a single license for the Azure Data Explorer RDBMS OCF Connector. It covers the connector that extracts source metadata into the data catalog. You are not billed per cluster, database, table, or column moved. The unit is the connector itself, not the volume of artifacts synchronized.
Does my cost change as I catalog more databases, tables, or columns?
No. Pricing is set by the contract for the single connector unit. It does not scale with the number of clusters, databases, tables, or columns you extract. Whether you sync a small source or a large one, the connector cost stays tied to the contract term, not the data volume moved.
Is this connector one-directional, and does that affect what I pay for?
The connector moves data in one direction only, pulling source metadata into the data catalog. It does not write back to the source. You pay for this single one-way connector as one contracted unit. There is no separate charge for a reverse or bidirectional flow, since none is offered.
Tell us how we can improve this page, or report an issue with this product.
Give us feedbackReport a problem with this product or seller
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA).
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
SaaS delivers cloud-based software applications directly to customers over the internet. You can access these applications through a subscription model. You will pay recurring monthly usage fees through your AWS bill, while AWS handles deployment and infrastructure management, ensuring scalability, reliability, and seamless integration with other AWS services.
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Connect Microsoft Purview File System to Alation's data catalog with automated metadata extraction. Extract Collections, Folders, Files, and Schemas from Purview into Alation. Supports Azure AD authentication, SSL/TLS, and selective extraction by Collection for enterprise-scale data governance.
Eliminate manual metadata reconciliation between Microsoft Purview and Alation. Automatically sync accounts, collections, assets, and schemas with permission mirroring and cross-system lineage.
Data Intelligence Platform for data search & discovery, data & AI governance, data products, data stewardship, analytics, cloud migrations, and modernization.
Connect ThoughtSpot to Alation's data catalog with automated metadata extraction and end-to-end lineage. Extract Organisations, Worksheets, Liveboards, Answers, Datasources, Measures, Dimensions, and Formulas. Supports Basic and Trusted authentication, permission mirroring, cross-system lineage, and selective extraction by Organisation.
Be the first to review this product. We've partnered with PeerSpot to gather customer feedback. You can share your experience by writing or recording a review, or scheduling a call with a PeerSpot analyst.