Create the User-Assigned Managed Identity for Azure Event Hub
Step-by-step instructions and Azure CLI examples for creating the User-Assigned Managed Identity for Azure Event Hub.
Configure a User-Assigned Managed Identity (UAMI) to enable secure, secret-less authentication between Cortex XDR and your Azure Event Hub. This process uses workload identity federation to allow the Cortex Collector to assume the identity of the UAMI.
Configure the Managed Identity
These instructions only an example using the Azure CLI; you can create and configure this UAMI using whichever method you prefer (Azure Portal UI, Infrastructure as Code, or any other preferred option).
Set these values once in your shell. After you fill them in, every command in this guide is copy-paste-and-run.
Set environment variables. The following values are examples; replace the placeholder strings with your specific resource values.
The
clientIdis the application ID used by Cortex to authenticate via workload identity federation.The
principalIdis the unique object ID used to bind Azure RBAC role assignments.
Create the UAMI. The UAMI is the workload identity assumed by the Cortex Collector.
3. Configure workload identity federation for the UAMI. Configure workload identity federation to allow the Cortex Collector's Google service account to authenticate as the UAMI.
4. Grant the UAMI Storage Blob Data Contributor on the Storage Account. Grant the UAMI access to the Storage Account you provided, using its resource ID.
Grant the UAMI Azure Event Hubs Data Receiver on the Event Hub. Grant the UAMI access to the specific Event Hub entity (not the whole namespace) by scoping the role assignment to the Event Hub's resource ID.
6. Verify the role assignments (optional). Confirm that both roles were assigned to the UAMI:
Last updated
Was this helpful?
