Skip to content

Commit 18f54b9

Browse files
authored
Update service-accounts-standalone-managed.md
1 parent 09aae38 commit 18f54b9

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

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

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,8 @@ In Active Directory (AD), sMSAs are tied to a server that runs a service. You ca
2323

2424
![Screenshot of a service name and type under Active Directory Users and Computers.](./media/securing-service-accounts/secure-standalone-msa-image-1.png)
2525

26-
Managed service accounts were introduced in Windows Server 2008 R2 Active Directory Schema, and they require Windows Server 2008 R2, or later version.
26+
> [!NOTE]
27+
> Managed service accounts were introduced in Windows Server 2008 R2 Active Directory Schema, and they require Windows Server 2008 R2, or a later version.
2728
2829
## sMSA benefits
2930

@@ -68,7 +69,7 @@ Use the following table to associate challenges with mitigations.
6869
| - | - |
6970
| sMSAs are on a single server | Use a gMSA to use the account across servers |
7071
| sMSAs can't be used across domains | Use a gMSA to use the account across domains |
71-
| Not all applications support sMSAs| Use a gMSA, if possible. Otherwise, use a standard user account or a computer account, as recommended by the creator.|
72+
| Not all applications support sMSAs| Use a gMSA, if possible. Otherwise, use a standard user account or a computer account, as recommended by the creator|
7273

7374
## Find sMSAs
7475

@@ -99,11 +100,11 @@ To manage your sMSAs, you can use the following AD PowerShell cmdlets:
99100
If an application service supports sMSAs, but not gMSAs, and you're using a user account or computer account for the security context, see</br>
100101
[Managed Service Accounts: Understanding, Implementing, Best Practices, and Troubleshooting](/archive/blogs/askds/managed-service-accounts-understanding-implementing-best-practices-and-troubleshooting).
101102

102-
If possible, move resources to Azure and use Azure managed identities or service principals.
103+
If possible, move resources to Azure and use Azure managed identities, or service principals.
103104

104105
## Next steps
105106

106-
To learn more about securing service accounts, see
107+
To learn more about securing service accounts, see:
107108

108109
* [Securing on-premises service accounts](service-accounts-on-premises.md)
109110
* [Secure group managed service accounts](service-accounts-group-managed.md)

0 commit comments

Comments
 (0)