...
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), or to track resources across your organization and have everything in one place.
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.
...
Note: If you had any IpConfigurations imported from a version prior to 3.15.0 and import them again, they will be treated as "duplicates" (since the Id attribute is being modified, the system sees it as a new object). To resolve this, we recommend bulk-removing all the existing IpConfigurations and then running the import again.
| Note |
|---|
|
If your organization has more than 30 Azure subscriptions, you may encounter restrictions in importing all subscriptions in a single process. While we are actively working on a permanent solution, here are some recommended approaches for managing larger imports.
Workarounds
Use Multiple Import Instances
Specify Individual Subscriptions
Consider running separate import sessions. This can be done by listing up to 30 subscriptions per session in the Subscription IDs configurationinput field.Import “All Available” Subscriptions: Create Additional Azure Registration Apps
Alternatively, you can create multiple Azure registration applications to divide and manage the subscription import process more effectively. Each app can be configured to import a different set of up to 30 subscriptions, reducing manual input and simplifying the import setup (utilizing the "All Available" configuration option)
Resolution Timeline
Our team is aware of this limitation, and a fix to enable larger bulk imports is currently under development. We appreciate your patience and will provide updates as soon as they are available.
Troubleshooting
Assets - Azure Integration requires both Jira and Assets to function. Also make sure all the specific permission in your Azure environment was set right.
...