Merge branch 'master' of https://github.com/MicrosoftDocs/azure-docs-pr into RegionCorrection

Author: roygara

articles/azure-monitor/agents/azure-monitor-agent-overview.md

@@ -136,18 +136,28 @@ The Azure Monitor agent extensions for Windows and Linux can communicate either
 
 	| Parameter | Value |
 	|:---|:---|
-	| SettingString | A JSON object from the preceding flowchart converted to a string. Skip if not applicable. An example is {"proxy":{"mode":"application","address":"http://[address]:[port]","auth": false}}. |
-	| ProtectedSettingString | A JSON object from the preceding flowchart converted to a string. Skip if not applicable. An example is {"proxy":{"username": "[username]","password": "[password]"}}. |
+	| Setting | A JSON object from the preceding flowchart converted to a string. Skip if not applicable. An example is {"proxy":{"mode":"application","address":"http://[address]:[port]","auth": false}}. |
+	| ProtectedSetting | A JSON object from the preceding flowchart converted to a string. Skip if not applicable. An example is {"proxy":{"username": "[username]","password": "[password]"}}. |
 
 
-# [Windows](#tab/PowerShellWindows)
+# [Windows VM](#tab/PowerShellWindows)
 ```powershell
-Set-AzVMExtension -ExtensionName AzureMonitorWindowsAgent -ExtensionType AzureMonitorWindowsAgent -Publisher Microsoft.Azure.Monitor -ResourceGroupName <resource-group-name> -VMName <virtual-machine-name> -Location <location> -TypeHandlerVersion 1.0 -SettingString <settingString> -ProtectedSettingString <protectedSettingString>
+Set-AzVMExtension -ExtensionName AzureMonitorWindowsAgent -ExtensionType AzureMonitorWindowsAgent -Publisher Microsoft.Azure.Monitor -ResourceGroupName <resource-group-name> -VMName <virtual-machine-name> -Location <location> -TypeHandlerVersion 1.0 -Setting <settingString> -ProtectedSetting <protectedSettingString>
 ```
 
-# [Linux](#tab/PowerShellLinux)
+# [Linux VM](#tab/PowerShellLinux)
 ```powershell
-Set-AzVMExtension -ExtensionName AzureMonitorLinuxAgent -ExtensionType AzureMonitorLinuxAgent -Publisher Microsoft.Azure.Monitor -ResourceGroupName <resource-group-name> -VMName <virtual-machine-name> -Location <location> -TypeHandlerVersion 1.5 -SettingString <settingString> -ProtectedSettingString <protectedSettingString>
+Set-AzVMExtension -ExtensionName AzureMonitorLinuxAgent -ExtensionType AzureMonitorLinuxAgent -Publisher Microsoft.Azure.Monitor -ResourceGroupName <resource-group-name> -VMName <virtual-machine-name> -Location <location> -TypeHandlerVersion 1.5 -Setting <settingString> -ProtectedSetting <protectedSettingString>
+```
+
+# [Windows Arc enabled server](#tab/PowerShellWindowsArc)
+```powershell
+New-AzConnectedMachineExtension -Name AzureMonitorWindowsAgent -ExtensionType AzureMonitorWindowsAgent -Publisher Microsoft.Azure.Monitor -ResourceGroupName <resource-group-name> -MachineName <arc-server-name> -Location <arc-server-location> -Setting <settingString> -ProtectedSetting <protectedSettingString>
+```
+
+# [Linux Arc enabled server](#tab/PowerShellLinuxArc)
+```powershell
+New-AzConnectedMachineExtension -Name AzureMonitorLinuxAgent -ExtensionType AzureMonitorLinuxAgent -Publisher Microsoft.Azure.Monitor -ResourceGroupName <resource-group-name> -MachineName <arc-server-name> -Location <arc-server-location> -Setting <settingString> -ProtectedSetting <protectedSettingString>
 ```
 
 ---

articles/azure-monitor/essentials/diagnostic-settings.md

@@ -1,11 +1,11 @@
 ---
 title: Create diagnostic settings to send platform logs and metrics to different destinations
 description: Send Azure Monitor platform metrics and logs to Azure Monitor Logs, Azure storage, or Azure Event Hubs using a diagnostic setting.
-author: bwren
-ms.author: bwren
+author: rboucher
+ms.author: robb
 services: azure-monitor
 ms.topic: conceptual
-ms.date: 06/09/2021
+ms.date: 11/02/2021
 ---
 
 # Create diagnostic settings to send platform logs and metrics to different destinations
@@ -42,6 +42,7 @@ Platform logs and metrics can be sent to the destinations in the following table
 | [Log Analytics workspace](../logs/design-logs-deployment.md) | Sending logs and metrics to a Log Analytics workspace allows you to analyze them with other monitoring data collected by Azure Monitor using powerful log queries and also to leverage other Azure Monitor features such as alerts and visualizations. |
 | [Event hubs](../../event-hubs/index.yml) | Sending logs and metrics to Event Hubs allows you to stream data to external systems such as third-party SIEMs and other log analytics solutions.  |
 | [Azure storage account](../../storage/blobs/index.yml) | Archiving logs and metrics to an Azure storage account is useful for audit, static analysis, or backup. Compared to Azure Monitor Logs and a Log Analytics workspace, Azure storage is less expensive and logs can be kept there indefinitely.  |
+| [Azure Monitor partner integrations](/azure/partner-solutions/overview/)| Specialized integrations between Azure Monitor and other non-Microsoft monitoring platforms. |
 
 
 ### Destination requirements
@@ -118,12 +119,12 @@ You can configure diagnostic settings in the Azure portal either from the Azure
         ![Send to Storage](media/diagnostic-settings/storage-settings-new.png)
 
         > [!TIP]
-        > Consider setting the retention policy to 0 and manually deleting your data from storage using a scheduled job to avoid possible confusion in the future.
+        > Consider setting the retention policy to 0 and either use [Azure Storage Lifecycle Policy](/azure/storage/blobs/lifecycle-management-policy-configure) or delete your data from storage using a scheduled job. These strategies are likely to provide more consistent behavior. 
         >
-        > First, if you are using storage for archiving, you generally want your data around for more than 365 days. Second, if you choose a retention policy that is greater than 0, the expiration date is attached to the logs at the time of storage. You can't change the date for those logs once stored.
-        >
-        > For example, if you set the retention policy for *WorkflowRuntime* to 180 days and then 24 hours later set it to 365 days, the logs stored during those first 24 hours will be automatically deleted after 180 days, while all subsequent logs of that type will be automatically deleted after 365 days. Changing the retention policy later doesn't make the first 24 hours of logs stay around for 365 days.
-
+        > First, if you are using storage for archiving, you generally want your data around for more than 365 days. Second, if you choose a retention policy that is greater than 0, the expiration date is attached to the logs at the time of storage. You can't change the date for those logs once stored. For example, if you set the retention policy for *WorkflowRuntime* to 180 days and then 24 hours later set it to 365 days, the logs stored during those first 24 hours will be automatically deleted after 180 days, while all subsequent logs of that type will be automatically deleted after 365 days. Changing the retention policy later doesn't make the first 24 hours of logs stay around for 365 days.
+    
+     1. **Partner integration** - You must first install a partner integration into your subscription. For more information, see [Azure Monitor Partner integrations](/azure/partner-solutions/overview/). 
+    
 6. Click **Save**.
 
 After a few moments, the new setting appears in your list of settings for this resource, and logs are streamed to the specified destinations as new event data is generated. It may take up to 15 minutes between when an event is emitted and when it [appears in a Log Analytics workspace](../logs/data-ingestion-time.md).

articles/azure-monitor/monitor-reference.md

@@ -4,7 +4,7 @@ description: Reference of all services and other resources monitored by Azure Mo
 ms.topic: conceptual
 author: rboucher
 ms.author: robb
-ms.date: 10/15/2021
+ms.date: 11/02/2021
 
 ---
 
@@ -77,7 +77,7 @@ The other services and older monitoring solutions in the following table store t
 |:---|:---|
 | [ITSM](alerts/itsmc-overview.md) | The IT Service Management Connector (ITSMC) allows you to connect Azure and a supported IT Service Management (ITSM) product/service.  |
 | [Azure Monitor Partners](/azure/azure-monitor/partners/) | A list of partners that integrate with Azure Monitor in some form | 
-| [Datadog Integration](/azure/partner-solutions/datadog/overview) | A specialized integration between Azure Monitor and Datadog for companies who have already built their monitoring infrastructure on Datadog |
+| [Azure Monitor Partner integrations](/azure/partner-solutions/overview/)| Specialized integrations between Azure Monitor and other non-Microsoft monitoring platforms if you've already built on them.  Examples include Datadog and Elastic|
 
 
 ## Resources outside of Azure

articles/cognitive-services/Speech-Service/releasenotes.md

@@ -22,11 +22,11 @@ ms.custom: ignite-fall-2021
 
 #### Highlights 
 
-- Speaker Recognition service is generally available (GA) now. Speech SDK APIs are available on C++, C#, Java and Javascript. With Speaker recognition you can accurately verify and identify speakers by their unique voice characteristics. See the [document](speaker-recognition-overview.md) for more details. 
+- Speaker Recognition service is generally available (GA) now. Speech SDK APIs are available on C++, C#, Java and Javascript. With Speaker recognition you can accurately verify and identify speakers by their unique voice characteristics. See the [documentation](speaker-recognition-overview.md) for more details. 
 
-- Ubuntu 16.04 reached end of life back in April of 2021. In conjunction with Azure DevOps and Github we have dropped support for Ubuntu 16.04 in this release.  Please migrate Ubuntu 16.04 workflows to Ubuntu 18.04 or newer.   
+- We have dropped support for Ubuntu 16.04 in conjunction with Azure DevOps and Github. Ubuntu 16.04 reached end of life back in April of 2021. Please migrate Ubuntu 16.04 workflows to Ubuntu 18.04 or newer.   
 
-- OpenSSL linking in Linux binaries changed to dynamic. Linux binary size has been reduced about 50%. 
+- OpenSSL linking in Linux binaries changed to dynamic. Linux binary size has been reduced by about 50%. 
 
 - Mac M1 ARM based silicon support added. 
 
@@ -38,31 +38,31 @@ ms.custom: ignite-fall-2021
 
 - **C++**: New APIs for intent recognition to facilitate more advanced pattern matching. This includes List and Prebuilt Integer entities as well as support for grouping intents and entities as models (Documentation, updates, and samples are under development and will be published in the near future). 
 
-- **Mac**: Support for ARM64 (M1) based silicon for Cocoapod, Python, Java and NuGet packages [Related customer issue](https://github.com/Azure-Samples/cognitive-services-speech-sdk/issues/1244).
+- **Mac**: Support for ARM64 (M1) based silicon for Cocoapod, Python, Java, and NuGet packages related to [GitHub issue 1244](https://github.com/Azure-Samples/cognitive-services-speech-sdk/issues/1244).
 
-- **iOS/Mac**: iOS and MacOS binaries are now packaged into xcframework [Related customer issue](https://github.com/Azure-Samples/cognitive-services-speech-sdk/issues/919).
+- **iOS/Mac**: iOS and MacOS binaries are now packaged into xcframework related to [GitHub issue 919](https://github.com/Azure-Samples/cognitive-services-speech-sdk/issues/919).
 
-- **iOS/Mac**: Support for Mac catalyst [Related customer issue](https://github.com/Azure-Samples/cognitive-services-speech-sdk/issues/1171). 
+- **iOS/Mac**: Support for Mac catalyst related to [GitHub issue 1171](https://github.com/Azure-Samples/cognitive-services-speech-sdk/issues/1171). 
 
 - **Linux**: New tar package added for CentOS7 [About the Speech SDK](speech-sdk.md).
 
 - **Javascript**: VoiceProfile & SpeakerRecognizer APIs made async/awaitable. 
 
 - **Javascript**: Support added for US government Azure regions. 
 
-- **Windows**: Support playback on Universal Windows Platform (UWP). 
+- **Windows**: Support added for playback on Universal Windows Platform (UWP). 
 
 
 
 #### Bug fixes 
 
-- **Android**: OpenSSL security update (updated to 1.1.1l version) for Android packages. 
+- **Android**: OpenSSL security update (updated to version 1.1.1l) for Android packages. 
 
-- **Python**: Fix bug selecting speaker device on Python fails. 
+- **Python**: Resolved bug where selecting speaker device on Python fails. 
 
 - **Core**: Automatically reconnect when a connection attempt fails. 
 
-- **iOS**: Audio compression disabled on iOS packages due instability and bitcode build problems when using Gstreamer. Details [here](https://github.com/Azure-Samples/cognitive-services-speech-sdk/issues/1209).
+- **iOS**: Audio compression disabled on iOS packages due instability and bitcode build problems when using Gstreamer. Details are available via [GitHub issue 1209](https://github.com/Azure-Samples/cognitive-services-speech-sdk/issues/1209).
 
 
 

articles/communication-services/concepts/interop/calling-chat.md

@@ -50,11 +50,11 @@ const call = callAgent.startCall([teamsCallee]);
 **Limitations and known issues**
 - Teams users must be in "TeamsOnly" mode. Skype for Business users can't receive 1:1 calls from Communication Services users.
 - Escalation to a group call isn't supported.
-- Communication Services users are not displayed correctly in the Call history
 - Communication Services call recording isn't available for 1:1 calls.
 - Advanced call routing capabilities such as call forwarding, group call pickup, simulring, and voice mail are not supported.
 - Teams users can't set Communication Services users as forwarding/transfer targets.
-- LyncIpPhone fork is not supported.
+- There are a number of features in the Teams client that do not work as expected during 1:1 calls with Communication Services users.
+- Third party [devices for Teams](/MicrosoftTeams/devices/teams-ip-phones) are not supported.
 
 ## Chat
 With the Chat SDK, Communication Services users or endpoints can start 1:n chat with Teams users, identified by their Azure Active Directory (AAD) object ID. You can easily modify an existing application that creates chats with other Communication Services users, to instead create chats with Teams users:

articles/container-apps/scale-app.md

@@ -161,7 +161,7 @@ The following example shows how to create a CPU scaling rule.
 
 ## Memory
 
-CPU scaling allows your app to scale in or out depending on how much the CPU is being used. CPU scaling doesn't allow your container app to scale to 0. For more information regarding this scaler, see [KEDA Memory scaler](https://keda.sh/docs/scalers/memory/).
+Memory scaling allows your app to scale in or out depending on how much of the memory is being used. Memory scaling doesn't allow your container app to scale to 0. For more information regarding this scaler, see [KEDA Memory scaler](https://keda.sh/docs/scalers/memory/).
 
 The following example shows how to create a memory scaling rule.
 

articles/mysql/flexible-server/connect-csharp.md

@@ -26,7 +26,7 @@ For this quickstart you need:
 - Create an Azure Database for MySQL Flexible server using [Azure portal](./quickstart-create-server-portal.md) <br/> or [Azure CLI](./quickstart-create-server-cli.md) if you do not have one.
 - Based on whether you are using public or private access, complete **ONE** of the actions below to enable connectivity.
 - [Create a database and non-admin user](../howto-create-users.md)
-- Install the [.NET SDK for your platform](/dotnet/core/install/windows?tabs=net50) (Windows, Ubuntu Linux, or macOS) for your platform.
+- Install the [.NET SDK for your platform](https://dotnet.microsoft.com/download) (Windows, Ubuntu Linux, or macOS) for your platform.
 
 [Having issues? Let us know](https://github.com/MicrosoftDocs/azure-docs/issues)
 

articles/postgresql/connect-csharp.md

@@ -27,7 +27,7 @@ For this quickstart you need:
   | **Configure Service Endpoint** | Public | [Portal](./howto-manage-vnet-using-portal.md) <br/> [CLI](./howto-manage-vnet-using-cli.md)|
   | **Configure private link** | Private | [Portal](./howto-configure-privatelink-portal.md) <br/> [CLI](./howto-configure-privatelink-cli.md) |
 
-- Install the [.NET SDK for your platform](/dotnet/core/install/windows?tabs=net50) (Windows, Ubuntu Linux, or macOS) for your platform.
+- Install the [.NET SDK for your platform](https://dotnet.microsoft.com/download) (Windows, Ubuntu Linux, or macOS) for your platform.
 - Install [Visual Studio](https://www.visualstudio.com/downloads/) to build your project.
 - Install [Npgsql](https://www.nuget.org/packages/Npgsql/) NuGet package in Visual Studio.
 

articles/postgresql/flexible-server/connect-csharp.md

@@ -20,7 +20,7 @@ For this quickstart you need:
 - An Azure account with an active subscription. [Create an account for free](https://azure.microsoft.com/free).
 - Create an Azure Database for PostgreSQL Flexible server using [Azure portal](./quickstart-create-server-portal.md) <br/> or [Azure CLI](./quickstart-create-server-cli.md) if you do not have one.
 - Use the empty *postgres* database available on the server or create a [new database](./quickstart-create-server-portal.md#connect-to-the-postgresql-database-using-psql).
-- Install the [.NET SDK for your platform](/dotnet/core/install/windows?tabs=net50) (Windows, Ubuntu Linux, or macOS) for your platform.
+- Install the [.NET SDK for your platform](https://dotnet.microsoft.com/download) (Windows, Ubuntu Linux, or macOS) for your platform.
 - Install [Visual Studio](https://www.visualstudio.com/downloads/) to build your project.
 - Install [Npgsql](https://www.nuget.org/packages/Npgsql/) NuGet package in Visual Studio.
 

articles/purview/.openpublishing.redirection.purview.json

@@ -44,6 +44,16 @@
         "source_path_from_root": "/articles/purview/file-extension-insights.md",
         "redirect_url": "/azure/purview/asset-insights",
         "redirect_document_id": true
+      },
+      {
+        "source_path_from_root": "/articles/purview/concept-data-policies.md",
+        "redirect_url": "/azure/purview/how-to-access-policies-storage",
+        "redirect_document_id": true
+      },
+      {
+        "source_path_from_root": "/articles/purview/concept-self-service.md",
+        "redirect_url": "/azure/purview/overview",
+        "redirect_document_id": true
       }
 ]
 }