Any known issue of using gMSA as destination in K2 Five 5.9?

Group Managed Service Account (gMSA)

https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/understand-service-accounts#group-managed-service-accounts

I have an AD account that I need to assign to destination and use K2 REST API for the Tasks.

Using gMSA would allow me to forgo the password maintenance.

Did anyone try gMSA as a destination?  (or gMSA mapped to a K2 Role)