You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/fundamentals/service-accounts-standalone-managed.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,8 @@ In Active Directory (AD), sMSAs are tied to a server that runs a service. You ca
23
23
24
24

25
25
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.
27
28
28
29
## sMSA benefits
29
30
@@ -68,7 +69,7 @@ Use the following table to associate challenges with mitigations.
68
69
| - | - |
69
70
| sMSAs are on a single server | Use a gMSA to use the account across servers |
70
71
| 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|
72
73
73
74
## Find sMSAs
74
75
@@ -99,11 +100,11 @@ To manage your sMSAs, you can use the following AD PowerShell cmdlets:
99
100
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>
100
101
[Managed Service Accounts: Understanding, Implementing, Best Practices, and Troubleshooting](/archive/blogs/askds/managed-service-accounts-understanding-implementing-best-practices-and-troubleshooting).
101
102
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.
103
104
104
105
## Next steps
105
106
106
-
To learn more about securing service accounts, see
107
+
To learn more about securing service accounts, see:
107
108
108
109
*[Securing on-premises service accounts](service-accounts-on-premises.md)
109
110
*[Secure group managed service accounts](service-accounts-group-managed.md)
0 commit comments