Content Comparison

...

As of February 4, 2025, the improved import capacity is now available on the Forge platform. This enhancement allows for significantly higher subscription limits per session, making the import process more efficient. In most cases, this increased limit should be sufficient to meet all user needs.
While the exact limit may vary based on factors like the amount of data associated with each subscription, here’s what you need to know:

1. General Guidance on Limits:

   • In many cases, users may encounter restrictions around 30 350 subscriptions per session.

   • However, under certain conditions with smaller datasets per subscription, it is possible to import up to 60 nearly 1000 subscriptions in a single session.

2. Real-World Variations:

   • Due to differences in data volume, some users may encounter import limitations at lower subscription counts. This variability makes it important to plan import sessions accordingly.

...

If your organization has a high number of large subscriptions or encounters import limitations, consider these approaches:

...

• Specify Individual Subscriptions
  Consider running separate import sessions. This can be done by listing up to around 30 350 subscriptions per session in the Subscription IDs configurationinput field.

• Import “All Available” Subscriptions
  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 around 30 350 subscriptions, reducing manual input and simplifying the import setup (utilizing the "All Available" configuration option)

...

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.

...