Azure Discovery Fails in Azure Service Account Pattern Because of Misconfigured Identification Inclusion RuleIssue 1.Azure Cloud Discovery fails during the Azure Service Account pattern execution due to a payload processing error. The pattern logs shows the following error: CMDB Identification Error: INSERT_FAILED:Insertion failed with error: Error during insert of cmdb_ci_cloud_service_accountSymptoms1.The pattern logs shows the following error: CMDB Identification Error: INSERT_FAILED:Insertion failed with error: Error during insert of cmdb_ci_cloud_service_account 2.System logs during the same time contain SQL exception: FAILED TRYING TO EXECUTE ON CONNECTION glide.25 (connpid=825373): INSERT INTO cmdb java.sql.BatchUpdateException: Duplicate entry '<account_id>' for key 'otjjuziw_u1' 3.Discovery does not proceed past the Azure Service Account pattern.Pattern execution stops at the payload processing stage.ReleaseAny releaseCauseDiscovery failed due to a unique constraint violation on the cmdb_ci_cloud_service_account table. This happened because a custom Identification Inclusion Rule on the cmdb_ci table did not include the Cloud Service Account class. As a result, IRE was bypassed and the system attempted to insert a duplicate CI, violating the table's unique key constraint.ResolutionReview the active Identification Inclusion Rules in your instance: 1.Navigate to Identification Inclusion Rules by going to CI Class Manager 2.Verify that rules do not exclude required CMDB classes (e.g., cmdb_ci_cloud_service_account). 3.Ensure no condition unintentionally bypasses IRE for cloud-related CIs. 4.Modify the rule if needed to include all relevant classes to ensure CIs are processed correctly through IRE. After updating the rule, re-run the Discovery schedule to validate that CI processing completes without errors.