Azure Sync for Jira Assets : FAQ
Q: Why does the import appear to be stuck at the beginning?
A: The import can take some time depending on the amount of Azure data being processed. During this phase, the progress bar may appear unchanged while the synchronization continues running in the background. This is expected behavior.
Q: How are Tags imported?
A: Only the Tags associated with the resources being imported are included. If a resource has a tag attribute, it will be imported.
Additionally, hidden tags (those with the prefix "hidden-") that are not displayed in Azure's Resource view - can also be imported. You can toggle the import of these hidden tags under the "Import options" section in the configuration dialog.
When importing Azure resources into Jira Assets, duplicate tags can appear if the same tag exists with different capitalization (e.g., Application:Backend-v2 vs. application:Backend-v2). For more info see Azure Sync for Jira Assets: User Documentation 📝.
Q: How can I import from multiple Azure subscriptions at once?
A: In the latest version of Azure Sync for Jira Assets, you have two options (in the import configuration dialog) for importing resources from multiple subscriptions:
Use All Available Subscriptions:
You can enable the option to import resources from all subscriptions that your Azure App has permission to access. This simplifies the process by pulling data from every subscription the app has access to without needing to specify them individually.Specify Subscriptions:
If you want more control and prefer to import from specific subscriptions, you can toggle off the "Use all available subscriptions" option. Then, manually enter the Subscription IDs you want to import from, separating multiple IDs with commas. This is useful for handling a large number of subscriptions efficiently within a single import instance.
Important: Please be aware of the current import limitation regarding the number of subscriptions per session. The exact limit may vary based on the data volume, but users should plan their imports accordingly. See the full documentation for details and recommended workarounds.
Q: Should I use Jira Automation or the built-in scheduler?
A: Both are supported. Choose based on what you need.
Use Jira Automation when you want:
a specific time or day (for example every weekday at 06:00),
Slack / Teams / email notifications after the import is started,
conditions or a manual “Run now” trigger,
one place to manage schedules together with other Jira rules.
Use the built-in scheduler when a simple every-12-hours or every-24-hours sync is enough and you prefer configuring it directly in the app.
Setup guide: see Scheduling imports in the User Documentation.
Important: use one scheduling mechanism per import (not both).
Q: What happens if the import is already running (when running from automation)?
A: If the selected import is already running, Azure Sync will not start a duplicate execution.
The Automation action still completes successfully and returns values you can use in later rule steps (started, status, message) - for example to notify that a sync was skipped because one was already in progress. The action only starts the import; the final import result is not available inside the same Automation action.
Q: When should I use Microsoft Entra ID only?
A: When you want a focused identity sync in Assets (and optional user–group membership), without Azure subscription resources.
Q: Can I sync membership and still import Azure resources later?
A: Yes - create the import with Azure resources and Microsoft Entra ID, switch to Microsoft Entra ID only for membership runs, then switch back for resource syncs.
Q: Can an Entra ID only import be upgraded to the full schema later?
A: No. Imports created as Microsoft Entra ID only keep their dedicated identity schema. Start with the full option if you may need Azure resources in the same import later.