Merge pull request #293533 from sreekzz/patch-558019

Updated the Note

Author: prmerger-automator[bot]

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

@@ -23,12 +23,12 @@ The Managed Identity (MI) option is available for the following Databases:
 |Ranger (ESP)|❌ | ❌ |
 
 > [!NOTE]
-> * Managed Identity (MI) is currently available only in public regions.
+> * Managed Identity (MI) is currently available only in public regions. It will be rolled out to other regions (Federal and China regions) in future releases.
 > * 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.
 
 > [!IMPORTANT]
 > * It's recommended not to update the Managed Identity after cluster recreation as it can disrupt cluster operation.
-> *  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.
+> * When you recreate an MSI with the same name, you 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.
 
 
 ## Steps to Use Managed Identity during cluster creation in Azure portal