Skip to content

Commit dead2fa

Browse files
Merge pull request #286252 from gabesmsft/patch-10
Update deploy.md
2 parents 58406ef + 612061f commit dead2fa

File tree

1 file changed

+4
-4
lines changed
  • articles/azure-functions/start-stop-vms

1 file changed

+4
-4
lines changed

articles/azure-functions/start-stop-vms/deploy.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -141,8 +141,8 @@ For each scenario, you can target the action against one or more subscriptions,
141141

142142
:::image type="content" source="media/deploy/schedule-recurrence-property.png" alt-text="Configure the recurrence frequency for logic app":::
143143

144-
> [!NOTE]
145-
> 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.
144+
> [!NOTE]
145+
> 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.
146146
147147
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.
148148

@@ -241,8 +241,8 @@ In an environment that includes two or more components on multiple Azure Resourc
241241

242242
:::image type="content" source="media/deploy/schedule-recurrence-property.png" alt-text="Configure the recurrence frequency for logic app":::
243243

244-
> [!NOTE]
245-
> 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.
244+
> [!NOTE]
245+
> 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.
246246

247247
1. In the designer pane, select **Function-Try** to configure the target settings and then select the **</> Code view** button in the top menu to edit the code for the **Function-Try** element. 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.
248248

0 commit comments

Comments
 (0)