Forum Discussion
viniciuscarmo
Dec 08, 2021Copper Contributor
Error create instance Defender for identity
Hello guys, I need help. I am create a intance the Defender for identity but receive mensage: the instance was not created because there is already a security group with the same name as the azur...
MrDavidFox
Oct 18, 2022Copper Contributor
I know this is old but just in case anyone has the same problem:
There are 3 default security groups called
Azure ATP {instance name} Administrator
Azure ATP {instance name} Users
Azure ATP {instance name} Viewers
https://learn.microsoft.com/en-us/defender-for-identity/role-groups
These may be empty but need to be deleted for defender for identity to proceed.
There are 3 default security groups called
Azure ATP {instance name} Administrator
Azure ATP {instance name} Users
Azure ATP {instance name} Viewers
https://learn.microsoft.com/en-us/defender-for-identity/role-groups
These may be empty but need to be deleted for defender for identity to proceed.
- wstitmgrJan 31, 2024Copper ContributorThank you VERY much for posting this!
- terryhugillSep 11, 2023Copper ContributorThank you, that helped me out.
- jnitterauerAug 24, 2023Copper Contributor
Microsoft's error messages should include the details like the name(s) of the groups that need to be deleted so people have clear (not nebulous) direction. Thanks for the clarification.
- wstitmgrJan 31, 2024Copper Contributor
jnitterauer EVERYTHING microsoft takes 10 times the effort it should. Not listing the names of the conflicting groups, forcing a delay-of-game while admins are forced to find this information is very much on brand for them.
- Mark_BrethertonMay 31, 2023Copper Contributorthat is still relevant David (thanks)
- NetworkCompanyMay 31, 2023Copper ContributorI'm curious where the groups came from and why some tenants have this issue and others don't,
- Mark_BrethertonMay 31, 2023Copper Contributor
NetworkCompany Not sure where they came from, I was assuming it was an Azure service template or something, I know I didn't previously create them manually. We are synchronising our accounts from on-prem AD and those accounts were Azure Native.