Install Azure CLI with zypper

For Linux distributions with zypper, such as openSUSE or SLES, there's a package available for the Azure CLI. This package has been tested with openSUSE 42.2 and later, and SLES 12 SP 2 and later.

The current version of the CLI is 2.0.67. For information about the latest release, see the release notes. To find your installed version and see if you need to update, run az --version.

Important

The RPM package of the Azure CLI depends on the python package. On your system, this may be a Python version which predates the requirement of Python 2.7.x. If this affects you, find a replacement python package or follow the manual install instructions.

Be aware that Python 2 is being end-of-lifed on January 1, 2020, and will no longer receive updates. For this reason, upgrade to Python 3 when possible. The Azure CLI is compatible with Python 3.6 and higher.

Install

  1. Install curl:

    sudo zypper install -y curl
    
  2. Import the Microsoft repository key:

    sudo rpm --import https://packages.microsoft.com/keys/microsoft.asc
    
  3. Create local azure-cli repository information:

    sudo zypper addrepo --name 'Azure CLI' --check https://packages.microsoft.com/yumrepos/azure-cli azure-cli
    
  4. Update the zypper package index and install:

    sudo zypper install --from azure-cli -y azure-cli
    

You can then run the Azure CLI with the az command. To sign in, use az login command.

  1. Run the login command.

    az login
    

    If the CLI can open your default browser, it will do so and load a sign-in page.

    Otherwise, you need to open a browser page and follow the instructions on the command line to enter an authorization code after navigating to https://aka.ms/devicelogin in your browser.

  2. Sign in with your account credentials in the browser.

To learn more about different authentication methods, see Sign in with Azure CLI.

Troubleshooting

Here are some common problems seen when installing with zypper. If you experience a problem not covered here, file an issue on github.

Proxy blocks connection

If you're unable to connect to an external resource due to a proxy, make sure that you've correctly set the HTTP_PROXY and HTTPS_PROXY variables in your shell. You will need to contact your system administrator to know what host(s) and port(s) to use for these proxies.

These values are respected by many Linux programs, including those which are used in the install process. To set these values:

# No auth
export HTTP_PROXY=http://[proxy]:[port]
export HTTPS_PROXY=https://[proxy]:[port]

# Basic auth
export HTTP_PROXY=http://[username]:[password]@[proxy]:[port]
export HTTPS_PROXY=https://[username]:[password]@[proxy]:[port]

Important

If you are behind a proxy, these shell variables must be set to connect to Azure services with the CLI. If you are not using basic auth, it's recommended to export these variables in your .bashrc file. Always follow your business' security policies and the requirements of your system administrator.

You may also want to explicitly configure zypper (via yast2) to use this proxy at all times. To do so, run the yast2 proxy command as superuser, and fill in the information presented in the form. If you have a window manager available on your system, you can also use the Network Services > Proxy pane in the YaST Control Center.

For advanced configuration or more information, see the OpenSUSE Proxy configuration documentation

In order to get the Microsoft signing key and get the package from our repository, your proxy needs to allow HTTPS connections to the following addresses:

  • https://packages.microsoft.com
  • https://download.opensuse.org

CLI fails to install or run on Windows Subsystem for Linux

Since Windows Subsystem for Linux (WSL) is a system call translation layer on top of the Windows platform, you might experience an error when trying to install or run the Azure CLI. The CLI relies on some features that may have a bug in WSL. If you experience an error no matter how you install the CLI, there's a good chance it's an issue with WSL and not with the CLI install process.

To troubleshoot your WSL installation and possibly resolve issues:

  • If you can, run an identical install process on a Linux machine or VM to see if it succeeds. If it does, your issue is almost certainly related to WSL. To start a Linux VM in Azure, see the create a Linux VM in the Azure Portal documentation.
  • Make sure that you're running the latest version of WSL. To get the latest version, update your Windows 10 installation.
  • Check for any open issues with WSL which might address your problem. Often there will be suggestions on how to work around the problem, or information about a release where the issue will be fixed.
  • If there are no existing issues for your problem, file a new issue with WSL and make sure that you include as much information as possible.

If you continue to have issues installing or running on WSL, consider installing the CLI for Windows.

Update

You can update the package with the zypper update command.

sudo zypper refresh
sudo zypper update azure-cli

Uninstall

If you decide to uninstall the Azure CLI, we're sorry to see you go. Before you uninstall, use the az feedback command to let us know what could be improved or fixed. Our goal is to make the Azure CLI bug-free and user-friendly. If you found a bug, we'd appreciate it if you file a GitHub issue.

  1. Remove the package from your system.

    sudo zypper remove -y azure-cli
    
  2. If you don't plan to reinstall the CLI, remove the repository information.

    sudo zypper removerepo azure-cli
    
  3. If you removed the repository information, also remove the Microsoft GPG signature key.

    MSFT_KEY=`rpm -qa gpg-pubkey /* --qf "%{version}-%{release} %{summary}\n" | grep Microsoft | awk '{print $1}'`
    sudo rpm -e --allmatches gpg-pubkey-$MSFT_KEY
    

Next Steps

Now that you've installed the Azure CLI, take a short tour of its features and common commands.