If there is an allocation error when restarting a deallocated VM, the following error message is logged:
“Failed to start virtual machine 'xyc'. Error: Allocation failed. Please try reducing the VM size or number of VMs, retry later, or try deploying to a different Availability Set or different Azure location.”

If there is an allocation issue when creating a new machine the following message is displayed:
“New-AzureRmVM : Unable to create the VM because the requested size Standard_F4 is not available in the cluster where the availability set is currently allocated. The available sizes are: Standard_DS1_v2,Standard_DS2_v2 …”

Would be nice to have the later message for all allocation errors.

I just spun up a brand new Standard B1ms (1 vcpu, 2 GB memory), all I did was login to the VM and am getting out of memory errors (which would tell me windows server 2016 doesn't really support this level of VM size). Also it fails to retrieve updates - this is just a plain vanilla OOB/first run experience. Additionally you can't login and click the start button - you have to click it about 10 times to get the menu to pop up - this is probably more of a windows issue but I'd expect it to at least the basics to function.

When deploying the image of SQL Server, the number of disks is set to the parameter of sqlStorageDisksCount, but when IaaS agent is running New-VirtualDisk, it is not used as the number of columns, so 16 disks Even if you set up, the number of columns is 8, and Virtual Disk is created.

When IaaS Agent runs New-VirtualDisk and creates a disk, it uses [NumberOfColumns <sqlStorageDisksCount parameter>] instead of [AutoNumberOfColumns] and uses the number of connected disks as the number of columns and 8 If you are connecting more disks than you want, let me set the appropriate number of columns.

I created new Azure account and went to the the new portal and created a storage account. I then went to the classic portal and did not see it ??? So I deleted the storage account in the new portal and created one in the classic -- BUT I could not get the Region to be US East in the classic portal only in the new Portal ?????? Go figure ???? How ridiculous is this ! I can not stand the new portal -- its as complex and stupid as AWS . So if you want to loose more customers keep the new portal !

To meet legal requirements, like many, we employ "forced tunneling", to push traffic through our proxy server. Many of your services, including agents are "Proxy Unaware" (like your developers!)

One possible way to overcome this, is to add a UDR to the special VM Agent IP of 168.63.129.16, however, when I try to create a route of 168.63.129.16/32, I get the below error, essentially saying it is in a restricted address space.

Please remove this restriction, post hast.

This is an incredibly quick and easy way to overcome your lack of proxy support with the VM agent.

Full error message:
Failed to add route 'DirectRouteToVMAgent' to route table 'UDR-TABLE-001'. Error: AddressPrefix 168.63.129.16/32 for route DirectRouteToVMAgent is not allowed because its in restricted address space.

The script of EnableRemotePS Run Command:
Enable-PSRemoting -Force
New-NetFirewallRule -Name "Allow WinRM HTTPS" -DisplayName "WinRM HTTPS" -Enabled True -Profile Any -Action Allow -Direction Inbound -LocalPort 5986 -Protocol TCP
$thumbprint = (New-SelfSignedCertificate -DnsName $env:COMPUTERNAME -CertStoreLocation Cert:\LocalMachine\My).Thumbprint
$command = "winrm create winrm/config/Listener?Address=*+Transport=HTTPS @{Hostname=""$env:computername""; CertificateThumbprint=""$thumbprint""}"
cmd.exe /C $command

It on Windows 10 VMs with the following error from RunCommandExtensionn.Log file :

[3504+00000001] [12/05/2018 08:52:29.69] [ERROR] Command execution finished. Command exited with code: 1

When executing the first command (Enable-PSRemoting -Force) manually on the VM, we get the following error:

Set-WSManQuickConfig : <f:WSManFault xmlns:f="http://schemas.microsoft.com/wbem/wsman/1/wsmanfault&quot; Code="2150859113" Machine="localhost"><f:Message><f:ProviderFault provider="Config provider"
path="%systemroot%\system32\WsmSvc.dll"><f:WSManFault xmlns:f="http://schemas.microsoft.com/wbem/wsman/1/wsmanfault&quot; Code="2150859113" Machine="AOVPN-10Dom"><f:Message>WinRM firewall exception will not work since one of the
network connection types on this machine is set to Public. Change the network connection type to either Domain or Private and try again. </f:Message></f:WSManFault></f:ProviderFault></f:Message></f:WSManFault>
At line:116 char:17
+ Set-WSManQuickConfig -force
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [Set-WSManQuickConfig], InvalidOperationException
+ FullyQualifiedErrorId : WsManError,Microsoft.WSMan.Management.SetWSManQuickConfigCommand

For the EnableRemotePS Run Command to work on Windows Client we need to add the switch SkipNetworkProfileCheck to the PSRemoting so it should look like
Enable-PSRemoting -Force -SkipNetworkProfileCheck