Merge pull request #217409 from paulth1/app-articles-batch-10

edit pass: App articles batch 10

Author: ShawnJackson

articles/azure-monitor/app/availability-azure-functions.md

@@ -1,47 +1,58 @@
 ---
-title: Create and run custom availability tests using Azure Functions
-description: This doc will cover how to create an Azure Function with TrackAvailability() that will run periodically according to the configuration given in TimerTrigger function. The results of this test will be sent to your Application Insights resource, where you will be able to query for and alert on the availability results data. Customized tests will allow you to write more complex availability tests than is possible using the portal UI, monitor an app inside of your Azure VNET, change the endpoint address, or create an availability test if it's not available in your region.
+title: Create and run custom availability tests by using Azure Functions
+description: This article explains how to create an Azure function with TrackAvailability() that will run periodically according to the configuration given in a TimerTrigger function. 
 ms.topic: conceptual
 ms.date: 05/06/2021
 ms.devlang: csharp
 ---
 
-# Create and run custom availability tests using Azure Functions
+# Create and run custom availability tests by using Azure Functions
 
-This article will cover how to create an Azure Function with TrackAvailability() that will run periodically according to the configuration given in TimerTrigger function with your own business logic. The results of this test will be sent to your Application Insights resource, where you will be able to query for and alert on the availability results data. This allows you to create customized tests similar to what you can do via [Availability Monitoring](./monitor-web-app-availability.md) in the portal. Customized tests will allow you to write more complex availability tests than is possible using the portal UI, monitor an app inside of your Azure VNET, change the endpoint address, or create an availability test even if this feature is not available in your region.
+This article explains how to create an Azure function with `TrackAvailability()` that will run periodically according to the configuration given in the `TimerTrigger` function with your own business logic. The results of this test will be sent to your Application Insights resource, where you can query for and alert on the availability results data. Then you can create customized tests similar to what you can do via [availability monitoring](./monitor-web-app-availability.md) in the Azure portal. By using customized tests, you can:
+
+- Write more complex availability tests than is possible by using the portal UI.
+- Monitor an app inside of your Azure virtual network.
+- Change the endpoint address.
+- Create an availability test even if this feature isn't available in your region.
 
 > [!NOTE]
-> This example is designed solely to show you the mechanics of how the TrackAvailability() API call works within an Azure Function. Not how to write the underlying HTTP Test code/business logic that would be required to turn this into a fully functional availability test. By default if you walk through this example you will be creating a basic availability HTTP GET test.
+> This example is designed solely to show you the mechanics of how the `TrackAvailability()` API call works within an Azure function. It doesn't show you how to write the underlying HTTP test code or business logic that's required to turn this example into a fully functional availability test. By default, if you walk through this example, you'll be creating a basic availability HTTP GET test.
+>
 > To follow these instructions, you must use the [dedicated plan](../../azure-functions/dedicated-plan.md) to allow editing code in App Service Editor.
 
 ## Create a timer trigger function
 
 1. Create an Azure Functions resource.
-    - If you already have an Application Insights Resource:
-        - By default Azure Functions creates an Application Insights resource but if you would like to use one of your already created resources you will need to specify that during creation.
+    - If you already have an Application Insights resource:
+    
+        - By default, Azure Functions creates an Application Insights resource. But if you want to use a resource you created previously, you must specify that during creation.
         - Follow the instructions on how to [create an Azure Functions resource](../../azure-functions/functions-create-scheduled-function.md#create-a-function-app) with the following modification:
-            - On the **Monitoring** tab, select the Application Insights dropdown box then type or select the name of your resource.
-                :::image type="content" source="media/availability-azure-functions/app-insights-resource.png" alt-text="On the monitoring tab select your existing Application Insights resource.":::
-    - If you do not have an Application Insights Resource created yet for your timer triggered function:
-        - By default when you are creating your Azure Functions application it will create an Application Insights resource for you. Follow the instructions on how to [create an Azure Functions resource](../../azure-functions/functions-create-scheduled-function.md#create-a-function-app).
+          
+          On the **Monitoring** tab, select the **Application Insights** dropdown box and then enter or select the name of your resource.
+            
+          :::image type="content" source="media/availability-azure-functions/app-insights-resource.png" alt-text="Screenshot that shows selecting your existing Application Insights resource on the Monitoring tab.":::
+
+    - If you don't have an Application Insights resource created yet for your timer-triggered function:
+        - By default, when you're creating your Azure Functions application, it will create an Application Insights resource for you. Follow the instructions on how to [create an Azure Functions resource](../../azure-functions/functions-create-scheduled-function.md#create-a-function-app).
+        
     > [!NOTE]
-    > You can host your functions on a Consumption, Premium, or App Service plan. If you are testing behind a V-Net or testing non public endpoints then you will need to use the premium plan in place of the consumption. Select your plan on the **Hosting** tab. Please ensure the latest .NET version is selected when creating the Function App.
-2. Create a timer trigger function.
+    > You can host your functions on a Consumption, Premium, or App Service plan. If you're testing behind a virtual network or testing nonpublic endpoints, you'll need to use the Premium plan in place of the Consumption plan. Select your plan on the **Hosting** tab. Ensure the latest .NET version is selected when you create the function app.
+1. Create a timer trigger function.
     1. In your function app, select the **Functions** tab.
-    1. Select **Add** and in the Add function tab select the follow configurations:
-        1. Development environment: *Develop in portal*
-        1. Select a template: *Timer trigger*
-    1. Select **Add** to create the Timer trigger function.
+    1. Select **Add**. On the **Add function** pane, select the following configurations:
+        1. **Development environment**: **Develop in portal**
+        1. **Select a template**: **Timer trigger**
+    1. Select **Add** to create the timer trigger function.
 
-    :::image type="content" source="media/availability-azure-functions/add-function.png" alt-text="Screenshot of how to add a timer trigger function to your function app." lightbox="media/availability-azure-functions/add-function.png":::
+    :::image type="content" source="media/availability-azure-functions/add-function.png" alt-text="Screenshot that shows how to add a timer trigger function to your function app." lightbox="media/availability-azure-functions/add-function.png":::
 
 ## Add and edit code in the App Service Editor
 
-Navigate to your deployed function app and under *Development Tools* select the **App Service Editor** tab.
+Go to your deployed function app, and under **Development Tools**, select the **App Service Editor** tab.
 
-To create a new file, right click under your timer trigger function (for example "TimerTrigger1") and select **New File**. Then type the name of the file and press enter.
+To create a new file, right-click under your timer trigger function (for example, **TimerTrigger1**) and select **New File**. Then enter the name of the file and select **Enter**.
 
-1. Create a new file called "function.proj" and paste the following code:
+1. Create a new file called **function.proj** and paste the following code:
 
     ```xml
     <Project Sdk="Microsoft.NET.Sdk"> 
@@ -54,9 +65,9 @@ To create a new file, right click under your timer trigger function (for example
     </Project> 
     ```
 
-    :::image type="content" source="media/availability-azure-functions/function-proj.png" alt-text=" Screenshot of function.proj in App Service Editor." lightbox="media/availability-azure-functions/function-proj.png":::
+    :::image type="content" source="media/availability-azure-functions/function-proj.png" alt-text=" Screenshot that shows function.proj in the App Service Editor." lightbox="media/availability-azure-functions/function-proj.png":::
 
-2. Create a new file called "runAvailabilityTest.csx" and paste the following code:
+1. Create a new file called **runAvailabilityTest.csx** and paste the following code:
 
     ```csharp
     using System.Net.Http; 
@@ -71,7 +82,7 @@ To create a new file, right click under your timer trigger function (for example
     } 
     ```
 
-3. Copy the code below into the run.csx file (this will replace the pre-existing code):
+1. Copy the following code into the **run.csx** file. (You'll replace the preexisting code.)
 
     ```csharp
     #load "runAvailabilityTest.csx" 
@@ -161,26 +172,26 @@ To create a new file, right click under your timer trigger function (for example
 
 ## Check availability
 
-To make sure everything is working, you can look at the graph in the Availability tab of your Application Insights resource.
+To make sure everything is working, look at the graph on the **Availability** tab of your Application Insights resource.
 
 > [!NOTE]
-> Tests created with TrackAvailability() will appear with **CUSTOM** next to the test name.
+> Tests created with `TrackAvailability()` will appear with **CUSTOM** next to the test name.
 
- :::image type="content" source="media/availability-azure-functions/availability-custom.png" alt-text="Availability tab with successful results." lightbox="media/availability-azure-functions/availability-custom.png":::
+ :::image type="content" source="media/availability-azure-functions/availability-custom.png" alt-text="Screenshot that shows the Availability tab with successful results." lightbox="media/availability-azure-functions/availability-custom.png":::
 
-To see the end-to-end transaction details, select **Successful** or **Failed** under drill into, then select a sample. You can also get to the end-to-end transaction details by selecting a data point on the graph.
+To see the end-to-end transaction details, under **Drill into**, select **Successful** or **Failed**. Then select a sample. You can also get to the end-to-end transaction details by selecting a data point on the graph.
 
-:::image type="content" source="media/availability-azure-functions/sample.png" alt-text="Select a sample availability test.":::
+:::image type="content" source="media/availability-azure-functions/sample.png" alt-text="Screenshot that shows selecting a sample availability test.":::
 
-:::image type="content" source="media/availability-azure-functions/end-to-end.png" alt-text="End-to-end transaction details." lightbox="media/availability-azure-functions/end-to-end.png":::
+:::image type="content" source="media/availability-azure-functions/end-to-end.png" alt-text="Screenshot that shows end-to-end transaction details." lightbox="media/availability-azure-functions/end-to-end.png":::
 
-## Query in Logs (Analytics)
+## Query in Log Analytics
 
-You can use Logs(analytics) to view you availability results, dependencies, and more. To learn more about Logs, visit [Log query overview](../logs/log-query-overview.md).
+You can use Log Analytics to view your availability results, dependencies, and more. To learn more about Log Analytics, see [Log query overview](../logs/log-query-overview.md).
 
-:::image type="content" source="media/availability-azure-functions/availabilityresults.png" alt-text="Availability results." lightbox="media/availability-azure-functions/availabilityresults.png":::
+:::image type="content" source="media/availability-azure-functions/availabilityresults.png" alt-text="Screenshot that shows availability results." lightbox="media/availability-azure-functions/availabilityresults.png":::
 
-:::image type="content" source="media/availability-azure-functions/dependencies.png" alt-text="Screenshot shows New Query tab with dependencies limited to 50." lightbox="media/availability-azure-functions/dependencies.png":::
+:::image type="content" source="media/availability-azure-functions/dependencies.png" alt-text="Screenshot that shows the New Query tab with dependencies limited to 50." lightbox="media/availability-azure-functions/dependencies.png":::
 
 ## Next steps