vCommander ® 6.0.2 introduces support for Azure Resource Manager (ARM) as a managed system. Beyond the name you provide to label the managed system in vCommander, you also need to provide some additional information, some of which only becomes available after substantial configuration has been performed in the Azure Management Portal. This includes creating an application identity and retrieving an API key. To reduce the amount of configuration effort required, follow the procedures covered in this article, which scripts much of what is required.




Requirements



Running the Script


  1. Unzip the attached file to your vCommander application server. Embotics recommends keeping all scripts used by or for vCommander in a single directory, with sub-directories indicating the purpose of scripts. Your filesystem should look like this:
    • C:\scripts\arm\setupArmSpn.ps1
  2. Execute the script in PowerShell. Note that it takes some time before the script responds.
  3. A Microsoft Azure logon window appears. Enter your Azure management credentials and click Sign in. Sign in with credentials able to be assigned the Owner role.

  4. If you have multiple subscriptions, you will be prompted to select the one you wish to add. Otherwise, the script will work with your subscription automatically.
  5. Enter the name of the application and service principal to register in Azure, for example vCommander.
  6. Enter the URL of the application's homepage. This field is used when Azure needs to callback an application which is not relevant for vCommander, but is a required field in Azure. Embotics recommends using your corporate web site.
  7. The script will continue to set everything up for you, and provides the information to enter into vCommander.
  8. Use the information provided in the Add Managed System dialog in vCommander.

Repeat this process for each subscription you want to add to vCommander.