Microsoft Azure Service Bus¶

The Microsoft Azure Service Bus connection type enables the Azure Service Bus Integration.

Authenticating to Azure Service Bus¶

There are three ways to authenticate and authorize access to Azure Service Bus resources:

Use a Connection String i.e. Use connection string Field to add Connection String in 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. fully_qualified_namespace is required in this authentication mechanism.

All hooks and operators related to Microsoft Azure Service Bus use azure_service_bus_default by default.

Connection String (optional): Specify the Azure Service bus connection string ID used for the initial connection. Please find the documentation on how to generate connection string in azure service bus Get connection string Use the key connection_string to pass in the Connection ID . It can be left out to fall back on DefaultAzureCredential.
Fully Qualified Namespace (optional): Specify the fully qualified Service Bus namespace that the connection is associated with. This is likely to be similar to {yournamespace}.servicebus.windows.net. Use the key fully_qualified_namespace to pass in the Connection ID . This is required when falling back to DefaultAzureCredential.
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.