...
| Note |
|---|
|
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:
General Guidance on Limits:
In many cases, users may encounter restrictions around 30 subscriptions per
...
session.
...
However, under certain conditions with smaller datasets per subscription, it is possible to import up to 60 subscriptions in a single
...
session.
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 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 around 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 around 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 developmentWe are actively working on improving the import capacity to accommodate larger numbers of subscriptions per session. A key enhancement to support higher limits is expected to become available through the Forge platform in February (2025). Once this feature is released, we anticipate significantly increasing the number of subscriptions supported in a single import session. We appreciate your patience and will provide updates as soon as they are available.
...