...
If you need specific subscriptions to be imported
In your Azure portal, search for Subscriptions
Select the Subscription(s) you would like to synchronize the Azure (Assets) data from
Save the Subscription ID(s) for future reference for usage in the import configuration
...
You need to register an Application that will be used for the API-Gateway(the Azure Registration Application) that works as a gateway that enables the Azure Sync app to access data within your Azure environment. This registration app acts as an intermediary; it has permissions to view or manage certain parts of your Azure setup, but Azure Sync for Jira Assets does not directly access or modify Azure data. The registration app specifies which data the Azure Sync app can import.
In your Azure portal, select All services > Microsoft Entra ID
Under the âAddâ tab, click on App registration (or in the left bar open App registrations and Select New registration)
Pick a name for your application. You can use something like "asset-azure-sync" as inspiration
Leave other settings at default values
Create the App registration
Save the Application (client) ID for future reference for usage in the import configuration
...
Assign Application Role assignment
Granting permissions to the registration app is essential as it defines the scope of data access: what the Azure Sync app can view and manage in Azure.
In your Azure portal, search for Subscriptions
Select your subscription (or more if you want to be able to import data from multiple subscriptions)
Select Access control (IAM) and click on the Role assignments tab
Click Add (you need to have proper permission)
Choose Role = Reader and search at the select for the Application name that you have created in steps above (saying this registered application now can read this subscription data)
...
Check Required Permissions
...
See which Object Types or Object Type Attributes have been added, removed, or updated.
Run the schema and mapping update to apply these changes.
Structuring Your Imports in Jira:
Depending on your organizationâs needs, you may want to import data from different subscriptions into one shared âroot objectâ within Jira Assets or keep them separated by creating distinct root objects.
Single Root Object: All resources, regardless of the subscription, are imported into a single location within Jira Assets. This works well if itâs not necessary to distinguish resources by environment (e.g., production vs. testing).
Separate Root Objects: If itâs essential to differentiate resources for example by environment, you can set up separate root objects within Jira for each subscription (multiple import instances). This setup reduces the risk of data confusion, as each environment is clearly separated in Jira Assets.
Performing the Import
Once you have configured your settings correctly, you should be ready to perform the import process effortlessly. Before the first execution, configured import will be in state âREADY TO RUNâ and âImport dataâ button will appear. To start the import manually, simply click on the button.
...