Assets Azure Integration Import Fails to Import Objects
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
After completing the Azure import process, none of the Azure objects are being imported into Asset schemas. Additionally, the logs do not show any specific errors that could help identify the root cause of this problem.
Diagnosis
The import log confirms the successful completion of the import process. Despite this, no objects have been imported. The log reports an infoMessage stating "No data to import," along with the notification that there are zero objects to import. Additionally, the entriesInSource is shown as 0.
024-05-17 10:49:01,928 [insight-InsightThreadGroup-worker-thread-189] | com.riadalabs.jira.plugins.insight.services.imports.common.ImportResult[
executedType=MANUAL
objectSchemaId=38
result=OK
infoMessage=No data to import
errorMessages=<null>
ObjectTypes : objectTypeResultMap={141=com.riadalabs.jira.plugins.insight.services.imports.common.ImportResult$ObjectTypeResult@237fc91c[
objectTypeName=Employee
objectTypeId=141
objectsUpdated=0
objectsCreated=0
objectsIdentical=0
entriesInSource=0
objectsFilteredWithIQL=0
Cause
The issue stems from the fact that the Assets - Azure import configuration lacks an updated Subscription ID. This ID, a distinctive alphanumeric string, is crucial for identifying your Azure subscription. The screenshot illustrates that the Subscription ID field is mandatory. Unfortunately, the field contains only a comma instead of a valid ID, leading to the problem.
Solution
A valid Azure subscription ID is required. To set up the import configuration, carefully follow all the steps outlined in the Assets Azure integration documentation. Make sure to input the values accurately in each field, which includes Application Id, Secret Key, Directory Id, and Subscription Id.