Paul: I wouldn't mind if there were this possibility, but I would consider it bad design to reflect it in the UI. IMHO, a hidden pref would be better. Anyway, since system-wide proxy autoconfiguration is possible since OS X 10.3.2, I also can't see any advantage in having browser-specific options. MacProxy provides system-wide network proxy support for the Mac, including for applications without proxy support. It provides a simple and intuitive user interface via a menulet control and a System Preference pane.
- Mac Proxy 3 0 10 – System Wide Network Proxy Supports
- Mac Proxy 3 0 10 – System Wide Network Proxy Supported
- Mac Proxy 3 0 10 – System Wide Network Proxy Supporting
This article explains how to install the Azure PowerShell modules usingPowerShellGet. These instructions work on Windows,macOS, and Linux platforms.
Azure PowerShell is also available in Azure Cloud Shell and is nowpreinstalled in Docker images.
Requirements
Note
PowerShell 7.x and later is the recommended version of PowerShell for use with Azure PowerShell onall platforms.
Azure PowerShell works with PowerShell 6.2.4 and later on all platforms. It is also supported withPowerShell 5.1 on Windows. Install thelatest version of PowerShell available foryour operating system. Azure PowerShell has no additional requirements when run on PowerShell 6.2.4and later.
To check your PowerShell version, run the command:
To use Azure PowerShell in PowerShell 5.1 on Windows:
- Update toWindows PowerShell 5.1.If you're on Windows 10 version 1607 or higher, you already have PowerShell 5.1 installed.
- Install .NET Framework 4.7.2 or later.
- Make sure you have the latest version of PowerShellGet. Run
Install-Module -Name PowerShellGet -Force.
Install the Azure PowerShell module
Warning
We do not support having both the AzureRM and Az modules installed for PowerShell 5.1 on Windowsat the same time. If you need to keep AzureRM available on your system, install the Az module forPowerShell 6.2.4 or later.
Mac Proxy 3 0 10 – System Wide Network Proxy Supports
Using the PowerShellGet cmdlets is the preferred installation method. Install the Az module for thecurrent user only. This is the recommended installation scope. This method works the same onWindows, macOS, and Linux platforms. Run the following command from a PowerShell session:
By default, the PowerShell gallery isn't configured as a trusted repository for PowerShellGet. Thefirst time you use the PSGallery you see the following prompt:
Answer Yes or Yes to All to continue with the installation.
Mac Proxy 3 0 10 – System Wide Network Proxy Supported
Installing the module for all users on a system requires elevated privileges. Start the PowerShellsession using Run as administrator in Windows or use the sudo command on macOS or Linux:
The Az module is a rollup module for the Azure PowerShell cmdlets. Installing it downloads all ofthe generally available Az PowerShell modules, and makes their cmdlets available for use.
Install offline
In some environments, it's not possible to connect to the PowerShell Gallery. In those situations,you can still install offline using one of these methods:
Download the modules to another location in your network and use that as an installation source.This method allows you to cache PowerShell modules on a single server or file share to be deployedwith PowerShellGet to any disconnected systems. Learn how to set up a local repository and installon disconnected systems withWorking with local PowerShellGet repositories.
Download the Azure PowerShell MSI to a machine connected to the network,and then copy the installer to systems without access to PowerShell Gallery. Keep in mind that theMSI installer only works for PowerShell 5.1 on Windows.
Save the module with Save-Module to a file share,or save it to another source and manually copy it to other machines:
Troubleshooting
Here are some common problems seen when installing the Azure PowerShell module. If you experience aproblem not listed here, file an issue on GitHub.
Proxy blocks connection
If you get errors from Install-Module that indicate the PowerShell Gallery is unreachable, you maybe behind a proxy. Different operating systems and network environment have different requirementsfor configuring a system-wide proxy. Contact your system administrator for your proxy settings andhow to configure them for your environment.
PowerShell itself may not be configured to use this proxy automatically. With PowerShell 5.1 andlater, configure the PowerShell session to use a proxy using the following commands:
If your operating system credentials are configured correctly, this configuration routes PowerShellrequests through the proxy. To have this setting persist between sessions, add the commands to yourPowerShell profile.
To install the package, your proxy needs to allow HTTPS connections to the following address:
https://www.powershellgallery.com
Sign in
To start working with Azure PowerShell, sign in with your Azure credentials.
Note
In some environments, it's not possible to connect to the PowerShell Gallery. In those situations,you can still install offline using one of these methods:
Download the modules to another location in your network and use that as an installation source.This method allows you to cache PowerShell modules on a single server or file share to be deployedwith PowerShellGet to any disconnected systems. Learn how to set up a local repository and installon disconnected systems withWorking with local PowerShellGet repositories.
Download the Azure PowerShell MSI to a machine connected to the network,and then copy the installer to systems without access to PowerShell Gallery. Keep in mind that theMSI installer only works for PowerShell 5.1 on Windows.
Save the module with Save-Module to a file share,or save it to another source and manually copy it to other machines:
Troubleshooting
Here are some common problems seen when installing the Azure PowerShell module. If you experience aproblem not listed here, file an issue on GitHub.
Proxy blocks connection
If you get errors from Install-Module that indicate the PowerShell Gallery is unreachable, you maybe behind a proxy. Different operating systems and network environment have different requirementsfor configuring a system-wide proxy. Contact your system administrator for your proxy settings andhow to configure them for your environment.
PowerShell itself may not be configured to use this proxy automatically. With PowerShell 5.1 andlater, configure the PowerShell session to use a proxy using the following commands:
If your operating system credentials are configured correctly, this configuration routes PowerShellrequests through the proxy. To have this setting persist between sessions, add the commands to yourPowerShell profile.
To install the package, your proxy needs to allow HTTPS connections to the following address:
https://www.powershellgallery.com
Sign in
To start working with Azure PowerShell, sign in with your Azure credentials.
Note
If you've disabled module autoloading, manually import the module with Import-Module -Name Az.Because of the way the module is structured, this can take a few seconds.
You'll need to repeat these steps for every new PowerShell session you start. To learn how topersist your Azure sign in across PowerShell sessions, seePersist user credentials across PowerShell sessions.
Update the Azure PowerShell module
To update any PowerShell module, you should use the same method used to install the module. Forexample, if you originally used Install-Module, then you should useUpdate-Module to get the latest version. If youoriginally used the MSI package then you should download and install the new MSI package.
The PowerShellGet cmdlets cannot update modules that were installed from an MSI package. MSIpackages do not update modules that were installed using PowerShellGet. If you have any issuesupdating using PowershellGet, then you should reinstall, rather than update. Reinstalling isdone the same way as installing, but you need to add the -Force parameter:
Mac Proxy 3 0 10 – System Wide Network Proxy Supporting
Unlike MSI-based installations, installing or updating using PowerShellGet does not remove olderversions that may exist on your system. To remove old versions of Azure PowerShell from your system,see Uninstall the Azure PowerShell module. For more information aboutMSI-based installations, see Install Azure PowerShell with an MSI.
Use multiple versions of Azure PowerShell
It's possible to install more than one version of Azure PowerShell. To check if you have multipleversions of Azure PowerShell installed, use the following command:
To remove a version of Azure PowerShell, see Uninstall the Azure PowerShell module.
If you have more than one version of the module installed, module autoload and Import-Module loadthe latest version by default.
You can install or load a specific version of the Az module using the -RequiredVersionparameter:
Use multiple repositories with PowerShellGet
The Repository parameter is required if you have added additional repositories to PowerShellGeton your system and the Az module can be found in more than one of them.
Provide feedback
If you find a bug in Azure PowerShell,file an issue on GitHub. To provide feedbackfrom the command line, use the Send-Feedback cmdlet.
Next Steps
To learn more about the Azure PowerShell modules and their features, seeGet Started with Azure PowerShell. If you're familiar with AzurePowerShell and need to migrate from AzureRM, seeMigrate from AzureRM to Az.
