Duplicate MSFT SQL instances are creating via SG - AWS which lead duplicate application CI relationships creation.Issue Duplicate MSFT SQL instances are creating via SG - AWS which lead duplicate application CI relationships creation.Release SG - AWS 2.9.1 Version CauseIdentifier entry in cmdb_ci_db_mssql_instance table is Instance name and class name with allow null attribute checked. In SG - AWS we observed the script include "sendcommandtranfromutil " there is no no mapping for "Instance name field" As there is no mapping for "Instance name field" it will always inserting the records in cmdb_ci_db_mssql_instance table, which eventually creating duplicate application CI relationships .Resolution➤ This was identified as a product defect. A Problem Record (PRB1891654) has been created to track it. ➤ Please follow the workaround below to temporarily resolve the issue by adding an additional identifier for the MSFT SQL Instance: Workaround Steps: Navigate to CI Class Model.Search for MSFT SQL Instance.Go to Identification Rule > Add.Select Use Attributes from MS SQL Instance Table.Set Priority to 900.Choose the Class and Name fields.Click Save. Note: Make sure to check the 2 boxes for 'Allow Null Attributes' and 'Allow fallback to Parent's Rule'. Other wise it will create de-duplication tasks (Please refer to the attached screenshot for guidance.) ➤ This issue will be addressed in a future AWS release. Once the fix is available, you'll be able to upgrade to that version. You can track the status of PRB1891654 directly on the Now Support Portal by searching for the PRB number.