Sign in with Azure PowerShell
Azure PowerShell supports several authentication methods. The easiest way to get started is with Azure Cloud Shell, which automatically logs you in. With a local install, you can sign in interactively through your browser. When writing scripts for automation, the recommended approach is to use a service principal with the necessary permissions. When you restrict sign-in permissions as much as possible for your use case, you help keep your Azure resources secure.
After signing in, commands are run against your default subscription. To change your active subscription for a session, use the Set-AzContext cmdlet. To change the default subscription used when logging in with Azure PowerShell, use Set-AzDefault.
Your credentials are shared among multiple PowerShell sessions as long as you remain signed in. For more information, see the article on Persistent Credentials.
Sign in interactively
To sign in interactively, use the Connect-AzAccount cmdlet.
When run, this cmdlet will present a token string. To sign in, copy this string and paste it into https://microsoft.com/devicelogin in a browser. Your PowerShell session will be authenticated to connect to Azure.
Username/password credential authorization has been removed in Azure PowerShell due to changes in Active Directory authorization implementations and security concerns. If you use credential authorization for automation purposes, instead create a service principal.
Service principals are non-interactive Azure accounts. Like other user accounts, their permissions are managed with Azure Active Directory. By granting a service principal only the permissions it needs, your automation scripts stay secure.
To learn how to create a service principal for use with Azure PowerShell, see Create an Azure service principal with Azure PowerShell.
To sign in with a service principal, use the
-ServicePrincipal argument with the
Connect-AzAccount cmdlet. You'll also need the service principal's application ID,
sign-in credentials, and the tenant ID associate with the service principal. How you sign in with a service principal will depend on whether it's configured for password-based or certificate-based authentication.
To get the service principal's credentials as the appropriate object, use the Get-Credential cmdlet. This cmdlet will present a prompt for a username and password. Use the service principal ID for the username.
$pscredential = Get-Credential Connect-AzAccount -ServicePrincipal -Credential $pscredential -TenantId $tenantId
For automation scenarios, you need to create credentials from a user name and secure string:
$passwd = ConvertTo-SecureString <use a secure password here> -AsPlainText -Force $pscredential = New-Object System.Management.Automation.PSCredential('service principal name/id', $passwd) Connect-AzAccount -ServicePrincipal -Credential $pscredential -TenantId $tenantId
Make sure that you use good password storage practices when automating service principal connections.
Certificate-based authentication requires that Azure PowerShell can retrieve information from a local certificate store based on a certificate thumbprint.
Connect-AzAccount -ServicePrincipal -TenantId $tenantId -CertificateThumbprint <thumbprint>
In PowerShell 5.1, the certificate store can be managed and inspected with the PKI module. For PowerShell Core 6.x and later, the process is more complicated. The following scripts show you how to import an existing certificate into the certificate store accessible by PowerShell.
Import a certificate in PowerShell 5.1
# Import a PFX $credentials = Get-Credential -Message "Provide PFX private key password" Import-PfxCertificate -FilePath <path to certificate> -Password $credentials.Password -CertStoreLocation cert:\CurrentUser\My
Import a certificate in PowerShell Core 6.x and later
# Import a PFX $storeName = [System.Security.Cryptography.X509Certificates.StoreName]::My $storeLocation = [System.Security.Cryptography.X509Certificates.StoreLocation]::CurrentUser $store = [System.Security.Cryptography.X509Certificates.X509Store]::new($storeName, $storeLocation) $certPath = <path to certificate> $credentials = Get-Credential -Message "Provide PFX private key password" $flag = [System.Security.Cryptography.X509Certificates.X509KeyStorageFlags]::Exportable $certificate = [System.Security.Cryptography.X509Certificates.X509Certificate2]::new($certPath, $credentials.Password, $flag) $store.Open([System.Security.Cryptography.X509Certificates.OpenFlags]::ReadWrite) $store.Add($Certificate) $store.Close()
Sign in using a managed identity
Managed identities are a feature of Azure Active Directory. Managed identities are service principals assigned to resources that run in Azure. You can use a managed identity service principal for sign-in, and acquire an app-only access token to access other resources. Managed identities are only available on resources running in an Azure cloud.
To learn more about managed identities for Azure resources, see How to use managed identities for Azure resources on an Azure VM to acquire an access token.
Sign in with a non-default tenant or as a Cloud Solution Provider (CSP)
If your account is associated with more than one tenant, sign-in requires the use of the
when connecting. This parameter will work with any other sign-in method. When logging in, this parameter value
can either be the Azure object ID of the tenant (Tenant ID) or the fully qualified domain name of the tenant.
If you're a Cloud Solution Provider (CSP), the
-TenantId value must be a tenant ID.
Connect-AzAccount -TenantId 'xxxx-xxxx-xxxx-xxxx'
Sign in to another Cloud
Azure cloud services offer environments compliant with regional data-handling laws.
For accounts in a regional cloud, set the environment when you sign in with the
For example, if your account is in the China cloud:
Connect-AzAccount -Environment AzureChinaCloud
The following command gets a list of available environments:
Get-AzEnvironment | Select-Object Name