Skip to main content
Logo

Azure addOn

Optimize your Azure experience with our new data scan add-on, simplifying the management and analysis of your critical information, for more informed decisions than ever.


Report Bug · Request Feature

Configuration​

Default.json​

For each of your environments, the following keys are mandatory:

  • rules: This refers to the set of rules files you want to apply to this environment.
  • prefix: the prefix is the particle to be placed in front of the environment variables to be quoted here.

The following keys are recommended to ensure better readability when re-reading the configuration:

  • name: The name refers to the environment concerned by one or more keywords.
  • description: the description helps to clarify the name and avoid any possible confusion about the environment concerned.

Example of configuration for 2 Azure environments.

Environment​

There are several ways to identify yourself in an Azure environment. Obviously, you can only scan the environment for which you are at least a reader role:

AZURETENANTID=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX     # ID of your Azure Tenant
SUBSCRIPTIONID=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX    # ID of your Azure subscription
AZURECLIENTID=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX     # ID of your Azure AD application
AZURECLIENTSECRET=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX # Secret associated to the Client ID
  • If you are runnning your Kexa in an Azure function you can also use this with UAI (User Assigned Identities) and it's recommended if you want use an Azure Keyvault:
USERAZUREIDENTITYID=XXXXXXXX
  • If you are using your Kexa in an Azure CLI environment and are already logged in, you do not need to log in again. Your credentials will be used during the scan.

Additional documentation​

Azure NodeJs SDK