Skip to content

Commit 6b3365a

Browse files
authored
Update managed-identities.md
1 parent 1cf6409 commit 6b3365a

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/data-explorer/managed-identities.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.date: 03/12/2020
1414
A [managed identity from Azure Active Directory](/azure/active-directory/managed-identities-azure-resources/overview) allows your cluster to easily access other AAD-protected resources such as Azure Key Vault. The identity is managed by the Azure platform and doesn't require you to provision or rotate any secrets. This article shows you how to create a managed identity for Azure Data Explorer clusters. Managed identity configuration is currently supported only to [enable customer-managed keys for your cluster](/azure/data-explorer/security#customer-managed-keys-with-azure-key-vault).
1515

1616
> [!Note]
17-
> Managed identities for Azure Data Explorer won't behave as expected if your app is migrated across subscriptions or tenants. The app will need to obtain a new identity, which can be done by [disabling](#remove-a-system-assigned-identity) and [re-enabling](#add-a-system-assigned-identity) the feature. Access policies of downstream resources will also need to be updated to use the new identity.
17+
> Managed identities for Azure Data Explorer won't behave as expected if your Azure Data Explorer cluster is migrated across subscriptions or tenants. The app will need to obtain a new identity, which can be done by [disabling](#remove-a-system-assigned-identity) and [re-enabling](#add-a-system-assigned-identity) the feature. Access policies of downstream resources will also need to be updated to use the new identity.
1818
1919
## Add a system-assigned identity
2020
@@ -159,13 +159,13 @@ When the cluster is created, it has the following additional properties:
159159

160160
---
161161

162-
## Remove a system-assigned identity
162+
## Disable a system-assigned identity
163163

164164
Removing a system-assigned identity will also delete it from AAD. System-assigned identities are also automatically removed from AAD when the cluster resource is deleted. A system-assigned identity can be removed by disabling the feature. The system-assigned identity is removed using C#, ARM templates, or the Azure portal as detailed below.
165165

166166
# [Azure portal](#tab/portal)
167167

168-
### Remove a system-assigned identity using the Azure portal
168+
### Disable a system-assigned identity using the Azure portal
169169

170170
1. Sign in to the [Azure portal](https://portal.azure.com/).
171171
1. Select **Settings** > **Identity** in left pane of portal.

0 commit comments

Comments
 (0)