Forum Discussion
Azure function Start-Stop-V2 ignores ResourceGroups
Hello,
Microsoft pushes customers to use Start-Stop-V2 for scheduled starting and stopping machines. This new functionality is based on Azure Functions, not based on automation accounts and runbooks.
Unfortunately, the Azure Function provided by Microsoft (deployed from marketplace) does not work properly. This function ignores the property ResourceGroups and starts all VMs within a subscription, instead of starting only the machines within the given ResourceGroups.
An exact description of the problem can be found here:
https://github.com/microsoft/startstopv2-deployments/issues/90
Updating / redeploying the function over github is also broken. Microsoft pushes the customers to a broken function without support. The function should be furthermore supported over Github, but isn't.
Did anybody resolve this issue (e.g. by updating the function, but how?)
Or has anybody found another solution, except of filtering machine names?
1 Reply
It is confirmed that Start/Stop VMs v2 is designed to operate at the subscription level and does not currently support scoping by resource groups. This is a known limitation, and Microsoft has stated that no further feature development will be made beyond critical updates.
https://learn.microsoft.com/en-us/azure/azure-functions/start-stop-v2/overview
