Your Instance was not Created Because a Security Group with Same Name Already Exists in Azure Active Directory

Table of Contents

Your Instance Was not Created – Defender for Identity

In some cases, when creating a Defender for Identity instance, you got the below message: Your instance was not created because there is already a security group with the same name as the Azure Active Directory.

Your Instance was not Created Because a Security Group with Same Name Already Exists in Azure Active Directory

To fix it, let’s delete or rename the existing three security groups from either Microsoft 365 admin center or Microsoft Entra admin center and try again.

Below is the list of security groups that need to be deleted or renamed from your tenant:

  • Azure ATP {instance name} Administrator
  • Azure ATP {instance name} Users
  • Azure ATP {instance name} Viewers
Your Instance was not Created Because a Security Group with Same Name Already Exists in Azure Active Directory

Once the security groups are deleted, go to the Microsoft Defender portal and then try to create the Defender for Identity instance again.

If you get the following error, let’s wait a few minutes and try again.

Your Instance was not Created Because a Security Group with Same Name Already Exists in Azure Active Directory

In some cases, you would get the below error. Don’t worry, let’s wait a few hours or try again after 24 hours.

Your Instance was not Created Because a Security Group with Same Name Already Exists in Azure Active Directory

Below is our Microsoft Defender for Identity instance.

Your Instance was not Created Because a Security Group with Same Name Already Exists in Azure Active Directory

Leave a Comment

Required fields are marked *