storage1 (Azure Blob storage): Blob storage supports all three primary authorization methods. You can use Shared Key for full account access, a Shared Access Signature (SAS) for delegated access, and Azure Active Directory (Azure AD) for identity-based access control (RBAC).

storage2 (Azure Files SMB): The type specifically mentions the SMB protocol. For mounting and accessing a file share over SMB, you can use the storage account's Shared Key or an identity-based method like Azure AD Domain Services (which is not an option in the list). A Shared Access Signature (SAS) is used for the FileREST API, not for authentication over the SMB protocol. Therefore, given the options, Shared Key only is the correct choice for SMB access.

storage3 (Azure Table storage): Like Blob storage, Table storage supports all three authorization methods. You can authenticate requests using the account's Shared Key, a SAS token for delegated access, or integrate with Azure AD for identity-based access management.

Microsoft Docs, "Mount SMB Azure file share on Windows." This document's instructions demonstrate using the storage account key (Shared Key) to authenticate and mount a file share over the SMB protocol. It does not mention SAS as a method for mounting.

Microsoft Docs, "Authorize access to data in Azure Storage." This document provides a general overview, but the specific protocol limitations are key. It states SAS is a valid authorization method for the Files service, which is true for REST operations, but not for SMB mounting.

Microsoft Docs, "Overview of Azure Files identity-based authentication options for SMB access." This resource details the identity-based options (Azure AD) and also explicitly mentions using the storage account key for access over SMB, reinforcing it as a valid method. It does not mention SAS for SMB.