Skip to content

Commit 4900906

Browse files
Update use-managed-identity-for-sql-database-authentication-in-azure-hdinsight.md
1 parent 0109174 commit 4900906

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
@@ -29,7 +29,7 @@ The Managed Identity (MI) option is available for the following Databases:
2929

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

32-
1. During cluster creation, navigate to the Storage section and select the SQL database for Ambari, Hive, Oozie, or Ranger. Choose Managed Identity as the Authentication method.
32+
1. During cluster creation, navigate to the Storage section and select the SQL database for Ambari/Hive/Oozie. Choose Managed Identity as the Authentication method.
3333

3434
:::image type="content" source="./media/use-managed-identity-for-sql-database-authentication-in-azure-hdinsight/basic-tab.png" alt-text="Screenshot showing the basic tab." border="true" lightbox="./media/use-managed-identity-for-sql-database-authentication-in-azure-hdinsight/basic-tab.png":::
3535

@@ -39,7 +39,7 @@ The Managed Identity (MI) option is available for the following Databases:
3939

4040
1. Create a contained user with the Managed identity in the corresponding SQL database.
4141

42-
Follow these steps in the Azure SQL database query editor to create a database user and grant it read-write permissions. Perform these steps for each SQL Database you're going to use for different services such as Ambari, Hive, Oozie, or Ranger.
42+
Follow these steps in the Azure SQL database query editor to create a database user and grant it read-write permissions. Perform these steps for each SQL Database you're going to use for different services such as Ambari, Hive, or Oozie.
4343

4444

4545
> [!NOTE]

0 commit comments

Comments
 (0)