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/aks/managed-aad.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,13 +10,13 @@ ms.date: 03/24/2020
10
10
# Integrate Azure AD in Azure Kubernetes Service (Preview)
11
11
12
12
> [!Note]
13
-
> Existing AKS clusters with AAD (Azure Active Directory) integration are not affected by the new AKSmanaged AAD experience.
13
+
> Existing AKS clusters with AAD (Azure Active Directory) integration are not affected by the new AKS-managed AAD experience.
14
14
15
-
Azure AD integration with AKSmanaged 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.
16
16
17
17
## Limitations
18
18
19
-
* You can't currently upgrade an existing AKS AAD Integrated cluster to the new AKSmanaged AAD experience.
19
+
* You can't currently upgrade an existing AKS AAD Integrated cluster to the new AKS-managed AAD experience.
20
20
21
21
> [!IMPORTANT]
22
22
> 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
104
104
az aks create -g MyResourceGroup -n MyManagedCluster --enable-aad [--aad-admin-group-object-ids <id>] [--aad-tenant-id <id>]
105
105
```
106
106
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
108
108
```
109
109
"Azure ADProfile": {
110
110
"adminGroupObjectIds": null,
@@ -148,7 +148,7 @@ The user above gets an error because the user is not a part of a group that has
148
148
149
149
## Next steps
150
150
151
-
Learn about [Azure AD RoleBased Access Control][azure-ad-rbac].
151
+
Learn about [Azure AD Role-Based Access Control][azure-ad-rbac].
152
152
Use [kubelogin][https://github.com/Azure/kubelogin] to use features for azure authentication that are not available in kubectl
0 commit comments