Installing Azure PowerShell Module in Your Local Windows PowerShell



The Azure PowerShell Module can be used to automate the creation, management and deployment
of resources in Microsoft Azure Portal, so it's very useful and we'd better have it installed in our local Windows PowerShell. We can simply follow the below steps to achieve this.

I. Firstly launch Windows Powershell with an administrator’s credential and execute the $PSVersionTable.PSVersion command to check the current version of PowerShell that’s been installed. As per the below screenshot, the version installed in my machine is 5.1. This is the minimum version that’s required to install the Azure PowerShell module.




II. Install .NET Framework 4.8 in your Windows system. In my case the install program indicates me that it’s already been installed. 



III. In PowerShell run the Update-Module PowerShellGet -Force command to install the latest version of PowerShellGet. PowerShellGet is a module with commands for discovering, installing, updating and publishing PowerShell artefacts. We’ll leverage its functions to install the Azure PowerShell module.

If you haven’t had the PowerShellGet module installed, you may encounter the below error message as I did.



If that’s the case, we can use the Install-Module -Name PowerShellGet -Force command to install it first, and then run the above ‘Update-Module’ command again. While updating, the below message will appear in your PowerShell window indicating the update process is on going.




IV. Once finished, execute the Install-Module -Name Az -AllowClobber command to install the Azure PowerShell module. Type ‘Y’ or ‘A’ when the below message displays and click the ‘Enter’ button.



Again, the below information displays indicating the installation is in process. Wait for it to be finished.




V. Run the Get-InstalledModule command to check all the modules installed. As per the below screenshot, you’ll see from the ‘Description’ field that a series of Auzre PowerShell modules have been installed. 



Comments

Post a Comment

Popular posts from this blog

SQL Server - Using SQL Agent JOBs to Schedule and Execute Multiple Stored Procedures in Parallel

This article introduces a way to schedule and kick off multiple stored procedures in parallel. Suppose we need to build an ETL system to migrate data from the source system to the target in T-SQL script; we've created multiple stored procedures (SP) each of which contains the payload of extracting data from one module of the source system and loading it to the target system; any of those stored procedures can be executed independently without relying on the execution statuses of any other stored procedures; and to speed up the whole process, we need to run multiple stored procedures simultaneously. Ideally, the above task can be handled easily in SSIS. Of course we could've created a Sequence Container and dropped a batch of SP execution tasks to it in SSIS, and then another Sequence Container containing the next batch of SP execution tasks, etc., but what if using SSIS has become a luxury for us (for example, your boss is not a fan of SSIS and prohibits you from using it as ...
Read more

sp_executesql – Let's learn How to Use It

Image
In the post SQL Server - Using SQL Agent JOBs to Scheduleand Execute Multiple Stored Procedures in Parallel , I’ve demonstrated the usage of sp_executesql and how powerful and helpful it is. This time I’ll put more explanations about it. Talk is cheap, and let’s see the code. DECLARE @ModDate datetime = '2017-12-04 00:00:00.000' SELECT        [AddressID]     , [AddressLine1]     , [AddressLine2]     , [City]     , [StateProvinceID]     , [PostalCode]     , [SpatialLocation]     , [rowguid]     , [ModifiedDate] FROM [AdventureWorks2017] . [Person] . [Address] WHERE [ModifiedDate] <= @ModDate The above code is straightforward enough. Now let’s consider the below scenarios – suppose our database name is composed by the keyword ‘AdventureWorks’ plus the year number suffix (in our example it’s 2017); ...
Read more