OnLink · Cloud resources
OnLink imports Azure virtual machines into Jira Service Management Assets through the Azure Compute REST API, using the same Entra ID app registration you may already have for users and Intune: Reader on the subscription, a mapping keyed on the VM resource ID, and a schedule.
This guide covers why Azure VMs belong in Assets, the four-step Entra ID setup and permissions, the OnLink import, and the field mapping.
Having your Azure virtual machines represented as assets in JSM unlocks practical benefits for IT operations and service management.
When your VMs are tracked in Assets, you can tie them into JSM workflows that alert your team to vulnerability issues. If a security advisory affects a specific OS version or VM configuration, you can quickly identify which machines are impacted and trigger incident or change management workflows.
Mapping VMs to the people who use them gives your IT team visibility into which cloud resources are assigned to which employees. This is especially valuable during onboarding (ensuring new hires have the infrastructure they need from day one) and offboarding (making sure departing employees' cloud resources are properly decommissioned or reassigned).
The Azure Cloud import in OnLink leverages the Microsoft Graph API through an Entra ID (formerly Azure AD) app registration. If you’ve already set up an Entra ID connection for other OnLink integrations, you can reuse that same connection.
Go to the Azure Portal, navigate to Azure Active Directory, then App registrations, and create a new registration (e.g., "OnLink Connection").
Under your app registration, go to API permissions and add the Microsoft Graph permissions your integration needs. For the Azure Cloud VM import specifically, you must also grant the following permission:
Under Certificates & secrets, generate a new client secret. Copy the value immediately — you won't be able to view it again later.
You'll need three values to configure the OnLink connection:
Grant the app read access to compute resources:
Microsoft.Compute/virtualMachines/read (read/list)
For detailed step-by-step instructions with screenshots, refer to the Entra ID connection guide in the OnLink documentation.
OnLink handles the entire import pipeline for you. There’s no need to write scripts, build middleware, or manage API pagination logic. You simply:
Select "Azure Cloud" as the source system when creating a new import configuration in OnLink.
Establish the connection using the Entra ID credentials from the previous step.
Configure field-level mapping through the OnLink UI, accessible from the "Manage your apps" menu.
Schedule automated runs so your asset data stays in sync with Azure on an ongoing basis.
OnLink maps fields from the Azure Compute REST API response directly to attributes in your JSM Assets object schema. The API used is the Virtual Machines – List All endpoint, which returns detailed information about every VM in your subscription.
The Azure Virtual Machines API returns a rich set of fields. Here are the most commonly mapped ones:
|
API Field
|
Description
|
|---|---|
id |
Unique Azure resource identifier for the VM
|
name |
The name of the virtual machine
|
type |
The resource type (e.g., Microsoft.Compute/virtualMachines)
|
location |
The Azure region where the VM is deployed
|
properties.hardwareProfile.vmSize |
The VM size/SKU (e.g., Standard_D2s_v3)
|
properties.osProfile.computerName |
The computer name set in the OS profile
|
properties.storageProfile.osDisk |
OS disk configuration details
|
properties.networkProfile |
Network interface references
|
key:id=id
map:name=Name
map:type=Type Name
map:location=Location
map:properties.hardwareProfile.vmSize=VMSize
map:properties.osProfile.computerName=Computer Name
config:subscription_id=
A few things to note about the syntax:
OnLink is on the Atlassian Marketplace with a free trial. Reuse your Entra ID connection and have Azure VMs in Assets today.
No. OnLink handles the entire integration — API connectivity, data retrieval, pagination, and import into JSM Assets — through its configuration UI. No scripting or middleware is required.
Yes. If you already have an Entra ID (Azure AD) app registration configured for OnLink, you can use the same connection. Just make sure the additional permission (Microsoft.Compute/virtualMachines/read) is granted and the app has Reader role access to the target subscription.
You’ll need to configure a separate import for each subscription, each with its own config:subscription_id value.
OnLink supports automated scheduling, so you can set imports to run at whatever interval makes sense for your organization — hourly, daily, weekly, or custom.
OnLink uses the key:id mapping to match records. If a VM no longer appears in the API response, the corresponding asset in JSM won’t be automatically deleted — but it also won’t be updated. You can manage lifecycle status through separate JSM automation rules if needed.
Yes. Google Cloud VMs, projects and service accounts import the same way, and the Entra ID connection used here also brings in users, groups and licenses and Intune devices. All sources.
Azure VMs in Assets
Start a free trial of OnLink on the Atlassian Marketplace. Azure, Google Cloud, Entra ID and Intune all run through the same app.
Install OnLink from the Atlassian Marketplace and reuse your Entra ID connection to import Azure VMs. Every other source the same app connects is listed in One App, Every Source.
With Azure VMs in Assets, your team can:
RELATED