What vm size that still works with cloud service definition (on Azure SDK 2.2) and at the Azure deployment

Naveen Kumar 0 Reputation points

Getting the error message 'the operation '6bb1a65b4babaf748f2e41df730b5468' failed: 'the requested vm tier is currently not available in east us for this subscription. please try another tier or deploy to a different location.'.' while deploying an app to cloud service. And am not sure what VM size to use in my cloud service project (which is on Azure SDK v2.2) as whatever sizes Azure supports now are not working in csdef.


We're having an ASP.Net application with a cloud service project which was developed long back with the Azure SDK v2.2. We have the same production application in Azure but since the cloud service is getting removed soon we're trying to create a replica of it to lay out the plan for migration.

So we're trying to repackage the application with the same Azure SDK v2.2. We were successful until we hit an issue with Azure VM size that is associated with a Web role in the csdef file. The VM size previously used was "Small" but that is not working with current Azure as those sizes are not there anymore. But I am unable to change the vm size to any other since Azure SDK 2.2 strictly validates the vm sizes and gives an error if I change "The 'vmsize' attribute is invalid - The value 'B2ms' is invalid according to its datatype 'http://schemas.microsoft.com/ServiceHosting/2008/10/ServiceDefinition:RoleSize' - The Enumeration constraint failed."

So I need to know what vm size I can use so that it works in csdef (with Azure SDK 2.2) and at the deployment. Please advise.

Azure Cloud Services
Azure Cloud Services
An Azure platform as a service offer that is used to deploy web and cloud applications.
587 questions
A cloud computing platform and infrastructure for building, deploying and managing applications and services through a worldwide network of Microsoft-managed datacenters.
639 questions
{count} votes

1 answer

Sort by: Most helpful
  1. VasimTamboli 4,440 Reputation points

    As you have mentioned, the Azure SDK v2.2 is quite old and the VM sizes available in the current Azure environment have changed. Since Azure no longer supports the Small VM size, you will need to choose a different size that is still supported and compatible with Azure SDK v2.2.

    One option is to use the "Standard_B1s" VM size, which is a Basic tier VM with 1 vCPU and 1 GB RAM, and should be compatible with Azure SDK v2.2. This VM size is currently available in the East US region.

    To use this VM size in your csdef file, you would need to update the "vmsize" attribute to "Standard_B1s". Your updated csdef file might look something like this:

    <?xml version="1.0" encoding="utf-8"?>
    <ServiceDefinition name="MyCloudService" xmlns="http://schemas.microsoft.com/ServiceHosting/2008/10/ServiceDefinition">
      <WebRole name="WebRole1" vmsize="Standard_B1s">
          <Site name="Web">
              <Binding name="Endpoint1" endpointName="HttpIn" />
          <InputEndpoint name="HttpIn" protocol="http" port="80" />
          <Import moduleName="Diagnostics" />
          <Setting name="Setting1" />

    Note that you may also need to update the VM size in your Azure deployment settings, depending on how you are deploying the application.