Skip to content

Commit 1af44b1

Browse files
committed
update for warning
1 parent 4b06089 commit 1af44b1

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

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

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,6 @@ A user that has logged into a SQL on-demand resource must be authorized to acces
2626
- [Shared access signature](?tabs=shared-access-signature)
2727
- [User Identity](?tabs=user-identity)
2828
- [Managed Identity](?tabs=managed-identity)
29-
- [Anonymous access](?tab=anonymous-access)
3029

3130
> [!NOTE]
3231
> [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).
@@ -95,7 +94,7 @@ If you want to re-enable it again, refer to the [force Azure AD pass-through](#f
9594

9695
Before accessing the data, the Azure Storage administrator must grant permissions to Managed Identity for accessing the data. Granting permissions to Managed Identity is done the same way as granting permission to any other Azure AD user.
9796

98-
### [Anonymous access](#tab/anonymous-access)
97+
### [Anonymous access](#tab/public-access)
9998

10099
You can access publicly available files placed on Azure storage accounts that [allow anonymous access](/azure/storage/blobs/storage-manage-access-to-resources.md).
101100

0 commit comments

Comments
 (0)