Skip to content

Commit 9841627

Browse files
authored
Update service-accounts-group-managed.md
1 parent 4fd01af commit 9841627

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

articles/active-directory/fundamentals/service-accounts-group-managed.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -110,16 +110,15 @@ To manage gMSAs, use the following Active Directory PowerShell cmdlets:
110110
## Move to a gMSA
111111

112112
gMSAs are a secure service account type for on-premises. It's recommended you use gMSAs, if possible. In addition, consider moving your services to Azure and your service accounts to Azure Active Directory.
113+
114+
> [!NOTE]
115+
> Before you configure your service to use the gMSA, see [Get started with group managed service accounts](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/jj128431(v=ws.11)).
113116
114117
To move to a gMSA:
115118

116119
1. Ensure the Key Distribution Service (KDS) root key is deployed in the forest. This is a one-time operation. See, [Create the Key Distribution Services KDS Root Key](/windows-server/security/group-managed-service-accounts/create-the-key-distribution-services-kds-root-key).
117120
2. Create a new gMSA. See, [Getting Started with Group Managed Service Accounts](/windows-server/security/group-managed-service-accounts/getting-started-with-group-managed-service-accounts).
118121
3. Install the new gMSA on hosts that run the service.
119-
120-
> [!NOTE]
121-
> Before you configure your service to use the gMSA, see [Get started with group managed service accounts](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/jj128431(v=ws.11)).
122-
123122
4. Change your service identity to gMSA.
124123
5. Specify a blank password.
125124
6. Validate your service is working under the new gMSA identity.

0 commit comments

Comments
 (0)