Skip to content

Commit e8e04bd

Browse files
Update develop-storage-files-storage-access-control.md
1 parent c09cebb commit e8e04bd

File tree

1 file changed

+1
-5
lines changed

1 file changed

+1
-5
lines changed

articles/synapse-analytics/sql/develop-storage-files-storage-access-control.md

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -21,11 +21,7 @@ This article describes the types of credentials you can use and how credential l
2121

2222
## Supported storage authorization types
2323

24-
A user that has logged into a SQL on-demand resource must be authorized to access and query the files in Azure Storage if the files are not publicly available. Three authorization types are supported:
25-
26-
- [User Identity](?tabs=user-identity)
27-
- [Shared access signature](?tabs=shared-access-signature)
28-
- [Managed Identity](?tabs=managed-identity)
24+
A user that has logged into a SQL on-demand resource must be authorized to access and query the files in Azure Storage if the files are not publicly available. You can use three authorization types to access non-public storage - [User Identity](?tabs=user-identity), [Shared access signature](?tabs=shared-access-signature), and [Managed Identity](?tabs=managed-identity).
2925

3026
> [!NOTE]
3127
> [Azure AD pass-through](#force-azure-ad-pass-through) is the default behavior when you create a workspace. If you use it, you don't need to create credentials for each storage account accessed using Azure AD logins. You can [disable this behavior](#disable-forcing-azure-ad-pass-through).

0 commit comments

Comments
 (0)