From 2d2a66ce782f3f456226f107b86ae1efa06c0733 Mon Sep 17 00:00:00 2001 From: tay caliguiri Date: Tue, 30 Dec 2025 17:55:41 -0500 Subject: [PATCH] gmsa-unsupported-for-action-modules --- docs/accessanalyzer/12.0/admin/settings/connection/gmsa.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/accessanalyzer/12.0/admin/settings/connection/gmsa.md b/docs/accessanalyzer/12.0/admin/settings/connection/gmsa.md index 06b5a0fa35..2a98ee4628 100644 --- a/docs/accessanalyzer/12.0/admin/settings/connection/gmsa.md +++ b/docs/accessanalyzer/12.0/admin/settings/connection/gmsa.md @@ -26,6 +26,9 @@ For FSAA, remote scans using gMSA credentials need to use the Windows Service la mechanism in the query configuration. ::: +:::note Action Modules +Using action modules with gMSAs is not currently supported. +::: See the Microsoft [Group Managed Service Accounts](https://learn.microsoft.com/en-us/windows-server/security/group-managed-service-accounts/group-managed-service-accounts-overview)