Merge pull request #308543 from cdpark/restore-stop-start-vm

Feature 449504: Q&M: Move Start/Stop VMs v2 content to the Learn archive

Author: JamesJBarnett

articles/azure-functions/start-stop-v2/TOC.yml

@@ -0,0 +1,14 @@
+- name: Start/Stop VMs
+  items:
+  - name: Overview
+    href: overview.md
+  - name: Deploy Start/Stop VMs
+    href: deploy.md
+  - name: Manage Start/Stop VMs
+    href: manage.md
+  - name: Preactions in Start/Stop VMs
+    href: actions.md
+  - name: Remove Start/Stop VMs
+    href: remove.md
+  - name: Troubleshoot Start/Stop VMs
+    href: troubleshoot.md

articles/azure-functions/start-stop-v2/actions.md

@@ -0,0 +1,56 @@
+---
+title: Add preactions to schedules in Start/Stop VMs v2 (Azure)
+titleSuffix: Azure Functions
+description: This article shows you how to add a preaction to your Start/Stop VMs v2 schedules.
+ms.service: azure-functions
+ms.date: 09/21/2022
+ms.topic: how-to
+---
+
+# Adding pre-actions to schedules in Start/Stop VMs v2
+
+Pre-actions are a set of actions in Start/Stop VMs v2 that execute before scheduled start or stop actions. Some scenarios for using pre-actions before a start or stop action include: 
+
+ - Create a backup of an Azure SQL Database.
+ - Send a message to Azure Application Insights.
+ - Call an external API.
+
+Because Start/Stop VMs v2 uses [Azure Logic Apps](../../logic-apps/logic-apps-overview.md) to manage its schedules, it's easy to add one or more pre-actions before the main action. To learn more about Logic Apps, see the [Logic Apps documentation](../../logic-apps/logic-apps-overview.md). 
+
+This article describes how to use the Logic Apps Designer in the Azure portal to add an HTTP request pre-action to an existing scheduled start action in Start/Stop VMs v2. In your implementation, the pre-action can be any action supported by Logic Apps.
+
+> [!NOTE]
+> At this time, Start/Stop VMs v2 only supports pre-actions, which are run before the execution of the main action. Because Log Apps runs Start/Stop VMs v2 actions asynchronously, there's currently no way to trigger a post-action that occurs after the main action completes. 
+
+## Prerequisites
+
+You must first complete the steps in [Deploy Start/Stop VMs v2 to an Azure subscription][deployment article], or else complete a default deployment from the [Start Stop V2 Deployments GitHub repository](https://github.com/microsoft/startstopv2-deployments). Logic app and action names are based on the ones in a default deployment of Start/Stop VMs v2.
+
+## Create an HTTP request pre-action
+
+The steps in this section require the `ststv2_vms_Scheduled_start` logic app that was created and deployed when you completed the [deployment article]. However, the same basic process is used for all scheduled actions.
+
+ 1. In the [Azure portal](https://portal.azure.com), search for and navigate to the resource group you created when you deployed Start/Stop VMs v2. 
+ 
+ 1. In the resource group, choose the logic app named `ststv2_vms_Scheduled_start`, which represents the default scheduled start action. 
+
+ 1. In **Overview** page of the logic app, select **Edit**. 
+
+ 1. In the Logic Apps Designer page, select **Function-Try** and then select **Add an action**.
+
+    :::image type="content" source="./media/pre-actions/add-action-button.png" alt-text="Screenshot of the Logic Apps designer showing Add an Action button location.":::
+
+ 5. Choose **HTTP**, select the HTTP **Method**, and add the **URL**. This HTTP request will be the pre-action for the scheduled start action, after you change the action order in **Function-Try**. You can also configure the HTTP action at a later time.
+
+ 6. Drag the **Scheduled** action below the new **HTTP** action in the **Function-Try** step. The pre-action must come before the scheduled action in the step. Your app should now look like the following example:
+
+    :::image type="content" source="./media/pre-actions/configured.png" alt-text="Screenshot of the Logic Apps designer showing the actions in the correct order.":::
+
+At this point, you've defined a pre-action that's run before the start action scheduled by `ststv2_vms_Scheduled_start`. 
+
+## Next steps
+
+If you have issues working with Start/Stop VMs v2, see the [Troubleshoot Guide](troubleshoot.md). For more assistance, you can also create an issue in the [Start Stop V2 Deployments GitHub repository](https://github.com/microsoft/startstopv2-deployments/issues).
+
+
+[deployment article]: deploy.md

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

@@ -0,0 +1,42 @@
+---
+title: Manage Start/Stop VMs v2
+titleSuffix: Azure Functions
+description: This article tells how to monitor status of your Azure VMs managed by the Start/Stop VMs v2 feature and perform other management tasks.
+ms.service: azure-functions
+ms.date: 06/08/2022
+ms.topic: conceptual
+---
+
+# How to manage Start/Stop VMs v2
+
+## Azure dashboard
+
+Start/Stop VMs v2 includes a [dashboard](/azure/azure-monitor/best-practices-analysis#azure-dashboards) to help you understand the management scope and recent operations against your VMs. It is a quick and easy way to verify the status of each operation that’s performed on your Azure VMs. The visualization in each tile is based on a Log query and to see the query, select the **Open in logs blade** option in the right-hand corner of the tile. This opens the [Log Analytics](/azure/azure-monitor/logs/log-analytics-overview#start-log-analytics) tool in the Azure portal, and from here you can evaluate the query and modify to support your needs, such as custom [log alerts](/azure/azure-monitor/alerts/alerts-log), a custom [workbook](/azure/azure-monitor/visualize/workbooks-overview), etc.
+
+The log data each tile in the dashboard displays is refreshed every hour, with a manual refresh option on demand by clicking the **Refresh** icon on a given visualization, or by refreshing the full dashboard.
+
+To learn about working with a log-based dashboard, see the following [tutorial](/azure/azure-monitor/visualize/tutorial-logs-dashboards).
+
+## Configure email notifications
+
+To change email notifications after Start/Stop VMs v2 is deployed, you can modify the action group created during deployment.
+
+1. In the Azure portal, navigate to **Monitor**, then **Alerts**. Select **Action groups**.
+
+1. On the **Manage actions** page, select the action group called **StartStopV2_VM_Notification**.
+
+    :::image type="content" source="media/manage/alerts-action-groups.png" alt-text="Screenshot of the Action groups page.":::
+
+1. On the **StartStopV2_VM_Notification** page, you can modify the Email/SMS/Push/Voice notification options. Add other actions or update your existing configuration to this action group and then click **OK** to save your changes.
+
+    :::image type="content" source="media/manage/email-notification-type-example.png" alt-text="Screenshot of the Email/SMS/Push/Voice page showing an example email address updated.":::
+
+    To learn more about action groups, see [action groups](/azure/azure-monitor/alerts/action-groups)
+
+The following screenshot is an example email that is sent when the feature shuts down virtual machines.
+
+:::image type="content" source="media/manage/email-notification-example.png" alt-text="Screenshot of an example email sent when the feature shuts down virtual machines.":::
+
+## Next steps
+
+To handle problems during VM management, see [Troubleshoot Start/Stop VMs v2](troubleshoot.md) issues.