Why is there a "User Manager Group" role created automatically after setting up a Failover Cluster?

Dear kedar giri,

We understand your concern, especially since this role was not manually created and appears automatically after adding cluster nodes. Based on current behavior in Windows Server 2025, this role is not part of the standard failover cluster configuration and is not documented as a default system role. It may have been introduced by a third-party application, a management tool, or a background service during cluster setup.

To determine its origin, we recommend checking the role’s associated resources and dependencies within Failover Cluster Manager, and reviewing recent event logs for any automated role creation. If the role is inactive or not linked to critical services, it is generally safe to leave it in place. However, if it’s not serving a known purpose, you may consider disabling or removing it after confirming it’s not required by your environment.

No immediate configuration or permission changes are necessary unless the role is actively impacting cluster operations.

Let me know how it goes, and if this answer helps, feel free to hit “Accept Answer” so others can benefit too 😊 T&B, Harry.

the role we’re talking about has nothing to do with any third party application or service, it’s 100% made in Microsoft, the role is automatically created immediately after creating the cluster, both under domain or in DMZ. Apparently it has to do with the different users’ permissions in cluster’s management, but I have no idea if deleting it could create any issue, or about the advantages of keeping it. But I’m quite completely sure that there is still no Microsoft documentation on this matter.