removed section: shared access key

Author: stevenmatthew

articles/storage/blobs/blob-containers-portal.md

@@ -7,7 +7,7 @@ author: stevenmatthew
 
 ms.service: storage
 ms.topic: how-to
-ms.date: 04/13/2022
+ms.date: 07/18/2022
 ms.author: shaas
 ms.subservice: blobs
 ---
@@ -84,16 +84,6 @@ Azure Active Directory (Azure AD) offers optimum security for Blob Storage resou
 
 You can read about the assignment of roles at [Assign Azure roles using the Azure portal](assign-azure-role-data-access.md?tabs=portal).
 
-### Use Shared Key authorization for data access
-
-A request to Azure Storage can be authorized using either your Azure AD account or the storage account access key. You can use portal to determine which method you are using, and switch between the two if you have the appropriate permissions. Follow the steps within the [Determine the current authentication method](authorize-data-operations-portal.md#determine-the-current-authentication-method) section.
-
-You may choose to use Azure AD authorization by default for data access when you create a storage account. You can accomplish this by following the steps within [Default to Azure AD authorization in the Azure portal](authorize-data-operations-portal.md#default-to-azure-ad-authorization-in-the-azure-portal).
-
-Shared Key authentication does not associate an identity with the caller, therefore permission-based authorization cannot be performed. The caller can receive full access to all operations on all resources including data, setting owner, and access control lists (ACLs).
-
-To minimize potential security vulnerabilities inherent in Shared Key, Azure AD authorization is recommended for use with your blobs when possible. For more information, read [Authorize access to blobs using Azure Active Directory](authorize-access-azure-active-directory.md). To disable Shared Key access, follow the steps within the [Prevent Shared Key authorization for an Azure Storage account](../common/shared-key-authorization-prevent.md?tabs=portal) article.
-
 ### Enable anonymous public read access
 
 Although anonymous read access for containers is supported, it's disabled by default. All access requests must require authorization until anonymous access is explicitly enabled. After anonymous access is enabled, any client will be able to read data within that container without authorizing the request.