Skip to content

Commit c46e207

Browse files
authored
Update data-virtualization-overview.md
PR review: Corrected spelling
1 parent a271ad9 commit c46e207

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

azure-sql/database/data-virtualization-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -141,7 +141,7 @@ User identity, also known as "Microsoft Entra pass-through", is an authorization
141141
- As an alternative, you can specify fine-grained ACL rules to access files and folders. Even if you are an Owner of a Storage Account, you still need to add yourself into one of the Storage Blob Data roles. To learn more about access control in Azure Data Lake Store Gen2, see [Access control in Azure Data Lake Storage Gen2](/azure/storage/blobs/data-lake-storage-access-control).
142142
- Microsoft Entra pass-through authentication does not support SQL authenticated login types.
143143
144-
1. Create a database scoped credential for a Microsoft Entra ID account with access to the Azure SQL Database. Subsitute `<UserCredential>` for the name of the identity, such as `identity-<random string>`. In the following example, `IDENTITY = 'User Identity'` is a hard-coded string. With a managed user identity, a database master key is not required because the credential doesn't contain a `SECRET`.
144+
1. Create a database scoped credential for a Microsoft Entra ID account with access to the Azure SQL Database. Substitute `<UserCredential>` for the name of the identity, such as `identity-<random string>`. In the following example, `IDENTITY = 'User Identity'` is a hard-coded string. With a managed user identity, a database master key is not required because the credential doesn't contain a `SECRET`.
145145

146146
```sql
147147
CREATE DATABASE SCOPED CREDENTIAL <UserCredential>

0 commit comments

Comments
 (0)