Different AG groups have the exactly same group_id value if the group names are same and the ‘CLUSTER_TYPE = EXTERNAL/NONE’
For external/none cluster type, since there is no orchestration, each replica needs to know how to independently determine the AG ID, thus the AG group name is used in hash.
Let’s say you have different Availability groups with cluster type ‘External’ or ‘None’ in different environments. As long as the AG groups have same name, the group_ids of AG groups are same, and the resource_ids are same as well.
Here is a screenshot of a AG group with Cluster type ‘None’ in Windows.
And Here is a screenshot of a AG group with Cluster type ‘External’ in Linux
How does it impact the product?
If you have applications using group_id or resource_id(For example, Microsoft SCOM) to determine the availability groups , please make sure to use different names when creating the availability groups.