The Start/Stop VMs during off-hours feature starts or stops enabled Azure VMs. It starts or stops machines on user-defined schedules, provides insights through Azure Application Insights, and sends optional emails by using action groups. The feature can be enabled on both Azure Resource Manager and classic VMs for most scenarios.
V2 User Guide: https://docs.microsoft.com/azure/azure-functions/start-stop-vms/overview
Note: Before you deploy this solution into your Azure subscription, please make sure you have owner permission at the subscription level.
Customers who have already deployed our Start/Stop V2 solution from the marketplace can use the below link to get the latest version. Please make sure you pass all the resource names correctly by referring to your existing deployment. This is a one-time manual effort for existing users to get the latest version, and from there you can configure the auto-update feature to get the latest version automatically.
Note: Running this template replaces previous files in the Function App, if updated file versions are available. To ensure that the file deployment is successful, we recommend that you stop the Function App before you run this template. After the template finishes running, you can start the Function App.
Customers who have already deployed our Start/Stop V2 solution from the marketplace can use the below link to get the latest version. Please make sure you pass all the resource names correctly by referring to your existing deployment. This is a one-time manual effort for existing users to get the latest version, and from there you can configure the auto-update feature to get the latest version automatically.
Note: Running this template replaces previous files in the Function App, if updated file versions are available. To ensure that the file deployment is successful, we recommend that you stop the Function App before you run this template. After the template finishes running, you can start the Function App.
After the start/stop deployment is completed, please follow the steps below to enable the feature to take action across multiple subscriptions:
- Copy the name of the Azure function that you had created during the deployment
- Navigate to your secondary subscription --> Select the subscription ---> Click on Access Control (IAM)
- Click the button "Add role assignments"
- Select the "contributor" role from the dropdown
- Enter the name of the Azure function in the "Select search by name or email address" box. Select the function name
- Click the Save button
Start/Stop V2 currently runs on .NET 6 using the in-process Functions model. Before the respective retirement dates for .NET 6 support and in-process support, we are planning to update Start/Stop V2 so that it remains on supported versions. No dates are confirmed yet for making the new .NET version or isolated process updates available for Start/Stop V2, but we will update this page once these updates are available.
February 13, 2024 Workspace-based Application insights is now available for Start/Stop v2
To update an existing Start/Stop v2 solution that you deployed, you can run the TriggerAutoUpdate Function either manually or let it run automatically on schedule. By default, it runs daily.
- The CostAnalyticsFunction and SavingsAnalyticsFunction functions might return failures such as 429 Too Many Requests errors. There is no ETA for fixing this issue, but this function does not impact the functionality of the Start/Stop V2 solution. This function is used by Microsoft to estimate aggregate savings of Start/Stop V2 across customers.
Please follow the steps below if you want to submit a support ticket from the Azure portal:
- Go to https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/overview (if public cloud) or https://portal.azure.us/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/overview (if US Government cloud)
- Click Create a support request
- In the Summary field, provide a description of the issue
- In the Issue type field, select Technical
- Select the subscription that you deployed to
- Select All services
- Select Start-Stop V2
- Select the appropriate topic from the list
- Follow the remaining steps in the form to create the support ticket
https://opensource.microsoft.com/codeofconduct
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.