You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-functions/start-stop-v2/deploy.md
+10-9Lines changed: 10 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,8 @@
1
1
---
2
2
title: Deploy Start/Stop VMs v2 to an Azure subscription
3
+
titleSuffix: Azure Functions
3
4
description: This article tells how to deploy the Start/Stop VMs v2 feature for your Azure VMs in your Azure subscription.
4
-
services: azure-functions
5
+
ms.service: azure-functions
5
6
ms.date: 06/08/2022
6
7
ms.topic: how-to
7
8
ms.custom: subject-rbac-steps
@@ -34,7 +35,7 @@ To simplify management and removal, we recommend you deploy Start/Stop VMs v2 to
34
35
> Currently this solution does not support specifying an existing Storage account or Application Insights resource.
35
36
36
37
> [!NOTE]
37
-
> The naming format for the function app and storage account has changed. To guarantee global uniqueness, a random and unique string is now appended to the names of these resource.
38
+
> The naming format for the function app and storage account changed. To guarantee global uniqueness, a random and unique string is now appended to the names of these resources.
38
39
39
40
1. Open your browser and navigate to the Start/Stop VMs v2 [GitHub organization](https://github.com/microsoft/startstopv2-deployments/blob/main/README.md).
40
41
1. Select the deployment option based on the Azure cloud environment your Azure VMs are created in.
@@ -63,10 +64,10 @@ To simplify management and removal, we recommend you deploy Start/Stop VMs v2 to
63
64
|Name |Value |
64
65
|-----|------|
65
66
|Region |Select a region near you for new resources.|
66
-
|Resource Group Name |Specify the resource group name that will contain the individual resources for Start/Stop VMs. |
67
+
|Resource Group Name |Specify the resource group name that contain the individual resources for Start/Stop VMs. |
67
68
|Resource Group Region |Specify the region for the resource group. For example, **Central US**.|
68
-
|Azure Function App Name |Type a name that is valid in a URL path. The name you type is validated to make sure that it's unique in Azure Functions. |
69
-
|Application Insights Name |Specify the name of your Application Insights instance that will hold the analytics for Start/Stop VMs. |
69
+
|Azure Function App Name |Type a name that's valid in a URL path. The name you type is validated to make sure that it's unique in Azure Functions. |
70
+
|Application Insights Name |Specify the name of your Application Insights instance that holds the analytics for Start/Stop VMs. |
70
71
|Application Insights Region |Specify the region for the Application Insights instance.|
71
72
|Storage Account Name |Specify the name of the Azure Storage account to store Start/Stop VMs execution telemetry. |
72
73
|Email Address |Specify one or more email addresses to receive status notifications, separated by a comma (,).|
@@ -81,7 +82,7 @@ To simplify management and removal, we recommend you deploy Start/Stop VMs v2 to
> We are collecting operation and heartbeat telemetry to better assist you if you reach the support team for any troubleshooting. We are also collecting virtual machine event history to verify when the service acted on a virtual machine and how long a virtual machine was snoozed in order to determine the efficacy of the service.
85
+
> We collect operation and heartbeat telemetry to better assist you if you reach the support team for any troubleshooting. We also collect virtual machine event history to verify when the service acted on a virtual machine and how long a virtual machine was snoozed in order to determine the efficacy of the service.
85
86
86
87
## Enable multiple subscriptions
87
88
@@ -111,7 +112,7 @@ To manage the automation method to control the start and stop of your VMs, you c
111
112
112
113
- Scheduled - Start and stop actions are based on a schedule you specify against Azure Resource Manager and classic VMs. **ststv2_vms_Scheduled_start** and **ststv2_vms_Scheduled_stop** configure the scheduled start and stop.
113
114
114
-
- Sequenced - Start and stop actions are based on a schedule targeting VMs with pre-defined sequencing tags. Only two named tags are supported - **sequencestart** and **sequencestop**. **ststv2_vms_Sequenced_start** and **ststv2_vms_Sequenced_stop** configure the sequenced start and stop.
115
+
- Sequenced - Start and stop actions are based on a schedule targeting VMs with predefined sequencing tags. Only two named tags are supported - **sequencestart** and **sequencestop**. **ststv2_vms_Sequenced_start** and **ststv2_vms_Sequenced_stop** configure the sequenced start and stop.
115
116
116
117
> [!NOTE]
117
118
> This scenario only supports Azure Resource Manager VMs.
@@ -126,7 +127,7 @@ Perform the following steps to configure the scheduled start and stop action for
126
127
127
128
Configuring the logic app to just start the VMs is supported.
128
129
129
-
For each scenario, you can target the action against one or more subscriptions, single or multiple resource groups, and specify one or more VMs in an inclusion or exclusion list. You cannot specify them together in the same logic app.
130
+
For each scenario, you can target the action against one or more subscriptions, single or multiple resource groups, and specify one or more VMs in an inclusion or exclusion list. You can't specify them together in the same logic app.
130
131
131
132
1. Sign in to the [Azure portal](https://portal.azure.com) and then navigate to **Logic apps**.
132
133
@@ -139,7 +140,7 @@ For each scenario, you can target the action against one or more subscriptions,
139
140
:::image type="content" source="media/deploy/schedule-recurrence-property.png" alt-text="Configure the recurrence frequency for logic app":::
140
141
141
142
> [!NOTE]
142
-
> If you do not provide a start date and time for the first recurrence, a recurrence will immediately run when you save the logic app, which might cause the VMs to start or stop before the scheduled run.
143
+
> If you don't provide a start date and time for the first recurrence, a recurrence immediately runs when you save the logic app, which might cause the VMs to start or stop before the scheduled run.
143
144
144
145
1. In the designer pane, select **Function-Try** to configure the target settings. In the request body, if you want to manage VMs across all resource groups in the subscription, modify the request body as shown in the following example.
0 commit comments