Microsoft Azure
You have a v2 Azure Virtual Machine that has been generalized and are ready to capture it using Azure PowerShell v1.0.x? All right, buckle your seat belt and follow this guide, at the end you should have your captured VHD in your storage account. This post assume you
Microsoft Azure
You have a v2 Azure Virtual Machine that has been generalized and are ready to capture it using Azure PowerShell v0.9.x? All right, buckle your seat belt and follow this guide, at the end you should have your captured VHD in your storage account. This post assume you
PowerShell
The IaaS v2 resource providers (Microsoft.Compute, Microsoft.Network & Microsoft.Storage) have been around for several months now and you may have wondered how to use your own custom images for creating virtual machines instead of one offered in the gallery. Let me show you how you can achieve
PowerShell
If you are experiencing this error: "Extension with publisher 'Microsoft.Powershell', type 'DSC', and type handler version 'x.x' could not be found in the extension repository" it is because Microsoft just pulled the cord on PowerShell DSC extension v1.x up
PowerShell
Azure PowerShell 1.0.0-preview is now available. It is in this version that the trigger is being pulled on Switch-AzureMode. Pow! Terminated! Gone!! Starting in version 1.0.0 both ASM and ARM PowerShell modules are able to coexists, but it also introduce breaking changes if you were already
PowerShell
You love PowerShell, have a custom VM image (specialized or generalized) and you want to create a new virtual machine from it under Azure Resource Manager API? You're at the right place... Prerequisites * Microsoft Azure PowerShell v0.9.4 or later, I used 0.9.7 * A custom
PowerShell
The introduction of agents and extensions bring a lot of possibilities to virtual machines in Azure. The CustomScript extension let you run one or a set of scripts on a virtual machine. The usage is simple, you upload one or many scripts & their required files if any to Azure
PowerShell
If you're like me and you open many PowerShell windows to work on Azure, this tip is for you. Am I on the right Azure subscription? At work and at home, I have to deal with a lot of Azure subscriptions. I also use a lot of PowerShell
PowerShell
The signal of the transition between ASM (Azure Service Management) to ARM (Azure Resource Management) APIs have been given not long ago with the recent deprecation of the Switch-AzureMode cmdlet in v0.9.2 of the Azure PowerShell cmdlets. Switch-AzureMode is now deprecated in release v.0.9.2 This
PowerShell
Version 0.8.0 introduced an aberration in the world of PowerShell modules in my opinion when they added the Switch-AzureMode cmdlet. The purpose of this cmdlet is to enable a switch between the Azure module and the AzureResourceManager module. In release 0.9.2 when you call Switch-AzureMode you
PowerShell
Since version 0.8.0, the Azure PowerShell can target multiple APIs, included in 2 PowerShell modules. Even if the name of some cmdlets are the same, they greatly differ in their inputs and responses. First we have the older cmdlets, the PowerShell Azure Service Management Cmdlets and then we
PowerShell
updated: May 10th 2015 - Added SAS workaround I played quite a bit with Azure Premium storage accounts recently and I have to say that I welcome with arms wide open this new performance level. Especially for dev/test environments in Azure. Even if I deeply think that this is