Skip to content

Commit a41f426

Browse files
committed
hyphens
1 parent ed803e4 commit a41f426

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/aks/managed-aad.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -10,13 +10,13 @@ ms.date: 03/24/2020
1010
# Integrate Azure AD in Azure Kubernetes Service (Preview)
1111

1212
> [!Note]
13-
> Existing AKS clusters with AAD (Azure Active Directory) integration are not affected by the new AKS managed AAD experience.
13+
> Existing AKS clusters with AAD (Azure Active Directory) integration are not affected by the new AKS-managed AAD experience.
1414
15-
Azure AD integration with AKS managed AAD is designed to simplify the Azure AD integration experience, where users were previously required to create a client app, a server app, and required the Azure AD tenant to grant Directory Read permissions. In the new version, the AKS resource provider manages the client and server apps for you.
15+
Azure AD integration with AKS-managed AAD is designed to simplify the Azure AD integration experience, where users were previously required to create a client app, a server app, and required the Azure AD tenant to grant Directory Read permissions. In the new version, the AKS resource provider manages the client and server apps for you.
1616

1717
## Limitations
1818

19-
* You can't currently upgrade an existing AKS AAD Integrated cluster to the new AKS managed AAD experience.
19+
* You can't currently upgrade an existing AKS AAD Integrated cluster to the new AKS-managed AAD experience.
2020

2121
> [!IMPORTANT]
2222
> AKS preview features are available on a self-service, opt-in basis. Previews are provided "as-is" and "as available," and are excluded from the Service Level Agreements and limited warranty. AKS previews are partially covered by customer support on a best-effort basis. As such, these features are not meant for production use. For more information, see the following support articles:
@@ -104,7 +104,7 @@ Alternatively, if you first create a group and add members, you can enable the A
104104
az aks create -g MyResourceGroup -n MyManagedCluster --enable-aad [--aad-admin-group-object-ids <id>] [--aad-tenant-id <id>]
105105
```
106106

107-
A successful creation of an AKS Managed AAD cluster has the following section in the response body
107+
A successful creation of an AKS-managed AAD cluster has the following section in the response body
108108
```
109109
"Azure ADProfile": {
110110
"adminGroupObjectIds": null,
@@ -148,7 +148,7 @@ The user above gets an error because the user is not a part of a group that has
148148

149149
## Next steps
150150

151-
Learn about [Azure AD Role Based Access Control][azure-ad-rbac].
151+
Learn about [Azure AD Role-Based Access Control][azure-ad-rbac].
152152
Use [kubelogin][https://github.com/Azure/kubelogin] to use features for azure authentication that are not available in kubectl
153153

154154
<!-- LINKS - Internal -->

0 commit comments

Comments
 (0)