How to fix "Wizard ended permaturely" when installing Azure PowerShell via MSI
Well this sounds like a straight forward task. Download the MSI package, run the installed and done. But there is one tiny obstacle that you may encounter
Microsoft Azure, is a cloud computing service for building, testing, deploying, and managing applications and services through Microsoft-managed data centers.
Well this sounds like a straight forward task. Download the MSI package, run the installed and done. But there is one tiny obstacle that you may encounter
This is just a quick run-through on how to use Azure PowerShell for Azure VNet management
I found it rather difficult to create an alert rule using PowerShell as opposed to using Azure CLI. That's why I thought it is worth a post. I assume there exists a resource group called rg-training and a VM named VM1. In general, an alert rule consists of the following components
While playing around with the Azure Licenses blade inside Azure Active Directory I was wondering why on earth I am not able to assing licenses to groups. Every time I clicked on Licensed groups and then on + Assign I only saw a list of users, without being able to
While using the Azure CLI I found it very frustrating to repeat information like the resource group name and other things over and over again. But luckily Microsoft took care of this
While playing around with the Azure CLI and Powershell Core 7.0 I encountered a strange situation, when trying to
Well admittedly the title of this post is kind of misleading... anticipating the result here: You can't rename a resource group. Not yet!