Using Windows Azure to encounter a new service that cannot be deployed, the existing service is running correctly

Login Azure During portal usage, a new virtual machine cannot be created and the database can be created. After removing the old virtual machine, it is not possible to create a new minimum small specification virtual machine.

The error is as follows: The subscription policy limit for the resource type "managed service Count" is exceeded. The limit for the resource type "managed Service Count" is 2 per subscription , the current count is 2, and the requested increment is 1.

This is generally because resource usage reaches the quota limit. Azure sets a quota limit on the account, and when the limit is reached, users cannot continue to deploy the service.

650) this.width=650; "title=" usage. jpg "src=" http://s3.51cto.com/wyfs02/M00/28/1F/wKioL1N1_ Y3witlxaaejlkxxa1q081.jpg "alt=" Wkiol1n1_y3witlxaaejlkxxa1q081.jpg "/>

For example, you can see that each of your accounts/subscriptions supports up to four cores, green represents the number of cores used by the current service, and Gray represents the number of cores available. In addition you have deleted the old virtual machine, but the cloud service is not deleted, your account's cloud service Cloud services Maximum is 2

This article is from the "Go to the Sky" blog, please be sure to keep this source http://songlihuan.blog.51cto.com/8735257/1412711