About Microsoft Azure Blob Storage
--file $DESTINATION_FILE --output tableecho "Done"Microsoft Azure Storage ExplorerAzure Storage Explorer is a standalone app from Microsoft. It allows you to easily work with both Azure Storage and Azure Stack Hub Storage data on Windows, macOS, and Linux computers. If you want an easy way to manage your Azure Stack Hub Storage data, then consider using Microsoft Azure Storage Explorer.For more information about configuring Azure Storage Explorer to work with Azure Stack Hub, see Connect Storage Explorer to an Azure Stack Hub subscription.For more information about Microsoft Azure Storage Explorer, see Get started with storage explorer.BlobfuseBlobfuse is a virtual file system driver for Azure Blob Storage, which allows you to access your existing block blob data in your storage account through the Linux file system. Azure Blob Storage is an object storage service and therefore doesn't have a hierarchical namespace. Blobfuse provides this namespace using the virtual directory scheme with the use of forward-slash / as a delimiter. Blobfuse works on both Azure and Azure Stack Hub.To learn more about mounting blob storage as a file system with Blobfuse on Linux, see How to mount Blob storage as a file system with Blobfuse.For Azure Stack Hub, blobEndpoint needs to be specified while configuring your storage account credentials along with accountName, accountKey/sasToken, and containerName.In the Azure Stack Development Kit (ASDK), the blobEndpoint should be myaccount.blob.local.azurestack.external. In Azure Stack Hub integrated system, contact your cloud admin if you're not sure about your endpoint.accountKey and sasToken can only be configured one at a time. When a storage account key is given, the credentials configuration file is in the following format:accountName myaccount accountKey myaccesskey== containerName mycontainer blobEndpoint myaccount.blob.local.azurestack.externalWhen a shared access token is given, the credentials configuration file is in the following format:accountName myaccount sasToken ?mysastoken containerName mycontainer blobEndpoint myaccount.blob.local.azurestack.externalNext stepsConnect storage explorer to an
Key features of the Microsoft Azure Blob Storage that are enabled through these drivers include:
- Microsoft Azure Blob Storage Account - SolarWinds
- Microsoft Azure Blob Storage Migration Tool
- Automating Snowpipe for Microsoft Azure Blob Storage
- Azure blob storage pricing - Microsoft Q A
- Microsoft Azure Storage Blob: Download multiple
- Microsoft Azure Blob Storage - Labelbox docs
- Configuring transfers with Microsoft Azure Blob Storage
Skip to main content This browser is no longer supported. Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Choose how to authorize access to blob data with Azure CLI Article10/12/2023 In this article -->Azure Storage provides extensions for Azure CLI that enable you to specify how you want to authorize operations on blob data. You can authorize data operations in the following ways:With a Microsoft Entra security principal. Microsoft recommends using Microsoft Entra credentials for superior security and ease of use.With the account access key or a shared access signature (SAS) token.Specify how data operations are authorizedAzure CLI commands for reading and writing blob data include the optional --auth-mode parameter. Specify this parameter to indicate how a data operation is to be authorized:Set the --auth-mode parameter to login to sign in using a Microsoft Entra security principal (recommended).Set the --auth-mode parameter to the legacy key value to attempt to retrieve the account access key to use for authorization. If you omit the --auth-mode parameter, then the Azure CLI also attempts to retrieve the access key.To use the --auth-mode parameter, make sure that you have installed Azure CLI version 2.0.46 or later. Run az --version to check your installed version.NoteWhen a storage account is locked with an Azure Resource Manager ReadOnly lock, the List Keys operation is not permitted for that storage account. List Keys is a POST operation, and all POST operations are prevented when a ReadOnly lock is configured for the account. For this reason, when the account is locked with a ReadOnly lock, users who do not already possess the account keys must use Microsoft Entra credentials to access blob data.ImportantIf you omit the --auth-mode parameter or set it to key, then the Azure CLI attempts to use the account access key for authorization. In this case, Microsoft recommends that you provide the access key either on the command or in the AZURE_STORAGE_KEY environment variable. For more information about environment variables, see the section titled Set environment variables for authorization parameters.If you do not provide the access key, then the Azure CLI attempts to call the Azure Storage resource provider to retrieve it for each operation. Performing many data operations that require a call to the resource provider may result in throttling. For more information about resource provider limits, see Scalability and performance targets for the Azure Storage resource provider.Authorize with Microsoft Entra credentialsWhen you sign in to Azure CLI with Microsoft Entra credentials, an OAuth 2.0 access token is returned. That token is automatically used by Azure CLI to authorize subsequent data operations against Blob or Queue storage. For supported operations, you no longer need to pass an account key or SAS token with the command.You can assign permissions to blob data to a Microsoft Entra security principal via Azure role-based access control (Azure RBAC). For more information about Azure roles in Azure Storage, see Assign an Azure role for access to blob data.Permissions for calling data operationsThe Azure
