Sometimes, it’s the little things that matter the most.
Creating a cloud service is more than just creating a cloud service. Have you ever wondered why you can’t scale beyond A-series? That is because the first VM you deployed to the cloud service is in the A-series. If you do this, Azure will create your cloud service on an old version of the hypervisor fabric. The old version doesn’t support D-series or higher.
But if you instead start by deploying your first VM as a D-series, you will be able to scale a bit more. You can of course scale down to A-series immediately, but at least now you have the option to scale if you want. You can now deploy VM’s as A-series in the same cloud service and later scale to D-series if needed.
In my case G-series is not available in the north Europe datacenter, but it would also be listed here if I deployed it to a datacenter that supported G-series. If you are planning to use a big G-series machine you should deploy this VM first. This is because your large G-series VM will be deployed on a new hypervisor, and your upcoming VM’s will be placed (physically) as close as possible to this VM.
But there is also one more thing that is kind of important. If you deploy to an old hypervisor-cluster, when Microsoft is upgrading the fabric. Your VM will be rebooted by Microsoft. If you instead use the new hypervisor-cluster, your VM will be paused and then resumed during fabric maintenance.