Skip to content

Commit a019479

Browse files
authored
Update concept-best-practices-network.md
Clarified wording in example - the usage of the phrase "SQL authentication" is incorrect in this context and is contradicted by the sentences which follow it.
1 parent 328f34c commit a019479

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/purview/concept-best-practices-network.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -85,7 +85,7 @@ Here are some best practices:
8585

8686
When you're scanning a data source in Microsoft Purview, you need to provide a credential. Microsoft Purview can then read the metadata of the assets by using the Azure integration runtime in the destination data source. When you're using a public network, authentication options and requirements vary based on the following factors:
8787

88-
- **Data source type**. For example, if the data source is Azure SQL Database, you need to use SQL authentication with db_datareader access to each database. This can be a user-managed identity or a Microsoft Purview managed identity. Or it can be a service principal in Azure Active Directory added to SQL Database as db_datareader.
88+
- **Data source type**. For example, if the data source is Azure SQL Database, you need to use a login with db_datareader access to each database. This can be a user-managed identity or a Microsoft Purview managed identity. Or it can be a service principal in Azure Active Directory added to SQL Database as db_datareader.
8989

9090
If the data source is Azure Blob Storage, you can use a Microsoft Purview managed identity, or a service principal in Azure Active Directory added as a Blob Storage Data Reader role on the Azure storage account. Or use the storage account's key.
9191

0 commit comments

Comments
 (0)