Skip to content

Commit 2b56148

Browse files
authored
Improved Correctness Score
Improved Correctness Score
1 parent fed8fa8 commit 2b56148

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -27,8 +27,8 @@ The Managed Identity (MI) option is available for the following Databases:
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
2929
> [!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.
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.
3232
3333

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

0 commit comments

Comments
 (0)