Merge branch 'main' of github.com:MicrosoftDocs/azure-docs-pr into sdg-main-toc2

Author: sdgilley

articles/azure-monitor/app/configuration-with-applicationinsights-config.md

@@ -1,6 +1,6 @@
 ---
-title: Azure Application Insights for Console Applications | Microsoft Docs
-description: Monitor web applications for availability, performance and usage.
+title: Application Insights for console applications | Microsoft Docs
+description: Monitor web applications for availability, performance, and usage.
 ms.topic: conceptual
 ms.date: 05/21/2020
 ms.devlang: csharp
@@ -12,58 +12,59 @@ ms.reviewer: casocha
 
 [Application Insights](./app-insights-overview.md) lets you monitor your web application for availability, performance, and usage.
 
-You need a subscription with [Microsoft Azure](https://azure.com). Sign in with a Microsoft account, which you might have for Windows, Xbox Live, or other Microsoft cloud services. Your team might have an organizational subscription to Azure: ask the owner to add you to it using your Microsoft account.
+You need an [Azure](https://azure.com) subscription. Sign in with a Microsoft account, which you might have for Windows, Xbox Live, or other Microsoft cloud services. Your team might have an organizational subscription to Azure. Ask the owner to add you to it by using your Microsoft account.
 
 > [!NOTE]
-> It is *highly recommended* to use the newer [Microsoft.ApplicationInsights.WorkerService](https://www.nuget.org/packages/Microsoft.ApplicationInsights.WorkerService) package and associated instructions from [here](./worker-service.md) for any Console Applications. This package is compatible with [Long Term Support (LTS) versions](https://dotnet.microsoft.com/platform/support/policy/dotnet-core) of .NET Core and .NET Framework or higher.
+> We recommend using the newer [Microsoft.ApplicationInsights.WorkerService](https://www.nuget.org/packages/Microsoft.ApplicationInsights.WorkerService) package and associated instructions from [Application Insights for Worker Service applications (non-HTTP applications)](./worker-service.md) for any console applications. This package is compatible with [Long Term Support (LTS) versions](https://dotnet.microsoft.com/platform/support/policy/dotnet-core) of .NET Core and .NET Framework or higher.
 
 [!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
 
-## Getting started
+## Get started
 
 * In the [Azure portal](https://portal.azure.com), [create an Application Insights resource](./create-new-resource.md).
-* Take a copy of the connection string. Find the connection string in the **Essentials** drop-down of the new resource you created.
-* Install latest [Microsoft.ApplicationInsights](https://www.nuget.org/packages/Microsoft.ApplicationInsights) package.
-* Set the connection string in your code before tracking any telemetry (or set the APPLICATIONINSIGHTS_CONNECTION_STRING environment variable). After that, you should be able to manually track telemetry and see it on the Azure portal
-
-```csharp
-// you may use different options to create configuration as shown later in this article
-TelemetryConfiguration configuration = TelemetryConfiguration.CreateDefault();
-configuration.ConnectionString = <Copy connection string from Application Insights Resource Overview>;
-var telemetryClient = new TelemetryClient(configuration);
-telemetryClient.TrackTrace("Hello World!");
-```
-
-> [!NOTE]
-> - Telemetry isn't sent instantly; items are batched and sent by the ApplicationInsights SDK. Console apps exit after calling `Track()` methods.
-> - Telemetry may not be sent unless `Flush()` and `Sleep`/`Delay` is done before the app exits as shown in [full example](#full-example) later in this article. `Sleep` is not required if you're using `InMemoryChannel`.
-
-* Install latest version of [Microsoft.ApplicationInsights.DependencyCollector](https://www.nuget.org/packages/Microsoft.ApplicationInsights.DependencyCollector) package - it automatically tracks HTTP, SQL, or some other external dependency calls.
-
-You may initialize and configure Application Insights from the code or using `ApplicationInsights.config` file. Make sure initialization happens as early as possible.
+* Take a copy of the connection string. Find the connection string in the **Essentials** dropdown of the new resource you created.
+* Install the latest [Microsoft.ApplicationInsights](https://www.nuget.org/packages/Microsoft.ApplicationInsights) package.
+* Set the connection string in your code before you track any telemetry (or set the `APPLICATIONINSIGHTS_CONNECTION_STRING` environment variable). After that, you should be able to manually track telemetry and see it in the Azure portal.
+    
+    ```csharp
+    // You may use different options to create configuration as shown later in this article
+    TelemetryConfiguration configuration = TelemetryConfiguration.CreateDefault();
+    configuration.ConnectionString = <Copy connection string from Application Insights Resource Overview>;
+    var telemetryClient = new TelemetryClient(configuration);
+    telemetryClient.TrackTrace("Hello World!");
+    ```
+    
+    > [!NOTE]
+    > Telemetry isn't sent instantly. Items are batched and sent by the ApplicationInsights SDK. Console apps exit after calling `Track()` methods.
+    >
+    > Telemetry might not be sent unless `Flush()` and `Sleep`/`Delay` are done before the app exits, as shown in the [full example](#full-example) later in this article. `Sleep` isn't required if you're using `InMemoryChannel`.
+
+* Install the latest version of the [Microsoft.ApplicationInsights.DependencyCollector](https://www.nuget.org/packages/Microsoft.ApplicationInsights.DependencyCollector) package. It automatically tracks HTTP, SQL, or some other external dependency calls.
+
+You can initialize and configure Application Insights from the code or by using `ApplicationInsights.config` file. Make sure initialization happens as early as possible.
 
 > [!NOTE]
-> - **ApplicationInsights.config** is not supported by .NET Core applications.
+> *ApplicationInsights.config* isn't supported by .NET Core applications.
 
-### Using config file 
+### Use the config file
 
-For .NET Framework based application, by default, Application Insights SDK looks for `ApplicationInsights.config` file in the working directory when `TelemetryConfiguration` is being created. Reading config file is not supported on .NET Core.
+For .NET Framework-based applications, by default, the Application Insights SDK looks for the `ApplicationInsights.config` file in the working directory when `TelemetryConfiguration` is being created. Reading the config file isn't supported on .NET Core.
 
 ```csharp
 TelemetryConfiguration config = TelemetryConfiguration.Active; // Reads ApplicationInsights.config file if present
 ```
 
-You may also specify path to the config file.
+You can also specify a path to the config file:
 
 ```csharp
 using System.IO;
 TelemetryConfiguration configuration = TelemetryConfiguration.CreateFromConfiguration(File.ReadAllText("C:\\ApplicationInsights.config"));
 var telemetryClient = new TelemetryClient(configuration);
 ```
 
-For more information, see [configuration file reference](configuration-with-applicationinsights-config.md).
+For more information, see [Configuration file reference](configuration-with-applicationinsights-config.md).
 
-You may get a full example of the config file by installing latest version of [Microsoft.ApplicationInsights.WindowsServer](https://www.nuget.org/packages/Microsoft.ApplicationInsights.WindowsServer) package. Here's the **minimal** configuration for dependency collection that is equivalent to the code example.
+You can get a full example of the config file by installing the latest version of the [Microsoft.ApplicationInsights.WindowsServer](https://www.nuget.org/packages/Microsoft.ApplicationInsights.WindowsServer) package. Here's the *minimal* configuration for dependency collection that's equivalent to the code example:
 
 ```xml
 <?xml version="1.0" encoding="utf-8"?>
@@ -93,44 +94,45 @@ You may get a full example of the config file by installing latest version of [M
 
 ```
 
-### Configuring telemetry collection from code
-> [!NOTE]
-> Reading config file is not supported on .NET Core. 
-
-* During application start-up, create and configure `DependencyTrackingTelemetryModule` instance - it must be singleton and must be preserved for application lifetime.
-
-```csharp
-var module = new DependencyTrackingTelemetryModule();
-
-// prevent Correlation Id to be sent to certain endpoints. You may add other domains as needed.
-module.ExcludeComponentCorrelationHttpHeadersOnDomains.Add("core.windows.net");
-//...
-
-// enable known dependency tracking, note that in future versions, we will extend this list. 
-// please check default settings in https://github.com/Microsoft/ApplicationInsights-dotnet-server/blob/develop/Src/DependencyCollector/DependencyCollector/ApplicationInsights.config.install.xdt
+### Configure telemetry collection from code
 
-module.IncludeDiagnosticSourceActivities.Add("Microsoft.Azure.ServiceBus");
-module.IncludeDiagnosticSourceActivities.Add("Microsoft.Azure.EventHubs");
-//....
-
-// initialize the module
-module.Initialize(configuration);
-```
-
-* Add common telemetry initializers
-
-```csharp
-// ensures proper DependencyTelemetry.Type is set for Azure RESTful API calls
-configuration.TelemetryInitializers.Add(new HttpDependenciesParsingTelemetryInitializer());
-```
-
-If you created configuration with plain `TelemetryConfiguration()` constructor, you need to enable correlation support additionally. **It is not needed** if you read configuration from file, used `TelemetryConfiguration.CreateDefault()` or `TelemetryConfiguration.Active`.
-
-```csharp
-configuration.TelemetryInitializers.Add(new OperationCorrelationTelemetryInitializer());
-```
-
-* You may also want to install and initialize Performance Counter collector module as described [here](https://apmtips.com/posts/2017-02-13-enable-application-insights-live-metrics-from-code/)
+> [!NOTE]
+> Reading the config file isn't supported on .NET Core.
+
+* During application startup, create and configure a `DependencyTrackingTelemetryModule` instance. It must be singleton and must be preserved for the application lifetime.
+
+    ```csharp
+    var module = new DependencyTrackingTelemetryModule();
+    
+    // prevent Correlation Id to be sent to certain endpoints. You may add other domains as needed.
+    module.ExcludeComponentCorrelationHttpHeadersOnDomains.Add("core.windows.net");
+    //...
+    
+    // enable known dependency tracking, note that in future versions, we will extend this list. 
+    // please check default settings in https://github.com/Microsoft/ApplicationInsights-dotnet-server/blob/develop/Src/DependencyCollector/DependencyCollector/ApplicationInsights.config.install.xdt
+    
+    module.IncludeDiagnosticSourceActivities.Add("Microsoft.Azure.ServiceBus");
+    module.IncludeDiagnosticSourceActivities.Add("Microsoft.Azure.EventHubs");
+    //....
+    
+    // initialize the module
+    module.Initialize(configuration);
+    ```
+
+* Add common telemetry initializers:
+
+    ```csharp
+    // ensures proper DependencyTelemetry.Type is set for Azure RESTful API calls
+    configuration.TelemetryInitializers.Add(new HttpDependenciesParsingTelemetryInitializer());
+    ```
+    
+    If you created configuration with a plain `TelemetryConfiguration()` constructor, you need to enable correlation support additionally. *It isn't needed* if you read configuration from a file or used `TelemetryConfiguration.CreateDefault()` or `TelemetryConfiguration.Active`.
+    
+    ```csharp
+    configuration.TelemetryInitializers.Add(new OperationCorrelationTelemetryInitializer());
+    ```
+
+* You might also want to install and initialize the Performance Counter collector module as described at [this website](https://apmtips.com/posts/2017-02-13-enable-application-insights-live-metrics-from-code/).
 
 #### Full example
 
@@ -209,5 +211,6 @@ namespace ConsoleApp
 ```
 
 ## Next steps
+
 * [Monitor dependencies](./asp-net-dependencies.md) to see if REST, SQL, or other external resources are slowing you down.
 * [Use the API](./api-custom-events-metrics.md) to send your own events and metrics for a more detailed view of your app's performance and usage.

articles/azure-monitor/app/console.md

@@ -6,51 +6,51 @@ ms.date: 07/30/2021
 ms.reviewer: mmcc
 ---
 
-# Users, sessions, and events analysis in Application Insights
+# User, session, and event analysis in Application Insights
 
 Find out when people use your web app, what pages they're most interested in, where your users are located, and what browsers and operating systems they use. Analyze business and usage telemetry by using [Application Insights](./app-insights-overview.md).
 
 :::image type="content" source="./media/usage-segmentation/users.png" alt-text="Screen capture shows the Users tab with an area chart. " lightbox="./media/usage-overview/users.png":::
 
 ## Get started
 
-If you don't yet see data in the users, sessions, or events blades in the Application Insights portal, [learn how to get started with the usage tools](usage-overview.md).
+If you don't yet see data in the **Users**, **Sessions**, or **Events** panes in the Application Insights portal, [learn how to get started with the Usage tools](usage-overview.md).
 
 ## The Users, Sessions, and Events segmentation tool
 
-Three of the usage blades use the same tool to slice and dice telemetry from your web app from three perspectives. By filtering and splitting the data, you can uncover insights about the relative usage of different pages and features.
+Three of the **Usage** panes use the same tool to slice and dice telemetry from your web app from three perspectives. By filtering and splitting the data, you can uncover insights about the relative use of different pages and features.
 
-* **Users tool**: How many people used your app and its features.  Users are counted by using anonymous IDs stored in browser cookies. A single person using different browsers or machines will be counted as more than one user.
-* **Sessions tool**: How many sessions of user activity have included certain pages and features of your app. A session is counted after half an hour of user inactivity, or after 24 hours of continuous use.
-* **Events tool**: How often certain pages and features of your app are used. A page view is counted when a browser loads a page from your app, provided you've [instrumented it](./javascript.md). 
+* **Users tool**: How many people used your app and its features? Users are counted by using anonymous IDs stored in browser cookies. A single person using different browsers or machines will be counted as more than one user.
+* **Sessions tool**: How many sessions of user activity have included certain pages and features of your app? A session is counted after half an hour of user inactivity, or after 24 hours of continuous use.
+* **Events tool**: How often are certain pages and features of your app used? A page view is counted when a browser loads a page from your app, provided you've [instrumented it](./javascript.md).
+
+    A custom event represents one occurrence of something happening in your app. It's often a user interaction like a button selection or the completion of a task. You insert code in your app to [generate custom events](./api-custom-events-metrics.md#trackevent).
 
-    A custom event represents one occurrence of something happening in your app, often a user interaction like a button select or the completion of some task. You insert code in your app to [generate custom events](./api-custom-events-metrics.md#trackevent).
-    
 > [!NOTE]
-> For details on an alternative to using [anonymous IDs](./data-model-context.md#anonymous-user-id) and ensuring an accurate count, reference the documentation for [authenticated IDs](./data-model-context.md#authenticated-user-id).
+> For information on an alternatives to using [anonymous IDs](./data-model-context.md#anonymous-user-id) and ensuring an accurate count, see the documentation for [authenticated IDs](./data-model-context.md#authenticated-user-id).
 
-## Querying for certain users
+## Query for certain users
 
 Explore different groups of users by adjusting the query options at the top of the Users tool:
 
-- During: Choose a time range.
-- Show: Choose a cohort of users to analyze.
-- Who used: Choose which custom events, requests, and page views.
-- Events: Choose multiple events, requests, and page views that will show users who did at least one, not necessarily all of the selected.
-- By value x-axis: Choose how to bucket the data, either by time range or by another property such as browser or city.
-- Split By: Choose a property by which to split or segment the data. 
-- Add Filters: Limit the query to certain users, sessions, or events based on their properties, such as browser or city. 
- 
+- **During**: Choose a time range.
+- **Show**: Choose a cohort of users to analyze.
+- **Who used**: Choose custom events, requests, and page views.
+- **Events**: Choose multiple events, requests, and page views that will show users who did at least one, not necessarily all, of the selected options.
+- **By value x-axis**: Choose how to categorize the data, either by time range or by another property, such as browser or city.
+- **Split By**: Choose a property to use to split or segment the data.
+- **Add Filters**: Limit the query to certain users, sessions, or events based on their properties, such as browser or city.
+
 ## Meet your users
 
-The **Meet your users** section shows information about five sample users matched by the current query. Exploring the behaviors of individuals and in aggregate, can provide insights about how people actually use your app.
+The **Meet your users** section shows information about five sample users matched by the current query. Exploring the behaviors of individuals and in aggregate can provide insights about how people use your app.
 
 ## Next steps
 
 - To enable usage experiences, start sending [custom events](./api-custom-events-metrics.md#trackevent) or [page views](./api-custom-events-metrics.md#page-views).
-- If you already send custom events or page views, explore the Usage tools to learn how users use your service.
+- If you already send custom events or page views, explore the **Usage** tools to learn how users use your service.
     - [Funnels](usage-funnels.md)
     - [Retention](usage-retention.md)
-    - [User Flows](usage-flows.md)
+    - [User flows](usage-flows.md)
     - [Workbooks](../visualize/workbooks-overview.md)
     - [Add user context](./usage-overview.md)

articles/azure-monitor/app/usage-segmentation.md

@@ -56,6 +56,10 @@ To troubleshoot issues related to SMS delivery, you can [enable delivery reporti
 
 If you want to clean up and remove a Communication Services subscription, you can delete the resource or resource group. Deleting the resource group also deletes any other resources associated with it. Learn more about [cleaning up resources](../create-communication-resource.md#clean-up-resources).
 
+## Toll-free verification
+
+If you have a new toll-free number and want to send [high volume of SMS messages](../../concepts/sms/sms-faq.md#what-happens-if-i-dont-verify-my-toll-free-numbers) or send SMS messages to Canadian phone numbers, please visit [here](../../concepts/sms/sms-faq.md#how-do-i-submit-a-toll-free-verification) to learn how to verify your toll-free number. 
+
 ## Next steps
 
 In this quickstart, you learned how to send SMS messages by using Communication Services.

articles/communication-services/quickstarts/sms/send.md

@@ -470,3 +470,4 @@ resource subToMG 'Microsoft.Management/managementGroups/subscriptions@2020-05-01
 * Now that you've created a subscription, you can grant that ability to other users and service principals. For more information, see [Grant access to create Azure Enterprise subscriptions (preview)](grant-access-to-create-subscription.md).
 * For more information about managing large numbers of subscriptions using management groups, see [Organize your resources with Azure management groups](../../governance/management-groups/overview.md).
 * To change the management group for a subscription, see [Move subscriptions](../../governance/management-groups/manage.md#move-subscriptions).
+* For advanced subscription creation scenarios using REST API, see [Alias - Create](/rest/api/subscription/2021-10-01/alias/create).