I'm trying to solve a conundrum for my DBAs and developers. We have an application that is running under a gMSA (group managed service account) identity. This application needs to access a SQL database, and we prefer to grant access by using groups whenever possible. However, when adding the gMSA to a security group that has access to the DB, SQL Server is unable to resolve the account as a member of the group. Here's the kicker: when the gMSA is added directly to the DB permissions, it works flawlessly. Are there any restrictions around nesting gMSAs in security groups that I am not aware of?