Merge pull request #95513 from mrbullwinkle/mrb_11_11_2019_toc

PowerShell TOC updates

Author: GitHubber17

.openpublishing.redirection.json

@@ -43597,6 +43597,11 @@
       "source_path": "articles/active-directory/develop/app-registrations-training-guide.md",
       "redirect_url": "articles/active-directory/develop/app-registrations-training-guide-for-app-registrations-legacy-users.md",
       "redirect_document_id": false
+    },
+	{
+      "source_path": "articles/azure-monitor/app/powershell-script-create-resource.md",
+      "redirect_url": "/azure/azure-monitor/app/create-new-resource#creating-a-resource-automatically",
+      "redirect_document_id": false
     }
   ]
 }

articles/azure-monitor/app/how-do-i.md

@@ -68,7 +68,7 @@ Some points to consider:
 [Use PowerShell to create new alerts](../../azure-monitor/app/alerts.md#automation)
 
 ## Use PowerShell to Manage Application Insights
-* [Create new resources](../../azure-monitor/app/powershell-script-create-resource.md)
+* [Create new resources](https://docs.microsoft.com/azure/azure-monitor/app/create-new-resource#creating-a-resource-automatically)
 * [Create new alerts](../../azure-monitor/app/alerts.md#automation)
 
 ## Separate telemetry from different versions
@@ -94,11 +94,11 @@ Or
 <a name="search-specific-users"></a>
 
 ### Filter out anonymous or authenticated users
-If your users sign in, you can set the [authenticated user id](../../azure-monitor/app/api-custom-events-metrics.md#authenticated-users). (It doesn't happen automatically.)
+If your users sign in, you can set the [authenticated user ID](../../azure-monitor/app/api-custom-events-metrics.md#authenticated-users). (It doesn't happen automatically.)
 
 You can then:
 
-* Search on specific user ids
+* Search on specific user IDs
 
 ![](./media/how-do-i/110-search.png)
 
@@ -110,12 +110,12 @@ You can then:
 Create a [filter](../../azure-monitor/app/api-filtering-sampling.md#filtering). This lets you modify or filter telemetry before it is sent from your app to Application Insights.
 
 ## List specific users and their usage
-If you just want to [search for specific users](#search-specific-users), you can set the [authenticated user id](../../azure-monitor/app/api-custom-events-metrics.md#authenticated-users).
+If you just want to [search for specific users](#search-specific-users), you can set the [authenticated user ID](../../azure-monitor/app/api-custom-events-metrics.md#authenticated-users).
 
 If you want a list of users with data such as what pages they look at or how often they log in, you have two options:
 
-* [Set authenticated user id](../../azure-monitor/app/api-custom-events-metrics.md#authenticated-users), [export to a database](../../azure-monitor/app/code-sample-export-sql-stream-analytics.md) and use suitable tools to analyze your user data there.
-* If you have only a small number of users, send custom events or metrics, using the data of interest as the metric value or event name, and setting the user id as a property. To analyze page views, replace the standard JavaScript trackPageView call. To analyze server-side telemetry, use a telemetry initializer to add the user id to all server telemetry. You can then filter and segment metrics and searches on the user id.
+* [Set authenticated user ID](../../azure-monitor/app/api-custom-events-metrics.md#authenticated-users), [export to a database](../../azure-monitor/app/code-sample-export-sql-stream-analytics.md) and use suitable tools to analyze your user data there.
+* If you have only a small number of users, send custom events or metrics, using the data of interest as the metric value or event name, and setting the user ID as a property. To analyze page views, replace the standard JavaScript trackPageView call. To analyze server-side telemetry, use a telemetry initializer to add the user ID to all server telemetry. You can then filter and segment metrics and searches on the user ID.
 
 ## Reduce traffic from my app to Application Insights
 * In [ApplicationInsights.config](../../azure-monitor/app/configuration-with-applicationinsights-config.md), disable any modules you don't need, such the performance counter collector.
@@ -146,7 +146,7 @@ For ASP.NET Core applications you may access `TelemetryConfiguration` instance u
 You can disable standard collectors (for example, performance counters, HTTP requests, or dependencies)
 
 * **ASP.NET applications** - Delete or comment out the relevant lines in [ApplicationInsights.config](../../azure-monitor/app/configuration-with-applicationinsights-config.md)
-* **ASP.NET Core applicaitons** - Follow telemetry modules configuration options in [ApplicationInsights ASP.NET Core](../../azure-monitor/app/asp-net-core.md#configuring-or-removing-default-telemetrymodules)
+* **ASP.NET Core applications** - Follow telemetry modules configuration options in [ApplicationInsights ASP.NET Core](../../azure-monitor/app/asp-net-core.md#configuring-or-removing-default-telemetrymodules)
 
 ## View system performance counters
 Among the metrics you can show in metrics explorer are a set of system performance counters. There's a predefined blade titled **Servers** that displays several of them.

articles/azure-monitor/app/powershell-alerts.md

@@ -127,7 +127,7 @@ The metrics are sent by different telemetry modules:
 You can [automate your response to an alert](../../azure-monitor/platform/alerts-webhooks.md). Azure will call a web address of your choice when an alert is raised.
 
 ## See also
-* [Script to configure Application Insights](powershell-script-create-resource.md)
+* [Script to configure Application Insights](https://docs.microsoft.com/azure/azure-monitor/app/create-new-resource#creating-a-resource-automatically)
 * [Create Application Insights and web test resources from templates](powershell.md)
 * [Automate coupling Microsoft Azure Diagnostics to Application Insights](powershell-azure-diagnostics.md)
 * [Automate your response to an alert](../../azure-monitor/platform/alerts-webhooks.md)

articles/azure-monitor/app/powershell-script-create-resource.md

@@ -591,7 +591,7 @@ Azure should set up the resources in strict order. To make sure one setup comple
 ## Next steps
 Other automation articles:
 
-* [Create an Application Insights resource](powershell-script-create-resource.md) - quick method without using a template.
+* [Create an Application Insights resource](https://docs.microsoft.com/azure/azure-monitor/app/create-new-resource#creating-a-resource-automatically) - quick method without using a template.
 * [Set up Alerts](powershell-alerts.md)
 * [Create web tests](https://azure.microsoft.com/blog/creating-a-web-test-alert-programmatically-with-application-insights/)
 * [Send Azure Diagnostics to Application Insights](powershell-azure-diagnostics.md)

articles/azure-monitor/app/powershell.md

@@ -47,7 +47,7 @@ Set the key in an initialization method, such as global.aspx.cs in an ASP.NET se
 In this example, the ikeys for the different resources are placed in different versions of the web configuration file. Swapping the web configuration file - which you can do as part of the release script - will swap the target resource.
 
 ### Web pages
-The iKey is also used in your app's web pages, in the [script that you got from the quick start blade](../../azure-monitor/app/javascript.md). Instead of coding it literally into the script, generate it from the server state. For example, in an ASP.NET app:
+The iKey is also used in your app's web pages, in the [script that you got from the quickstart blade](../../azure-monitor/app/javascript.md). Instead of coding it literally into the script, generate it from the server state. For example, in an ASP.NET app:
 
 *JavaScript in Razor*
 
@@ -77,7 +77,7 @@ In the [portal.azure.com](https://portal.azure.com), add an Application Insights
 
 Creating the resource takes a few seconds. You'll see an alert when it's done.
 
-(You can write a [PowerShell script](../../azure-monitor/app/powershell-script-create-resource.md) to create a resource automatically.)
+(You can write a [PowerShell script](https://docs.microsoft.com/azure/azure-monitor/app/create-new-resource#creating-a-resource-automatically) to create a resource automatically.)
 
 ### Getting the instrumentation key
 The instrumentation key identifies the resource that you created. 
@@ -130,7 +130,7 @@ There are several different methods of setting the Application Version property.
     To allow MSBuild to generate version numbers, set the version like `1.0.*` in AssemblyReference.cs
 
 ## Version and release tracking
-To track the application version, make sure `buildinfo.config` is generated by your Microsoft Build Engine process. In your .csproj file, add:  
+To track the application version, make sure `buildinfo.config` is generated by your Microsoft Build Engine process. In your `.csproj` file, add:  
 
 ```XML
 
@@ -141,7 +141,7 @@ To track the application version, make sure `buildinfo.config` is generated by y
 
 When it has the build info, the Application Insights web module automatically adds **Application version** as a property to every item of telemetry. That allows you to filter by version when you perform [diagnostic searches](../../azure-monitor/app/diagnostic-search.md), or when you [explore metrics](../../azure-monitor/app/metrics-explorer.md).
 
-However, notice that the build version number is generated only by the Microsoft Build Engine, not by the developer build in Visual Studio.
+However, notice that the build version number is generated only by the Microsoft Build Engine, not by the developer build from Visual Studio.
 
 ### Release annotations
 If you use Azure DevOps, you can [get an annotation marker](../../azure-monitor/app/annotations.md) added to your charts whenever you release a new version. The following image shows how this marker appears.

articles/azure-monitor/app/separate-resources.md

@@ -1183,19 +1183,17 @@
         href: platform/autoscale-webhook-email.md
     - name: PowerShell
       items:  
-      - name: Azure PowerShell samples
+      - name: Managing with PowerShell
         href: platform/powershell-quickstart-samples.md
-      - name: PowerShell cmdlets
+      - name: Create alerts
+        href: app/powershell-alerts.md  
+      - name: Manage Log Analytics
         href: platform/powershell-workspace-configuration.md
-      - name: Applications
+      - name: Application Insights
         items:
-        - name: Create Application Insights resources 
+        - name: Manage Application Insights
           href: app/powershell.md
-        - name: Create resources
-          href: app/powershell-script-create-resource.md
-        - name: Set alerts
-          href: app/powershell-alerts.md
-        - name: Get Azure diagnostics
+        - name: Manage Azure Cloud Services
           href: app/powershell-azure-diagnostics.md
     - name: Azure CLI samples
       href: platform/cli-samples.md