Skip to content

Commit fed8fa8

Browse files
authored
Added an Important note section
Added an Important note section
1 parent 01934ee commit fed8fa8

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

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

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,10 @@ The Managed Identity (MI) option is available for the following Databases:
2626
> 1. Managed Identity (MI) is currently available only in public regions. It will be rolled out to other regions in future releases.
2727
> 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.
2828
29+
> [!IMPORTANT]
30+
> 1. It's recomanded not to update the Managed Identity after cluster recreation as it can disrupt cluster operation.
31+
> 2. When recreating 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.
32+
2933

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

0 commit comments

Comments
 (0)