From bfeb9ee8416bc4e83e6fec5731e5a57127b3e868 Mon Sep 17 00:00:00 2001
From: solid03 <90660726+solid03@users.noreply.github.com>
Date: Tue, 29 Jul 2025 18:35:45 -0400
Subject: [PATCH] Update create-group-managed-service-account.md

Add clarifying information for sAMAccountName requirements copied from from New-ADServiceAccount documentation
---
 .../create-group-managed-service-account.md                 | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/articles/azure-monitor/scom-manage-instance/create-group-managed-service-account.md b/articles/azure-monitor/scom-manage-instance/create-group-managed-service-account.md
index fd2cb22686..9699d08d16 100644
--- a/articles/azure-monitor/scom-manage-instance/create-group-managed-service-account.md
+++ b/articles/azure-monitor/scom-manage-instance/create-group-managed-service-account.md
@@ -61,7 +61,9 @@ In that command:
 - `MSOMHSvc/ContosoLB.aquiladom.com`, `SMSOMHSvc/ContosoLB`, `MSOMSdkSvc/ContosoLB.aquiladom.com`, and `MSOMSdkSvc/ContosoLB` are service principal names.
 
 > [!NOTE]
-> If the gMSA name is longer than 14 characters, ensure that you set `SamAccountName` at less than 15 characters, including the `$` sign.
+> If the gMSA name is longer than 15 characters, ensure that you set the `-SamAccountName` parameter at 15 characters or less, excluding the `$` sign, to be compatible with older operating systems.
+>
+> Note: If the specified SAMAccountName string doesn't end with a `$`, one is appended if necessary.
 
 If the root key isn't effective, use the following command:
 
@@ -76,4 +78,4 @@ Ensure that the created gMSA account is a local admin account. If there are any
 
 ## Next steps
 
-[Store domain credentials in Azure Key Vault](store-domain-credentials-key-vault.md)
\ No newline at end of file
+[Store domain credentials in Azure Key Vault](store-domain-credentials-key-vault.md)