Skip to content

Commit ea2acb7

Browse files
author
Sreekanth Iyer (Ushta Te Consultancy Services)
committed
Merge branch 'storage-tab-image-change' of https://github.com/sreekzz/azure-docs-pr into storage-tab-image-change
2 parents 613ca36 + 2b56148 commit ea2acb7

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

articles/hdinsight/use-managed-identity-for-sql-database-authentication-in-azure-hdinsight.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,11 @@ The Managed Identity (MI) option is available for the following Databases:
2424

2525
> [!NOTE]
2626
> 1. Managed Identity (MI) is currently available only in public regions. It will be rolled out to other regions in future releases.
27-
> 2. MI option in't enabled by default. To get it enabled, submit a [support ticket](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/overview) with your subscription and region details.
27+
> 2. MI option isn't enabled by default. To get it enabled, submit a [support ticket](https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/overview) with your subscription and region details.
28+
29+
> [!IMPORTANT]
30+
> 1. It's recommended not to update the Managed Identity after cluster recreation as it can disrupt cluster operation.
31+
> 2. When you recreate an MSI with the same name, users must recreate the contained user and reassign roles, as the new MSI will have different object and client IDs even if the name remains unchanged.
2832
2933

3034
## Steps to Use Managed Identity during cluster creation in Azure portal

0 commit comments

Comments
 (0)