Allow a Role instance count of 0
In many scenarios it is useful to have a role that is only run for certain periods of the day. At present this is very complex to achieve as it involved using the management API to deploy and undeploy a whole service (from Blob storage). it would be much more elegant if the role count could be set to Zero thus undeploying all instances of just that role. In this way other services in the project could use the management API to start and stop just that Role.
We are likely to support this in phases. Stay tuned for more details.
Can we please get an update. The second highest voted request and years 4 years without a response.
Gøran Thomassen commented
So, any ETA on this?
Any updates on this?
This is a very needed feature especially for dev environments.
oh never mind I see the 969 people before me have already moved to AWS. last one out turn off the lights.
hey you can do this AWS lets just move there.
I doubt Microsoft will implement it. Reason is money. With this feature customers could pay less by not paying for idle computing. Unacceptable by profit driven management.
2+ years and no response? Seriously Microsoft, WTH is this nonsense? Are you trying to force your customers to Service Fabric (which does not support 0 instances either, mind you)? Is it because some internal stats show you that a majority of PaaS customers are internal Microsoft and so you decide to ***** over the few PaaS customers out there?
Your CEO shouts about "cloud first" and how we wants an Azure run-rate of $18 billion USD by 2018 and with stuff like this, what do you expect the customers to do?
Worst of all, when a Group Program Manager talks about something being "Under Review" and then conveniently forgets to provide status update, even after 2+ years, what does it speak about a company like Microsoft?
There are several features that the community has been clamoring for the past several years:
1) This ask
2) Allow multiple Worker Roles to run on 1 or fewer VMs (let us control how many VMs Worker Roles create)
3) Have a Resource Provider for Cloud Services so that they can be deployed through ARM templates.
Fix this broken piece of **** Microsoft!
Andrew Goad commented
It has been a few years. Any news on this??
Guys, @Corey/ @Clavin
Any chance this is going to happen?
Hey, Microsoft, it's been a 5+ years since the first ask. How many CEOs and reorgs does it take to ******* do this? Unless, of course you don't want us to use Azure.
Garth Sweet commented
This is a must have feature. It's been requested for years now and sorely needed.
Eivind Tjore commented
Any news on this? Allowing instance count of 0 would greatly improve life for azure-developers :)
Sean Feldman commented
Please add support for this.
Please provide an update. This is an important feature and I now see that Azure competitors are providing functionality to facilitate - e.g. AWS Lambda
Leon Meijer commented
Please provide an update. For development purposes, 0 role instances (or via Azure Automation) would be appreciated
Alan M commented
Please provide an update on support for this.
What surprises me is that we can deprovision a VM, but not a Worker Role or a Web Role. Currently this is only possible if we remove the deployment, which is quite cumbersome.
"Post Fall 2012" is quite a broad timeframe. Can you please provide one that is more accurate?
Is there any update on this feature? Now that cloud services can have reserved IPs providing this feature for Cloud Services only with reserved IPs would be okay with me.
Jeroen Landheer commented
Today they have released pricing changes on Azure, but unlike virtual machines, it does not look like charges stop if cloud services or role instances are stopped. (The portal still tells you that you continue to incur charges until a deployment is deleted.) If this changes there might be a work around or even a solution to this.