...
Handling Deleted Objects Across Multiple Subscriptions in the same Root Object
If you are 're importing from multiple Azure subscriptions and using into a shared root object in Jira Assets, you may encounter issues with the status approach. The can now use a single import instance to aggregate data across subscriptions. This reduces the need to configure multiple imports and prevents issues related to the "missing object" check, which previously applied only applies to individual imports , which (could lead to the inactivation or removal of asset objects that still exist in other subscriptions).
Solution:
To avoid this issue, consider one of the following options:
...
Use Separate Root Objects: Create distinct root objects for each subscription to keep them separate in Jira Assets.
With the latest multi-subscription feature, this streamlined approach avoids the potential problems mentioned above. You have two options when configuring imports:
Import All Available Subscriptions: Automatically imports asset data from all subscriptions the app has permissions for.
Specify Individual Subscriptions: You can selectively import one or more subscriptions by listing their IDs, separated by commas, in the import settings.
For detailed setup instructions, see Import Configuration section in our documentation.
Solutions:
Single Import for Multiple Subscriptions:
...
Use a single import instance to bring in data from multiple subscriptions under one root object,
...
utilizing either of the options mentioned above.
Separate Root Objects (Optional): If you still prefer to keep subscription data isolated, you can create distinct root objects for each subscription to maintain separation in Jira Assets.
Billing Data
TBD