ADGroup: New-ADGroup fails when a distinguished name is used for GroupName

Details of the scenario you tried and the problem that is occurring

Simple to reproduce: Just try to configure same group in different domains. This is because groupname is the only parameter which is part of the key properties.

Verbose logs showing the problem

Compilation errors occurred while processing configuration 'XXXXX'. Please review the errors reported in error stream and modify your configuration code appropriately.
STDERR: A conflict was detected between resources '[xADGroup]Add_group_DL_SQL_C2_DB_XXXX_owner_xxxx.local (C:\XXX)' and '[xADGroup]Add_group_DL_SQL_C2_DB_XXXX_db_owner_xxx.local (C:\XXX)' in node 'localhost'. Resources have identical key properties but there are differences in the following non-key properties:

Suggested solution to the issue

Add DomainController as key property. Because this is not mandatory now this can break "old" DSC configurations. I think this is important to discuss. If you have a look at xAdUser domain is part of the key property. I think this should be consistent for both resources.

Version of the DSC module that was used ('dev' if using current dev branch)

2.26.0.0

Start with the xADGroup resource and compare its key properties with xAdUser, focusing on the reported New-ADGroup behavior when GroupName is a distinguished name. Review how DomainController is currently handled and consider the compatibility concern for existing DSC configurations. Done means the conflict is addressed without leaving the old-configuration impact unresolved.