Run PowerShell commands with Azure AD credentials to access blob or queue data
Azure Storage provides extensions for PowerShell that enable you to sign in and run scripting commands with Azure Active Directory (Azure AD) credentials. When you sign in to PowerShell with Azure AD credentials, an OAuth 2.0 access token is returned. That token is automatically used by PowerShell 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 and queue data to an Azure AD security principal via role-based access control (RBAC). For more information about Azure roles in Azure Storage, see Manage access rights to Azure Storage data with RBAC.
The Azure Storage extensions are supported for operations on blob and queue data. Which operations you may call depends on the permissions granted to the Azure AD security principal with which you sign in to PowerShell. Permissions to Azure Storage containers or queues are assigned via RBAC. For example, if you have been assigned the Blob Data Reader role, then you can run scripting commands that read data from a container or queue. If you have been assigned the Blob Data Contributor role, then you can run scripting commands that read, write, or delete a container or queue or the data they contain.
For details about the permissions required for each Azure Storage operation on a container or queue, see Call storage operations with OAuth tokens.
Call PowerShell commands using Azure AD credentials
This article has been updated to use the new Azure PowerShell Az module. You can still use the AzureRM module, which will continue to receive bug fixes until at least December 2020. To learn more about the new Az module and AzureRM compatibility, see Introducing the new Azure PowerShell Az module. For Az module installation instructions, see Install Azure PowerShell.
To use Azure PowerShell to sign in and run subsequent operations against Azure Storage using Azure AD credentials, create a storage context to reference the storage account, and include the
The following example shows how to create a container in a new storage account from Azure PowerShell using your Azure AD credentials. Remember to replace placeholder values in angle brackets with your own values:
Sign in to your Azure account with the Connect-AzAccount command:
For more information about signing into Azure with PowerShell, see Sign in with Azure PowerShell.
Create an Azure resource group by calling New-AzResourceGroup.
$resourceGroup = "sample-resource-group-ps" $location = "eastus" New-AzResourceGroup -Name $resourceGroup -Location $location
Create a storage account by calling New-AzStorageAccount.
$storageAccount = New-AzStorageAccount -ResourceGroupName $resourceGroup ` -Name "<storage-account>" ` -SkuName Standard_LRS ` -Location $location `
Get the storage account context that specifies the new storage account by calling New-AzStorageContext. When acting on a storage account, you can reference the context instead of repeatedly passing in the credentials. Include the
-UseConnectedAccountparameter to call any subsequent data operations using your Azure AD credentials:
$ctx = New-AzStorageContext -StorageAccountName "<storage-account>" -UseConnectedAccount
Before you create the container, assign the Storage Blob Data Contributor role to yourself. Even though you are the account owner, you need explicit permissions to perform data operations against the storage account. For more information about assigning Azure roles, see Grant access to Azure blob and queue data with RBAC in the Azure portal.
Azure role assignments may take a few minutes to propagate.
Create a container by calling New-AzStorageContainer. Because this call uses the context created in the previous steps, the container is created using your Azure AD credentials.
$containerName = "sample-container" New-AzStorageContainer -Name $containerName -Context $ctx