Content Comparison

...

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

As of February 4, 2025, imports in our app now have improved capacity. 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 350 subscriptions per session.

   • However, under certain conditions with smaller datasets per subscription, it is possible to import up to 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.

Workarounds for Larger Imports

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

Use Multiple Import Instances

• Specify Individual Subscriptions
  Consider running separate import sessions. This can be done by listing up to 30 around 350 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 around 350 subscriptions, reducing manual input and simplifying the import setup (utilizing the "All Available" configuration option)

...

• " 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.

...

You might notice your import process appears to run endlessly without completing. This is due to an issue in the Forge platform, where the error occurs internally during calls to Atlassian’s API
Currently, the only plausible solution is to manually stop the import and start it again. Unfortunately, this error cannot be programmatically detected, as it happens within Atlassian’s systems.
The issue is .

We have implemented a workaround that we believe resolves the issue; however, it may still occur as it is being tracked under ECO-516, and Atlassian is actively working on a permanent fix. Until then, please use the restart workaround as neededIf the issue does arise, the current solution is to manually stop the import and restart it. Please note that this issue can also occur during scheduled imports. As a result, we recommend monitoring scheduled imports and restarting them if necessary.

Feedback and Support

Your invaluable feedback fuels the evolution of Azure Sync for Jira Assets. Share your insights, and together, we'll cultivate a more refined and impactful user experience! 📊🌱

...