Skip to main content

Azure Resources



Azure Resources provides on-demand cloud computing platforms and APIs. You can use Azure Resources to drive insights into values such as:

  • Catalog
  • Dependencies



If you do not see the Settings page you're looking for, you likely don't have the proper permissions and need to contact your admin.

In order to connect Cortex to your Azure Resources, you’ll need to add your Azure tenant ID, client ID, client secret, and subscription ID in Settings → Azure Resources. The service principal for the subscription ID should have a Reader role.

Multi-account support

The Azure resources integration has multi-account support so you can add a configuration for each additional instance by repeating the above process.

Each configuration requires an alias, which Cortex uses to correlate the designated instance with registrations for various entities. Registrations can also use a default configuration without a listed alias.

You can edit aliases and default configurations from the Azure resources page in Settings. Select the edit icon next to a given configuration and toggle "Set as default" on. If you only have one configuration, it will automatically be set as the default.


Entity descriptor

You can associate a Cortex entity with one or more Azure Resources entities. Cortex will display those Azure Resources entities' metadata on the Cortex entity page. If you want to define a dependency from a Cortex service to an Azure Resources entity, please see Dependencies and the Dependencies section on this page.

- id: /subscriptions/1fbb2da1-2ce7-45e4-b85f-676ab8e685b9/resourceGroups/GROUP1/providers/Microsoft.Compute/disks/vm1_disk1_3d9f85717666435e9e87e4883d31a7e9
alias: my-default-alias # alias is optional and only relevant if you have opted into multi account support
- id: /subscriptions/1fbb2da1-2ce8-45e4-b85f-676ab8e685b0/resourceGroups/GROUP2/providers/Microsoft.Compute/disks/vm1_disk1_3d9f85717666435e9e87e4883d31a7e0
alias: my-other-alias # alias is optional and only relevant if you have opted into multi account support


Cortex automatically discovers dependencies between your services and resources by scanning for resources with specific Azure Resources tags. By default, a service will have dependencies on any Cortex resource that has a corresponding Azure Resources resource with Azure Resources tag key = "service" and tag value = the service's Cortex tag.