52 articles
In the upcoming major release of Azure PowerShell (Az 12.0.0), the DisplayBreakingChangeWarning configuration option will be activated by default. A warning message will be shown in the output of a cmdlet
This post explains how to set the default location for Azure PowerShell cmdlets, eliminating the need to specify it with each command.
If your virtual machine (VM) isn’t operational, it will be in one of two states: Stopped or Stopped (deallocated). Essentially, if a resource is ‘allocated’, you are still incurring charges for it.
Even when stopped, Azure VMs that are not deallocated continue to incur costs. This article explores methods to find the stopped Azure VMs and deallocating them.
Even when stopped, Azure VMs that are not deallocated continue to incur costs. This article explores methods to locate such servers utilizing PowerShell.
When an Azure VM is shutdown using the operating system it enters a Stopped state. In this state, the server is not running but the compute resource is still being held by Azure so you continue to get charged for that compute.
Sometimes, you may need to obtain the public IP address of an Azure VM, such as when you wish to connect to the VM via remote desktop automatically after its creation with PowerShell.
When managing Azure, I often create Windows VMs. To automate this, I utilize PowerShell. However, I would like to establish an RDP connection to the newly created VM without manually inputting the public IP address, username, and password.
In some cases, your Azure tenant has multiple Azure subscriptions. Every time, when you sign-in into Microsoft Azure using PowerShell, you would get this warning:
This article shows you how to securely and seamlessly create an RDP connection to your Windows VMs located in an Azure virtual network directly through the Azure portal.