...
After creating an import, it will be in “NOT CONFIGURED” state. You will first need to provide your Azure Connection Details to execute it. Click on the “three dots” and then “Configure app” to open configuration modal.
...
Connection configuration
Fill the necessary fields and click “Save configuration”. Also you should test the connection using the test connection button before proceeding to further tasks. You can also open the schema tree, and see the (empty) structure of Asset Object Types generated under the Root Object Type.
...
Azure Connection parameters:
Root object type name
Specify the name of the object type where the imported data will be stored.
Note : Select the unique name for the root object type. If the object type already exists, it may cause issues due to the Atlassian limitations.
Subscription ID
Note : Only resources registered under the specified subscription will be imported.
Application (Client) ID
Application (Client) Secret Key
Advanced settings
On separate tab you can modify import parameters not critical for import execution.
Scheduler:
Off
Once a day
Using the scheduler, you can automate imports. When enabled, the import will run automatically once a day, starting approximately 24 hours after the configuration is saved. Or you can take control with manual synchronization for precise adjustments on demand.
Import options:
Include hidden tags - hidden tags are special tags that are not displayed in Azure Resource view with “hidden-” prefix in tag name. You can toggle import of these here.
Object Types Update
The Configuration modal includes an "Object Types Update" tab. When you deploy a new version of the app, it may support additional Object Types or Object Type Attributes. These changes are part of the new schema and mapping.
...
| Note |
|---|
|
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.
...