Microsoft Azure Batch¶
The Microsoft Azure Batch connection type enables the Azure Batch integrations.
Authenticating to Azure Batch¶
There is one way to connect to Azure Batch using Airflow.
Use Azure Shared Key Credential i.e. add shared key credentials to the Airflow connection.
Use managed identity by setting
managed_identity_client_id
,workload_identity_tenant_id
(under the hook, it uses DefaultAzureCredential with these arguments)Fallback on DefaultAzureCredential. This includes a mechanism to try different options to authenticate: Managed System Identity, environment variables, authentication through Azure CLI and etc.
Default Connection IDs¶
All hooks and operators related to Microsoft Azure Batch use azure_batch_default
by default.
Configuring the Connection¶
- Batch Account Name (optional)
Specify the Azure Batch Account Name used for the initial connection. It can be left out to fall back on DefaultAzureCredential.
- Batch Account Access Key (optional)
Specify the access key used for the initial connection. It can be left out to fall back on DefaultAzureCredential.
- Batch Account URL
Specify the batch account URL you would like to use.
- Managed Identity Client ID (optional)
The client ID of a user-assigned managed identity. If provided with
workload_identity_tenant_id
, they’ll pass to DefaultAzureCredential.- Workload Identity Tenant ID (optional)
ID of the application’s Microsoft Entra tenant. Also called its “directory” ID. If provided with
managed_identity_client_id
, they’ll pass to DefaultAzureCredential.
When specifying the connection in environment variable you should specify it using URI syntax.
Note that all components of the URI should be URL-encoded.
For example:
export AIRFLOW_CONN_AZURE_BATCH_DEFAULT='azure-batch://batch%20acount:batch%20key@?account_url=mybatchaccount.com'