Azure Virtual Machine data source

Data Manager is included in all Service Collection Premium and Enterprise plans.

Azure Virtual Machine (Azure VM) is a Microsoft tool used to manage virtual infrastructure.

The Azure Virtual Machine data source uses an API connection to bring Azure VM data into Data Manager. It requires an application registered in Azure to obtain a Tenant ID, Client ID, and Client secret. Work with your Azure SME for setup.

This task requires Data Manager & Adapters admin permissions to complete. See how permissions and roles work in Data Manager.

How do I connect Azure Virtual Machine to Data Manager?

  1. Gather all of the Data Manager type information, including the data source name, short display name, and the data source type.

  2. Gather the Azure Virtual Machine fields – this may require consultation with the Azure Virtual Machine subject matter expert (SME).

  3. In Data Manager, add a new data source by selecting the tool you which to connect and configure with all the gathered information.

Each time this data source is fetched the data becomes raw data.

Data Manager fields

You need to specify the following information from Data Manager:

  • Data source name – the name of the data source used to run, transform, map, cleanse, and import the data.

  • Short display name – a unique name as a data source label.

  • Data source type – what type of data the tool is providing. For example, Assets, CMDB, user location.

Azure Virtual Machine fields

  • Subscription‑ID – identifies the Azure subscription.

  • Client‑ID – identifies the application in Azure AD.

  • Client secret – secret used by the app to request tokens.

  • Tenant ID – identifies the Azure AD tenant for authentication.

  • API version – version of the Azure VM API.

  • API timeout – time before requests time out.

API timeout

Same pattern as other adapters:

  • Default: 0

  • Recommended: 9000

  • If needed, reduce gradually down to 2000 or follow Azure guidance if timeouts occur.

Authentication and authorization

  1. In Azure Portal, open Subscriptions.

  2. Choose Access control (IAM).

  3. Select + Add > Add custom role.

  4. Provide a role name (for example, Role For AzureVMConnection).

  5. Add these permissions to the role:

    • Microsoft.Compute/virtualMachines/read

    • Microsoft.SqlVirtualMachine/sqlVirtualMachines/read

  6. Create the role.

  7. Back in Access control (IAM), choose Add role assignment.

  8. Select your new role (for example, Role For AzureVMConnection).

  9. Add members (the Azure application created for the connector).

  10. Review and assign the role to the application.

API call

The documented API permission is:

  • Device.Read.All

Fields retrieved

The following fields are retrieved:

Name StorageProfileImageReferenceSku AdminUsername Id StorageProfileImageReferenceVersion ProvisionVMAgent Type StorageProfileImageReferenceExactVersion EnableAutomaticUpdates Location StorageProfileImageReferenceId PatchMode VmId OsDiskType AssessmentMode VmSize OsDiskName AllowExtensionOperations NumberOfCores OsDiskCreateOption RequireGuestProvisionSignal OsDiskSizeInMB OsDiskCaching BootDiagnosticsEnabled ResourceDiskSizeInMB OsDiskStorageAccountTyp BootDiagnosticsStorageUri MemoryInMB OsDiskId ProvisioningState MaxDataDiskCount OsDiskSizeGB StorageProfileImageReferencePublisher DataDiskCountTotalDataDiskSizeGB StorageProfileImageReferenceOffer ComputerName

Still need help?

The Atlassian Community is here for you.
Ask the Community
CommunityQuestions, discussions, and articles