In the meantime, by tweaking a Microsoft provided script we can easily rename a VM by deleting the VM object (keeping all disks, NICs, IPs, etc.) and then recreating the VM using those existing objects.  The whole process should take ~10min (although it will vary based on the number of disks and NICs attached).

The below PowerShell script will work as-is for Windows VMs using managed disks and can easily be tweaked to run with Linux VMs or those using storage accounts.

# Nicole Welch, 10 January 2019
# Rename existing Windows VM in Azure Portal (resource name)
# Based on https://docs.microsoft.com/en-us/azure/virtual-machines/windows/change-availability-set

Add-AzureRmAccount

# Set variables
     $resourceGroup = "Demo"
     $oldvmName = "myVM"
     $newvmName = "newVM"

# Get the details of the VM to be renamed
     $originalVM = Get-AzureRmVM `
        -ResourceGroupName $resourceGroup `
        -Name $oldvmName

# Remove the original VM
     Remove-AzureRmVM -ResourceGroupName $resourceGroup -Name $oldvmName   

# Create the basic configuration for the replacement VM
     $newVM = New-AzureRmVMConfig -VMName $newvmName -VMSize $originalVM.HardwareProfile.VmSize

    Set-AzureRmVMOSDisk -VM $newVM -CreateOption Attach -ManagedDiskId $originalVM.StorageProfile.OsDisk.ManagedDisk.Id -Name $originalVM.StorageProfile.OsDisk.Name -Windows

# Add Data Disks
     foreach ($disk in $originalVM.StorageProfile.DataDisks) {
     Add-AzureRmVMDataDisk -VM $newVM `
        -Name $disk.Name `
        -ManagedDiskId $disk.ManagedDisk.Id `
        -Caching $disk.Caching `
        -Lun $disk.Lun `
        -DiskSizeInGB $disk.DiskSizeGB `
        -CreateOption Attach
     }

# Add NIC(s)
     foreach ($nic in $originalVM.NetworkProfile.NetworkInterfaces) {
         Add-AzureRmVMNetworkInterface `
            -VM $newVM `
            -Id $nic.Id
     }

# Recreate the VM
     New-AzureRmVM `
        -ResourceGroupName $resourceGroup `
        -Location $originalVM.Location `
        -VM $newVM `
        -DisableBginfoExtension

• Azure Overview Training - https://azure.microsoft.com/en-us/training/learning-paths/azure-administrator/
• Azure Hands-On-Labs - https://azure.microsoft.com/en-us/training/hands-on-labs/
• Recorded Presentations from Ignite - https://myignite.microsoft.com/videos
• Recorded Presentations from Build - https://www.microsoft.com/en-us/build
• Channel 9 - https://channel9.msdn.com/Tags/azure (just try to stick with recent content as Azure is very dynamic)
• Microsoft Virtual Academy - https://channel9.msdn.com/Tags/azure

Add the value per the screenshot below and you should be fine!

Growth Mindset

In a fixed mindset students believe their basic abilities, their intelligence, their talents, are just fixed traits. They have a certain amount and that's that, and then their goal becomes to look smart all the time and never look dumb. In a growth mindset students understand that their talents and abilities can be developed through effort, good teaching and persistence. They don't necessarily think everyone's the same or anyone can be Einstein, but they believe everyone can get smarter if they work at it.^[

My Personal Journey

How does this impact you?

Summary

• Learn a new skill (for work or fun)
• Read
• Travel or watch programming that exposes you to different cultures and ways of life
• Listen and learn from those around you
• Surround yourself with smart people
• Go outside your comfort zone

Monitoring Product Comparison

My Summary

The Future

Closing

What exactly is the cloud?

Evolution of Digital Computing

Before Digital Computing

The Rise of the Modern Computer

The Democratization of Computing

Connecting Devices

The Internet of Things (IoT)

Leveraging our Data

Artificial Intelligence (AI)

And then?

Closing

1. Goto https://azure.microsoft.com/en-us/regions/services/
2. Select only the Azure Government region checkbox
3. You can now see this VM is only available in the Virginia data center.

The features/service is not available where I need it!

• Features often depend on physical hardware and so they often deploy to each region at slightly different times depending on the hardware deployment.  I.e. with a new VM size/series
• Some features are delayed as we work on the required compliances or attestations.
• Engineering wants to release features as quickly as possible.  If the product can be deployed/engineered the same in MAC and MAG they are often released at the same time.  However if significant changes are required for MAG they don’t want to delay the MAC release.  In those cases the feature most likely will be deployed to MAC and then MAG after the required modifications are made.  Often features are delayed 6-9 months in MAG.
• There is no/limited demand expected in MAG.

But I need it!

1. Include hard facts.  We want numbers, timelines, and project implications.  I.e. if the M series were available in Texas we would deploy an additional 10 VMs by the end of 1Q 2018.  This gives Microsoft an idea of the urgency/timeline, infrastructure required to support the request, and the impact to our accounts.
2. Include clear details.  I.e. if this is available in MAC, include the blog announcement or documentation too so we know exactly what you are requesting.  Often features have similar names, vary between cloud providers, etc. resulting in confusion.
3. Include the consequences.  If this request isn’t met, what is the result?  I.e. if Service Map is not made available in MAG OMS will we not migrate our monitoring of 8000 servers into OMS.
4. Share with your friends!  Votes count, so if you add a request have all your peers vote for it too.
5. And be realistic.  Asking for a feature not even planned for MAC is unlikely to be approved for MAG.  Asking for a feature fulfilling a clear business need is much more likely to get backing.

Azure CLI

AzCopy

1. sudo yum install rh-dotnetcore11
2. scl enable rh-dotnetcore11 bash
3. source scl_source enable rh-dotnetcore11

1. wget -O azcopy.tar.gz https://aka.ms/downloadazcopyprlinux
2. tar -xf azcopy.tar.gz
3. sudo ./install.sh

Wget