Step 1: Install App

Install the Azure AD Insight Importer App from the Atlassian Marketplace to your Jira Cloud environment.

Step 2: Setup Asset External Import

In order to import data you need to have an existing object schema and an Assets Token.

2.1 Generate a token for importing

To import data from an external app, you must generate a key that allows the external app to securely transfer the data into Assets. This is called a Single Sign-On (SSO) token, or just token.

You must also generate a token to import data from Asset Discovery.

To generate a token:

1. From your service project, go to Assets > Object schemas.

2. Select an Object schema.

3. Select Configure, then choose the Import tab.

4. Click on the cogwheel under either Assets Discovery (DSC) or External app (EXT) import connections and select Generate token.

5. Click Generate to create or refresh a token.

6. Store the token in a secure location, as it will not be visible once the page is closed. Then, click Close.

2.2 Apply the Token to the App

1. Open the App by navigating to App > Manage your Apps > Assets Azure AD Importer.

2. Enter the API Key in the first step. The key is validated immediately, and you will be directed to the second step.

Step 3: Enter Azure AD Credentials

After entering the API Key in the first step, input the Client ID, Client Secret, and Tenant ID.

3.1 Obtain your Tenant ID:

1. On the dashboard, select All services > Azure Active Directory in the left navigation menu.

2. Scroll down to Manage and open Properties.

3. Note the Tenant ID for use in the import configuration.

3.2 Create an Enterprise Application:

1. Select All services > Azure Active Directory from the dashboard's left navigation menu.

2. Go to App registrations and select New registration.

3. Enter an application name of your choice, such as "asset-azure-integration".

4. Create the App registration.

3.2 Create an Application Secret Key:

1. Access the settings of the previously created application.

2. Select Certificates & secrets.

3. Click New client secret.

4. Enter a description for the key (e.g., AppKey), choose a duration, and click Save.

5. Note the generated Key-Value for use in the import configuration.

3.3 Verify Required Permissions:

1. Access the settings of the previously created application.

2. Select API permissions.

3. Ensure the delegated permission User.Read.All, Group.Read.All, Device.ReadWrite.All and DeviceManagementManagedDevices.Read.All exists.

Step 4: Select Objects to Import and Structure creation

Within the app's Step 3, you can choose which objects to import. You have three options:

1. Do not sync

2. Create Structure

3. Use existing Structure

Step 3 within the App allows you to select the Objects you want to import. You have two three options:

• Do not sync

• Create Structure

• Use existing Structure

Do not sync simply omits the data import.

If you have an empty Object Schema, you can select Create Structure, which will generate all necessary Object Types with all available attributes.

If you have an existing structure, you can select Use existing structure. You will need to match the Object Name. Unfortunately, Atlassian does not allow reading and using the existing structure without adjustments. Therefore, you need to update the mapping of the object type afterwards. Every possible parameter is linked to an attribute called ADImport. You must select the correct attribute. Afterwards, you can remove the identifier flag. If you don't need the attribute, leave it in ADImport or delete the row.

Step 4: Missing Mapping

After the initial setup, the import status should be MISSING_MAPPING. Click on Create Structure, then click on Reload or refresh the page. You should now see IDLE. If you encounter an error message, contact support with a timestamp.

Now you are ready. The import is performed every hour, or you can manually start the import.

Check for Object references and set the Cardinality to Unlimited

This needs to be done for the following attributes