Configure the Azure Discovery connector

The Snow Integration Connector for Azure Discovery is configured in Snow Integration Manager. For more information, refer to Snow Integration Manager.

The Azure Discovery connector uses an HTTPS connection.

  1. In the Directory id box, paste the Directory (tenant) ID copied from the Microsoft Azure portal.

    For details, see Create Azure Active Directory application.

    azure.png
  2. In the Application id box, paste the Application (client) ID of the Azure SIM Gateway application, copied from the Microsoft Azure portal.

    For details, see Create Azure Active Directory application.

  3. In the Application secret box, paste the value of the sim_secret_key of the Azure SIM Gateway application, copied from the Microsoft Azure portal.

    For details, see Create client secret.

  4. To configure import filters for subscriptions and resource groups, select Advanced options and follow the instructions in Advanced options.

  5. To verify the connection, select Test connection.

Advanced options

Under Advanced Options you can set up filtering of subscriptions and resource groups, and choose options for site name. Select Confirm to save the changes, or Cancel to close the view.

azure_advanced.png

Use the options under Filter settings to set filters for which subscriptions and resource groups you want to import:

  • Select Don't import selected subscriptions and resource groups to exclude the selected subscriptions and resource groups from the import.

  • Select Only import selected subscriptions and resource groups to include the selected subscriptions and resource groups in the import.

Use the options under Naming to make changes to Site Name and appending of Resource Group name:

  • Enter your own site name in Override Site Name. This will override any automatically detected site name, for example the site name set in SIM.

  • Select the Append Resource Group name to Site name checkbox to add the resource group name to the site name for every resource group. The site name will then be different for servers in different resource groups.

    Note

    Option Append Resource Group name to Site name will most likely have unintended consequences and should not be used unless you understand exactly what it does and you are certain that it is supposed to be used in your environment.

    Selecting this option will require you to reconfigure your agent deployment to allow discovered hosts to be matched to their agents.