Ready to get started?

Download a free trial of the Azure Active Directory ODBC Driver to get started:

 Download Now

Learn more:

Azure Active Directory Icon Azure Active Directory ODBC Driver

The Azure Active Directory ODBC Driver is a powerful tool that allows you to connect with live data from Azure Active Directory, directly from any applications that support ODBC connectivity.

Access Azure Active Directory data like you would a database - read, write, and update Azure Active Directory 0, etc. through a standard ODBC Driver interface.

Connect to Azure Active Directory as an External Data Source using PolyBase



Use the CData ODBC Driver for Azure Active Directory and PolyBase to create an external data source in SQL Server 2019 with access to live Azure Active Directory data.

PolyBase for SQL Server allows you to query external data by using the same Transact-SQL syntax used to query a database table. When paired with the CData ODBC Driver for Azure Active Directory, you get access to your Azure Active Directory data directly alongside your SQL Server data. This article describes creating an external data source and external tables to grant access to live Azure Active Directory data using T-SQL queries.

NOTE: PolyBase is only available on SQL Server 19 and above, and only for Standard SQL Server.

The CData ODBC drivers offer unmatched performance for interacting with live Azure Active Directory data using PolyBase due to optimized data processing built into the driver. When you issue complex SQL queries from SQL Server to Azure Active Directory, the driver pushes down supported SQL operations, like filters and aggregations, directly to Azure Active Directory and utilizes the embedded SQL engine to process unsupported operations (often SQL functions and JOIN operations) client-side. And with PolyBase, you can also join SQL Server data with Azure Active Directory data, using a single query to pull data from distributed sources.

Connect to Azure Active Directory

If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs. To create an external data source in SQL Server using PolyBase, configure a System DSN (CData Azure Active Directory Sys is created automatically).

Azure Active Directory uses the OAuth authentication standard. To authenticate using OAuth, you will need to create an app to obtain the OAuthClientId, OAuthClientSecret, and CallbackURL connection properties. See the OAuth section in the Help documentation for an authentication guide.

Click "Test Connection" to ensure that the DSN is connected to Azure Active Directory properly. Navigate to the Tables tab to review the table definitions for Azure Active Directory.

Create an External Data Source for Azure Active Directory Data

After configuring the connection, you need to create a master encryption key and a credential database for the external data source.

Creating a Master Encryption Key

Execute the following SQL command to create a new master key, 'ENCRYPTION,' to encrypt the credentials for the external data source.

CREATE MASTER KEY ENCRYPTION BY PASSWORD = 'password';

Creating a Credential Database

Execute the following SQL command to create credentials for the external data source connected to Azure Active Directory data.

NOTE: Since Azure Active Directory does not require a User or Password to authenticate, you may use whatever values you wish for IDENTITY and SECRET.


CREATE DATABASE SCOPED CREDENTIAL azuread_creds
WITH IDENTITY = 'username', SECRET = 'password';

Create an External Data Source for Azure Active Directory

Execute a CREATE EXTERNAL DATA SOURCE SQL command to create an external data source for Azure Active Directory with PolyBase:

  • Set the LOCATION parameter , using the DSN and credentials configured earlier.

For Azure Active Directory, set SERVERNAME to the URL or address for your server (e.g. 'localhost' or '127.0.0.1' for local servers; the remote URL for remote servers). Leave PORT empty. PUSHDOWN is set to ON by default, meaning the ODBC Driver can leverage server-side processing for complex queries.


CREATE EXTERNAL DATA SOURCE cdata_azuread_source
WITH ( 
  LOCATION = 'odbc://SERVER_URL',
  CONNECTION_OPTIONS = 'DSN=CData Azure Active Directory Sys',
  -- PUSHDOWN = ON | OFF,
  CREDENTIAL = azuread_creds
);

Create External Tables for Azure Active Directory

After creating the external data source, use CREATE EXTERNAL TABLE statements to link to Azure Active Directory data from your SQL Server instance. The table column definitions must match those exposed by the CData ODBC Driver for Azure Active Directory. You can refer to the Tables tab of the DSN Configuration Wizard to see the table definition.

Sample CREATE TABLE Statement

The statement to create an external table based on a Azure Active Directory Domains would look similar to the following:

CREATE EXTERNAL TABLE Domains(
  id [nvarchar](255) NULL,
  availabilityStatus [nvarchar](255) NULL,
  ...
) WITH ( 
  LOCATION='Domains',
  DATA_SOURCE=cdata_azuread_source
);

Having created external tables for Azure Active Directory in your SQL Server instance, you are now able to query local and remote data simultaneously. Thanks to built-in query processing in the CData ODBC Driver, you know that as much query processing as possible is being pushed to Azure Active Directory, freeing up local resources and computing power. Download a free, 30-day trial of the ODBC Driver for Azure Active Directory and start working with live Azure Active Directory data alongside your SQL Server data today.