From Brian Laws, @BrianHLaws via Twitter:
But I've got a new question. Got a roadblock that I'm not able to get around. I'm trying to deploy my first Standard_DS3 VM to US East 2. I have a script to do so. The script runs great if I'm using Standard_D3 but gives me the following if I use DS3: "New-AzureVM : Compute.OverconstrainedAllocationRequest : The VM size (or combination of VM sizes) required by this deployment cannot be provisioned due to deployment request constraints. If possible, try relaxing constraints such as virtual network bindings, deploying to a hosted service with no other deployment in it and to a different affinity group or with no affinity group, or try deploying to a different region." I've confirmed, however, that my affinity group and VNET are in US East 2, and the cloud service and storage accounts are all in the affinity group. This is the first vm in the cloud service. As far as I can tell, everything is lined up for US East 2. Is there some gotcha for using Standard_DS3 vs. Standard_D3? I am still able to use cloud services and affinity groups with them, right? A limitation in my MSDN? I'm really puzzled by what's happening here.
I wonder if there's simply something going on in the service, since the preview portal is failing to allow me to create VMs through the GUI. When I click "Create" for either Windows 2008 R2 SP1 or 2012 R2 Datacenter, I get an "Oops! Could not create Windows Server 2012 R2 Datacenter. Something went wrong while creating Windows Server 2012R2 Datacenter."
One other thought: perhaps you can't use the Win 2008 R2 SP1 image with the DS series? I'll try the same script except with a 2012.
Thanks!
@AzureSupport