Madan's Blog

Check Azure Resource Manager (ARM) VM Core & Storage Usage using PowerShell

Madan [MSFT] — Tue, 25 Oct 2016 20:37:07 GMT

For classic Azure VM's you can simply check the VM Core Usage & Limits right within the classic portal. However, for ARM that is not possible via the classic or the new portal. Only way to check the usage and the thresholds currently set for your subscription, you will need to use Azure PowerShell. You can download Azure PowerShell module from here.

Add-AzureRmAccount For Azure Gov't: Add-AzureRmAccount -EnvironmentName AzureUSGovernment

Set the default subscription incase you have more than one

Set-AzureRmContext -SubscriptionId “"

Then run the below command to check the VM usage details such as total VM's, Cores Used, Availability Sets, etc. The output will also show the limits for each of them.

Get-AzureRmVMUsage -Location "" For example: Get-AzureRmVMUsage -Location "USGov Iowa"

You can also view the storage usage and limits using the below command

Get-AzureRmStorageUsage

DISCLAIMER: The above blog posting is provided “AS IS” with no warranties and confers no rights.

Resize Azure Resource Manager (ARM) VM OS & Data disk using Azure Portal

Madan [MSFT] — Wed, 28 Sep 2016 00:06:00 GMT

If you have an Azure VM that was created using the Azure Resource Manager (ARM) stack you can now easily resize the OS or the data disk within the Azure Portal. Of course, you can also use PowerShell but way too easy using the GUI.

1. Navigate to the Virtual Machine (VM) that you would like to resize the disk(s). 2. Shutdown the VM from the Azure portal. Make sure it's completely shutdown (de-allocated)

3. Select 'Disks' in the Settings blade.

4. Select the OS/Data disk that you would like to resize.

5. On the new blade, enter the new disk size (1023GB or 1TB max per disk).

Note: The below screenshot shows OS disk resize which has Host Caching set to Read/Write. For data disk it's ideally set to none.

6. Hit 'Save' on top.

7. Start the VM back again.

That's it! You can login to the VM and check that you have the new selected size for the disk(s). DISCLAIMER: The above blog posting is provided “AS IS” with no warranties and confers no rights.

Installing Microsoft Antimalware extension in Azure Gov't VM using PowerShell

Madan [MSFT] — Tue, 27 Sep 2016 22:44:34 GMT

Microsoft Antimalware for Azure Virtual Machines is a real time protection that will monitor the VM's to detect and block malwares. You can read more about Microsoft Antimalware here. Please follow the below steps to enable the Antimalware extension for Azure Gov't VM. You will need to use Azure PowerShell to enable the extension. You can download Azure PowerShell module from here.

Add-AzureAccount -Environment AzureUSGovernment

Set the correct subscription as current

Select-AzureSubscription -SubscriptionId ""

Save the below as a JSON template. For example, AntimalwareConfig.JSON

{ "AntimalwareEnabled": true, "RealtimeProtectionEnabled": true, "ScheduledScanSettings": { "isEnabled": true, "day": 1, "time": 120, "scanType": "Full" } }

Then run the below script

$serviceName = "" $vmName = "" Get-AzureVM –ServiceName $serviceName –Name $vmName | Set-AzureVMMicrosoftAntimalwareExtension ` -AntimalwareConfigFile ""| Update-AzureVM 5. You can view the extension info by running the below command Get-AzureVM –ServiceName $serviceName –Name $vmName | Get-AzureVMMicrosoftAntimalwareExtension You can read more about Set-AzureVMMicrosoftAntimalwareExtension cmdlet here. You can modify the config file as mentioned in the documentation.

DISCLAIMER: The above blog posting is provided “AS IS” with no warranties and confers no rights.

Resizing Azure VM OS or Data Disk

Madan [MSFT] — Mon, 02 Nov 2015 22:12:00 GMT

Are you running out of space on the OS or data disk of your Azure VM? Here is a simple way to resize the OS or the data disk. Resizing of the disk is done using Azure PowerShell. If you don’t have Azure PowerShell on your local machine, then you can follow the documentation to install Azure PowerShell in your local machine and connect to your Azure Subscription. Note: I have tested this for VM's running Windows OS only but not Linux. Also keep in mind that once you run the command to resize the disk it is irreversible. You will NOT be able to shrink the disk. In addition, this applies only to V1 VM's created using Azure Service Manager (ASM). If you like to resize disks for Azure Resource Manager (ARM), see my blog @ Resize Azure Resource Manager (ARM) VM OS & Data disk using Azure Portal Few things to ensure before performing shutdown/de-allocation of the VM:

Make sure you don’t have any data in the Temporary D-Drive in the VM as the data will be lost since it’s a non-persistent drive.
You will lose the VIP (Public IP) if this is the only VM in the cloud service. If you need to preserve the VIP, then you can either reserve the VIP or add a test VM in the same cloud service before shutting down the VM that you would like to resize the disks.
I highly recommend that you take back up copies of the disk prior to executing any command to resize the disk incase something goes wrong.

Resizing OS disk:

Shutdown (de-allocate) the VM from the Azure portal. Check VM's dashboard to make sure it says Deallocated (See screenshots below)

On the classic portal: On the new portal:

Once the VM is completely de-allocated, then launch Azure PowerShell and connect to your Azure subscription.

Then, you will need to collect the OS disk info that you want to resize. Use the command below to output the OS disk details.

Get-AzureVM -ServiceName "" -Name "" | Get-AzureOSDisk

For example:

Get-AzureVM -ServiceName MnDemoVM2 -Name "MnDemoVM2" | Get-AzureOSDisk

If you want to see the current size of your disk, you can either connect to your VM and check or you can check from the portal. To check in the portal, go to the dashboard of the VM and take a note of the VHD path from the disk section in the dashboard (See screenshot below). Then, go to the storage account of that VM and navigate to container where that VHD is located. You will see the size of the disk in the last column of that table.

VHDs Path:

Before Resize:

Next, run the below command with the OS disk name you have acquired from step-3 to resize the disk.

Update-AzureDisk -DiskName "" -Label Resized -ResizedSizeInGB 400

Note: Azure allows you to have a OS or Data disk up to 1TB (1023 GB) for each disk.

For example:

Update-AzureDisk -DiskName "MNDemoVM2-MNDemoVM2-0-201510092258210053" -Label Resized -ResizedSizeInGB 400

Now, go back to the same container where the VHD is and you can see the size of the VHD has changed to 400 GB.

Once you verify that the disk has been resized, start the VM from the portal and connect to the VM.

After you login to the VM, go to Disk Management. You will notice that the disk size has changed to 400 GB now. Right-click on the volume and select 'Extend Volume'. Follow the on-screen steps to extend the volume.

After Extending the volume:

********************************************************************************************************************************************************************* Resizing Data disk:

The process to resize the data disk is same except the command you run in Azure PowerShell is slightly different.

Run the below command to collect the data disk info to resize.

Get-AzureVM -ServiceName "" -Name "" | Get-AzureDataDisk

For example:

Get-AzureVM -ServiceName MnDemoVM2 -Name "MnDemoVM2" | Get-AzureDataDisk

Check the size of the data disk before resizing.

Before Resize:

Next, run the below command with the data disk name you have acquired from step-3 to resize the disk.

Update-AzureDisk -DiskName "" -Label ResizeDataDisk -ResizedSizeInGB 500

Note: Azure allows you to have a OS or Data disk up to 1TB (1023 GB) for each disk.

For example:

Update-AzureDisk -DiskName MNDemoVM2-MNDemoVM2-0-201511032306210081 -Label ResizeDataDisk -ResizedSizeInGB 500

Now, go back to the same container where the VHD is and you can see the size of the VHD has changed to 500 GB.

Once you verify that the disk has been resized, start the VM from the portal and connect to the VM.

After you login to the VM, go to Disk Management. You will notice that the disk size has changed to 500 GB now. Right-click on the volume and select 'Extend Volume'. Follow the on-screen steps to extend the volume.

I hope this post helped you resolve your OS or Data disk resizing issue. Please feel free to comment if you have any additional questions. DISCLAIMER: The above blog posting is provided "AS IS" with no warranties and confers no rights.

Reserved Multiple VIPs per Cloud Service

Madan [MSFT] — Sun, 27 Sep 2015 13:02:00 GMT

Scenario: Let's assume you want three Reserved Public Virtual IPs (VIPs) for a single cloud service. By default you can have up to 5 VIPs per cloud service. However, if you need more you can have that increased through Microsoft Support. Good example you may need multiple VIPs for a single cloud service is to host multiple different SSL websites from a single Azure IaaS VM. I'll show you how you can achieve that using Azure PowerShell. If you don’t have Azure PowerShell installed then you can follow the document Azure PowerShell to install it in your local machine and connect to the Azure Subscription.

Note: This post applies only for Classic Model deployments created using Azure Service Manager (ASM).

Steps to follow:

Create your Virtual Machine using the standard process from the Azure Portal/Azure PowerShell. For this demo, I created a VM and cloud service with the name MNWin10 in South Central US.

Then using Azure PowerShell, run the below commands to reserve 3 public IP’s. You can change the names & locations to whatever suits your environment.

New-AzureReservedIP –ReservedIPName “ReservedVIP1” –Location “South Central US”

New-AzureReservedIP –ReservedIPName “ReservedVIP2” –Location “South Central US”

New-AzureReservedIP –ReservedIPName “ReservedVIP3” –Location “South Central US”

Now run the below command and make sure that you have three different reserved IP’s and that they are not in use.

Get-AzureReservedIP

Run the below commands and you will see only one VIP associated to the cloud service MNWin10. Which is the primary VIP and is not reserved yet. We will replace this VIP with the reserved IP in further steps.

$deployment = Get-AzureDeployment -ServiceName MNWin10

$deployment.VirtualIPs

Next, run the following set of commands to add two additional VIP to the cloud service. We are only adding two additional VIP’s because by default when you create the VM you will be given a primary VIP.

Add-AzureVirtualIP -VirtualIPName VIP2 -ServiceName MNWin10

Add-AzureVirtualIP -VirtualIPName VIP3 -ServiceName MNWin10

Now when you run the below commands you will see 3 VIP names but only one VIP address. Vip1 is the default VIP, you know that because the value for IsDnsProgrammedName is set to true. Vip2 and Vip3 are not used as they don’t have any IP addresses. They will only be used if you associate an endpoint to the VIP.

$deployment = Get-AzureDeployment -ServiceName MNWin10

$deployment.VirtualIPs

Then run the following commands to associate the VIP2 & VIP3 to an http & https endpoints. Also we need to create endpoints for the default primary VIP.

Primary VIP:

Get-AzureVM -ServiceName MNWin10 -Name MNWin10 | Add-AzureEndPoint -Name "Http" -Protocol "tcp" -PublicPort 80 -LocalPort 8080 | Update-AzureVM

Get-AzureVM -ServiceName MNWin10 -Name MNWin10 | Add-AzureEndPoint -Name "Https" -Protocol "tcp" -PublicPort 443 -LocalPort 8081 | Update-AzureVM

VIP 2:

Get-AzureVM -ServiceName MNWin10 | Add-AzureEndpoint -Name http2 -Protocol tcp -PublicPort 80 -LocalPort 8082 -VirtualIPName VIP2 | Update-AzureVM

Get-AzureVM -ServiceName MNWin10 | Add-AzureEndpoint -Name https2 -Protocol tcp -PublicPort 443 -LocalPort 8083 -VirtualIPName VIP2 | Update-AzureVM

VIP 3:

Get-AzureVM -ServiceName MNWin10 | Add-AzureEndpoint -Name http3 -Protocol tcp -PublicPort 80 -LocalPort 8084 -VirtualIPName VIP3 | Update-AzureVM

Get-AzureVM -ServiceName MNWin10 | Add-AzureEndpoint -Name https3 -Protocol tcp -PublicPort 443 -LocalPort 8085 -VirtualIPName VIP3 | Update-AzureVM

Now run the same commands in step 4 and you should see three different VIP’s associated to the cloud service MNWin10. However, these VIP’s are not the same VIP’s you have reserved in step 2. We will replace these VIP with the reserved VIP's in the next step.

Run the below commands to associate the reserved IP to the multi VIP cloud service. Before you run the first command below you need to make note of the first default VIP Name. You will find that info in the output of step 4. It may be something like *ContractContract.

Note: You will have a brief disruption in your network (about a minute) when the first command below is run for the primary VIP.

Set-AzureReservedIPAssociation -ReservedIPName ReservedVIP1 -ServiceName MNWin10 -VirtualIPName MNWin10ContractContract

Set-AzureReservedIPAssociation -ReservedIPName ReservedVIP2 -ServiceName MNWin10 -VirtualIPName VIP2

Set-AzureReservedIPAssociation -ReservedIPName ReservedVIP3 -ServiceName MNWin10 -VirtualIPName VIP3

Now re-run the commands in step 5 and you should see 3 Reserved VIPs associated to your cloud service.

Also, if you run Get-AzureReservedIP command you will see that all the three IP Addresses are 'In Use' and assigned to the same cloud service.

And if you go to the portal and look at the endpoints for the VM, you should see something similar to this.

The VIPS won't be reachable from externally yet. You will need to install and configure IIS and bind the port numbers. So, connect to your VM and install IIS. Once you have IIS installed and then bind the port numbers accordingly to your configurations. In my case I added only the http ports for this demo in bindings in IIS.

Once you added those port number, you should be all set. You can use any of those VIPs in the cloud service and it will resolve and display the default IIS page.

15. Hope you find this documentation helpful if you are looking to setup same or similar in your Azure environment.

Resource: Multiple VIPs per cloud service