Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr

Author: msjasteppe

articles/azure-monitor/agents/om-agents.md

@@ -30,7 +30,7 @@ If your IT security policies do not allow computers on your network to connect t
 Before starting, review the following requirements.
 
 >[!Note]
->From 1 February 2023, System Center Operations Manager version lower than [2019 UR3](/system-center/scom/release-build-versions?view=sc-om-2019#agents) will stop sending data to Log Analytics workspace. Ensure your agents are on SCOM Agent version 10.19.10177.0 ([2019 UR3](/system-center/scom/release-build-versions?view=sc-om-2019#agents) or later) or 10.22.10056.0 ([2022 RTM](/system-center/scom/release-build-versions?view=sc-om-2022#agents)) and SCOM Management Group version is SCOM 2022 & 2019 UR3 or later version.
+>From 1 February 2023, System Center Operations Manager version lower than [2019 UR3](/system-center/scom/release-build-versions?view=sc-om-2019#agents&preserve-view=true) will stop sending data to Log Analytics workspace. Ensure your agents are on SCOM Agent version 10.19.10177.0 ([2019 UR3](/system-center/scom/release-build-versions?view=sc-om-2019#agents&preserve-view=true) or later) or 10.22.10056.0 ([2022 RTM](/system-center/scom/release-build-versions?view=sc-om-2022#agents&preserve-view=true)) and SCOM Management Group version is SCOM 2022 & 2019 UR3 or later version.
 
 * Azure Monitor supports the following:
     * System Center Operations Manager 2022
@@ -57,10 +57,9 @@ Before starting, review the following requirements.
 >[!NOTE]
 >Recent changes to Azure APIs will prevent customers from being able to successfully configure integration between their management group and Azure Monitor for the first time. For customers who have already integrated their management group with the service, you are not impacted unless you need to reconfigure your existing connection.  
 >A new management pack has been released for the following versions of Operations Manager:
-> - For System Center Operations Manager 2019, this management pack is included with the source media and installed during setup of a new management group or during an upgrade.
->- Operations Manager 1801 management pack is also applicable for Operations Manager 1807.
->- For System Center Operations Manager 1801, download the management pack from [here](https://www.microsoft.com/download/details.aspx?id=57173).
->- For System Center 2016 - Operations Manager, download the management pack from [here](https://www.microsoft.com/download/details.aspx?id=57172).  
+> - For System Center Operations Manager 2019 and newer, this management pack is included with the source media and installed during setup of a new management group or during an upgrade.
+>- For System Center Operations Manager 1801/1807, download the management pack from [here](https://www.microsoft.com/download/details.aspx?id=57173).
+>- For System Center Operations Manager 2016, download the management pack from [here](https://www.microsoft.com/download/details.aspx?id=57172).  
 >- For System Center Operations Manager 2012 R2, download the management pack from [here](https://www.microsoft.com/download/details.aspx?id=57171).  
 
 

articles/azure-monitor/app/convert-classic-resource.md

@@ -1,137 +1,120 @@
 ---
-title: Azure Application Insights Telemetry Data Model - Telemetry Context | Microsoft Docs
-description: Application Insights telemetry context data model
+title: 'Application Insights telemetry data model: Telemetry context | Microsoft Docs'
+description: Learn about the Application Insights telemetry context data model.
 ms.topic: conceptual
 ms.date: 05/15/2017
 ms.reviewer: osrosado
 ---
 
 # Telemetry context: Application Insights data model
 
-Every telemetry item may have a strongly typed context field. Every field enables a specific monitoring scenario. Use the custom properties collection to store custom or application-specific contextual information.
-
+Every telemetry item might have a strongly typed context field. Every field enables a specific monitoring scenario. Use the custom properties collection to store custom or application-specific contextual information.
 
 ## Application version
 
-Information in the application context fields is always about the application that is sending the telemetry. Application version is used to analyze trend changes in the application behavior and its correlation to the deployments.
-
-Max length: 1024
+Information in the application context fields is always about the application that's sending the telemetry. The application version is used to analyze trend changes in the application behavior and its correlation to the deployments.
 
+Maximum length: 1,024
 
 ## Client IP address
 
-The IP address of the client device. IPv4 and IPv6 are supported. When telemetry is sent from a service, the location context is about the user that initiated the operation in the service. Application Insights extract the geo-location information from the client IP and then truncate it. So client IP by itself can't be used as end-user identifiable information. 
-
-Max length: 46
+This field is the IP address of the client device. IPv4 and IPv6 are supported. When telemetry is sent from a service, the location context is about the user that initiated the operation in the service. Application Insights extract the geo-location information from the client IP and then truncate it. The client IP by itself can't be used as user identifiable information.
 
+Maximum length: 46
 
 ## Device type
 
-Originally this field was used to indicate the type of the device the end user of the application is using. Today used primarily to distinguish JavaScript telemetry with the device type 'Browser' from server-side telemetry with the device type 'PC'.
-
-Max length: 64
+Originally, this field was used to indicate the type of the device the user of the application is using. Today it's used primarily to distinguish JavaScript telemetry with the device type `Browser` from server-side telemetry with the device type `PC`.
 
+Maximum length: 64
 
 ## Operation ID
 
-A unique identifier of the root operation. This identifier allows grouping telemetry across multiple components. See [telemetry correlation](./correlation.md) for details. The operation ID is created by either a request or a page view. All other telemetry sets this field to the value for the containing request or page view. 
-
-Max length: 128
+This field is the unique identifier of the root operation. This identifier allows grouping telemetry across multiple components. For more information, see [Telemetry correlation](./correlation.md). The operation ID is created by either a request or a page view. All other telemetry sets this field to the value for the containing request or page view.
 
+Maximum length: 128
 
 ## Parent operation ID
 
-The unique identifier of the telemetry item's immediate parent. See [telemetry correlation](./correlation.md) for details.
-
-Max length: 128
+This field is the unique identifier of the telemetry item's immediate parent. For more information, see [Telemetry correlation](./correlation.md).
 
+Maximum length: 128
 
 ## Operation name
 
-The name (group) of the operation. The operation name is created by either a request or a page view. All other telemetry items set this field to the value for the containing request or page view. Operation name is used for finding all the telemetry items for a group of operations (for example 'GET Home/Index'). This context property is used to answer questions like "what are the typical exceptions thrown on this page."
-
-Max length: 1024
+This field is the name (group) of the operation. The operation name is created by either a request or a page view. All other telemetry items set this field to the value for the containing request or page view. The operation name is used for finding all the telemetry items for a group of operations (for example, `GET Home/Index`). This context property is used to answer questions like What are the typical exceptions thrown on this page?
 
+Maximum length: 1,024
 
 ## Synthetic source of the operation
 
-Name of synthetic source. Some telemetry from the application may represent synthetic traffic. It may be web crawler indexing the web site, site availability tests, or traces from diagnostic libraries like Application Insights SDK itself.
-
-Max length: 1024
+This field is the name of the synthetic source. Some telemetry from the application might represent synthetic traffic. It might be the web crawler indexing the website, site availability tests, or traces from diagnostic libraries like the Application Insights SDK itself.
 
+Maximum length: 1,024
 
 ## Session ID
 
-Session ID - the instance of the user's interaction with the app. Information in the session context fields is always about the end user. When telemetry is sent from a service, the session context is about the user that initiated the operation in the service.
-
-Max length: 64
+Session ID is the instance of the user's interaction with the app. Information in the session context fields is always about the user. When telemetry is sent from a service, the session context is about the user who initiated the operation in the service.
 
+Maximum length: 64
 
 ## Anonymous user ID
 
-Anonymous user ID. (User.Id) Represents the end user of the application. When telemetry is sent from a service, the user context is about the user that initiated the operation in the service.
+Anonymous user ID (User.Id) represents the user of the application. When telemetry is sent from a service, the user context is about the user who initiated the operation in the service.
 
-[Sampling](./sampling.md) is one of the techniques to minimize the amount of collected telemetry. Sampling algorithm attempts to either sample in or out all the correlated telemetry. Anonymous user ID is used for sampling score generation. So anonymous user ID should be a random enough value. 
+[Sampling](./sampling.md) is one of the techniques to minimize the amount of collected telemetry. A sampling algorithm attempts to either sample in or out all the correlated telemetry. An anonymous user ID is used for sampling score generation, so an anonymous user ID should be a random enough value.
 
 > [!NOTE]
-> The count of anonymous user IDs is not the same as the number of unique application users. The count of anonymous user IDs is typically higher because each time the user opens your app on a different device or browser, or cleans up browser cookies, a new unique anonymous user id is allocated. This calculation may result in counting the same physical users multiple times.
+> The count of anonymous user IDs isn't the same as the number of unique application users. The count of anonymous user IDs is typically higher because each time the user opens your app on a different device or browser, or cleans up browser cookies, a new unique anonymous user ID is allocated. This calculation might result in counting the same physical users multiple times.
 
 User IDs can be cross referenced with session IDs to provide unique telemetry dimensions and establish user activity over a session duration.
 
-Using anonymous user ID to store user name is a misuse of the field. Use Authenticated user ID.
-
-Max length: 128
+Using an anonymous user ID to store a username is a misuse of the field. Use an authenticated user ID.
 
+Maximum length: 128
 
 ## Authenticated user ID
 
-Authenticated user ID. The opposite of anonymous user ID, this field represents the user with a friendly name. This ID is only collected by default with the ASP.NET Framework SDK's [`AuthenticatedUserIdTelemetryInitializer`](https://github.com/microsoft/ApplicationInsights-dotnet/blob/develop/WEB/Src/Web/Web/AuthenticatedUserIdTelemetryInitializer.cs).  
+An authenticated user ID is the opposite of an anonymous user ID. This field represents the user with a friendly name. This ID is only collected by default with the ASP.NET Framework SDK's [`AuthenticatedUserIdTelemetryInitializer`](https://github.com/microsoft/ApplicationInsights-dotnet/blob/develop/WEB/Src/Web/Web/AuthenticatedUserIdTelemetryInitializer.cs).
 
-Use the Application Insights SDK to initialize the Authenticated User ID with a value identifying the user persistently across browsers and devices. In this way, all telemetry items are attributed to that unique ID. This ID enables querying for all telemetry collected for a specific user (subject to [sampling configurations](./sampling.md) and [telemetry filtering](./api-filtering-sampling.md)). 
+Use the Application Insights SDK to initialize the authenticated user ID with a value that identifies the user persistently across browsers and devices. In this way, all telemetry items are attributed to that unique ID. This ID enables querying for all telemetry collected for a specific user (subject to [sampling configurations](./sampling.md) and [telemetry filtering](./api-filtering-sampling.md)).
 
 User IDs can be cross referenced with session IDs to provide unique telemetry dimensions and establish user activity over a session duration.
 
-Max length: 1024
-
+Maximum length: 1,024
 
 ## Account ID
 
-The account ID, in multi-tenant applications, is the tenant account ID or name that the user is acting with. It's used for more user segmentation when user ID and authenticated user ID aren't sufficient. For example, a subscription ID for Azure portal or the blog name for a blogging platform.
-
-Max length: 1024
+The account ID, in multi-tenant applications, is the tenant account ID or name that the user is acting with. It's used for more user segmentation when a user ID and an authenticated user ID aren't sufficient. Examples might be a subscription ID for Azure portal or the blog name for a blogging platform.
 
+Maximum length: 1,024
 
 ## Cloud role
 
-Name of the role the application is a part of. Maps directly to the role name in Azure. Can also be used to distinguish micro services, which are part of a single application.
-
-Max length: 256
+This field is the name of the role of which the application is a part. It maps directly to the role name in Azure. It can also be used to distinguish micro services, which are part of a single application.
 
+Maximum length: 256
 
 ## Cloud role instance
 
-Name of the instance where the application is running. Computer name for on-premises, instance name for Azure.
-
-Max length: 256
+This field is the name of the instance where the application is running. For example, it's the computer name for on-premises or the instance name for Azure.
 
+Maximum length: 256
 
 ## Internal: SDK version
 
-SDK version. See [this article](https://github.com/MohanGsk/ApplicationInsights-Home/blob/master/EndpointSpecs/SDK-VERSIONS.md) for information.
-
-Max length: 64
+For more information, see this [SDK version article](https://github.com/MohanGsk/ApplicationInsights-Home/blob/master/EndpointSpecs/SDK-VERSIONS.md).
 
+Maximum length: 64
 
 ## Internal: Node name
 
 This field represents the node name used for billing purposes. Use it to override the standard detection of nodes.
 
-Max length: 256
-
+Maximum length: 256
 
 ## Next steps
 
 - Learn how to [extend and filter telemetry](./api-filtering-sampling.md).
-- See [data model](data-model.md) for Application Insights types and data model.
-- Check out standard context properties collection [configuration](./configuration-with-applicationinsights-config.md#telemetry-initializers-aspnet).
-
+- See [Application Insights telemetry data model](data-model.md) for Application Insights types and data model.
+- Check out standard context properties collection [configuration](./configuration-with-applicationinsights-config.md#telemetry-initializers-aspnet).