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

Author: yelevin

articles/azure-monitor/agents/azure-monitor-agent-migration-tools.md

@@ -12,7 +12,7 @@ ms.custom: devx-track-azurepowershell, devx-track-azurecli
 
 ---
 
-# Migration tools for Log Analytics Agent to Azure Monitor Agent
+# Tools for migrating from Log Analytics Agent to Azure Monitor Agent 
 
 Azure Monitor Agent (AMA) replaces the Log Analytics Agent (MMA/OMS) for Windows and Linux virtual machines, scale sets, and on premise and Arc-enabled servers. The [benefits of migrating to Azure Monitor Agent](../agents/azure-monitor-agent-migration.md) include enhanced security, cost-effectiveness, performance, manageability and reliability. This article explains how to use the AMA Migration Helper and DCR Config Generator tools to help automate and track the migration from Log Analytics Agent to Azure Monitor Agent.
 

articles/azure-monitor/alerts/itsmc-dashboard-errors.md

@@ -84,7 +84,7 @@ The following sections describe common errors that appear in the connector statu
 **Cause**: Such an error appears in either of these situations:
 
 * A newly created ITSM Connector instance has yet to finish the initial sync.
-* The connector was not defined correctly.
+* The connector wasn't defined correctly.
 
 **Resolution**: 
 
@@ -93,17 +93,19 @@ The following sections describe common errors that appear in the connector statu
 
 
 ## IP restrictions
-**Error**: "Failed to add ITSM Connection named "XXX" due to Bad Request. Error: Bad request. Invalid parameters provided for connection. Http Exception: Status Code Forbidden."
+**Error**: 
+* "Failed to add ITSM Connection named "XXX" due to Bad Request. Error: Bad request. Invalid parameters provided for connection. Http Exception: Status Code Forbidden."
+* "Failed to update ITSM Connection credentials"
 
-**Cause**: The IP address of ITSM application is not allow ITSM connections from partners ITSM tools.
+**Cause**: The IP address of ITSM application isn't allow ITSM connections from partners ITSM tools.
 
-**Resolution**: In order to list the ITSM IP addresses in order to allow ITSM connections from partners ITSM tools, we recommend the to list the whole public IP range of Azure region where their LogAnalytics workspace belongs. [details here](https://www.microsoft.com/download/details.aspx?id=56519) For regions EUS/WEU/EUS2/WUS2/US South Central the customer can list ActionGroup network tag only.
+**Resolution**: In order to list the ITSM IP addresses to allow ITSM connections from partners ITSM tools, we recommend the to list the whole public IP range of Azure region where their LogAnalytics workspace belongs. [details here](https://www.microsoft.com/download/details.aspx?id=56519) For regions EUS/WEU/EUS2/WUS2/US South Central the customer can list ActionGroup network tag only.
 
 
 ## Authentication
 **Error**: "User Not Authenticated"
 
-**Cause**: There can be one of 2 options either the token need to be refreshed or there is missing integration user rights.
+**Cause**: There can be one of two options either the token need to be refreshed or there's missing integration user rights.
 
 **Resolution**:If the integration worked for you in the past, it might be that the refresh token has expired. Then sync ITSMC to generate a new refresh token, as explained in [How to manually fix sync problems](./itsmc-resync-servicenow.md). If it never worked, it might be missing integration user rights, Please check it [here ](./itsmc-connections-servicenow.md#install-the-user-app-and-create-the-user-role)
 

articles/defender-for-iot/organizations/media/how-to-manage-sensors-on-the-cloud/prepare-to-update.png

@@ -19,14 +19,28 @@ For Site Recovery components, we support N-4 versions, where N is the latest rel
 
 **Update** |  **Unified Setup** | **Configuration server/Replication appliance** | **Mobility service agent** | **Site Recovery Provider** | **Recovery Services agent**
 --- | --- | --- | --- | --- | ---
+[Rollup 63](https://support.microsoft.com/topic/update-rollup-63-for-azure-site-recovery-992e63af-aa94-4ea6-8d1b-2dd89a9cc70b) | 9.50.6419.1 | 5.1.7626.0 | 9.50.6419.1 | 5.1.7626.0 | 2.0.9249.0
 [Rollup 62](https://support.microsoft.com/topic/update-rollup-62-for-azure-site-recovery-e7aff36f-b6ad-4705-901c-f662c00c402b) | 9.49.6395.1 | 5.1.7418.0 | 9.49.6395.1 | 5.1.7418.0 | 2.0.9248.0
 [Rollup 61](https://support.microsoft.com/topic/update-rollup-61-for-azure-site-recovery-kb5012960-a1cc029b-03ad-446f-9365-a00b41025d39) | 9.48.6349.1 | 5.1.7387.0 | 9.48.6349.1 | 5.1.7387.0 | 2.0.9245.0
 [Rollup 60](https://support.microsoft.com/topic/883a93a7-57df-4b26-a1c4-847efb34a9e8) | 9.47.6219.1 | 5.1.7127.0 | 9.47.6219.1 | 5.1.7127.0 | 2.0.9241.0
 [Rollup 59](https://support.microsoft.com/topic/update-rollup-59-for-azure-site-recovery-kb5008707-66a65377-862b-4a4c-9882-fd74bdc7a81e) | 9.46.6149.1 | 5.1.7029.0 | 9.46.6149.1 | 5.1.7030.0 | 2.0.9239.0
-[Rollup 58](https://support.microsoft.com/topic/update-rollup-58-for-azure-site-recovery-kb5007075-37ba21c3-47d9-4ea9-9130-a7d64f517d5d) | 9.45.6096.1 | 5.1.6952.0 | 9.45.6096.1 | 5.1.6952.0 | 2.0.9237.0
 
 [Learn more](service-updates-how-to.md) about update installation and support.
 
+## Updates (August 2022)
+
+### Update Rollup 63
+
+[Update rollup 63](https://support.microsoft.com/topic/update-rollup-63-for-azure-site-recovery-992e63af-aa94-4ea6-8d1b-2dd89a9cc70b) provides the following updates:
+
+**Update** | **Details**
+--- | ---
+**Providers and agents** | Updates to Site Recovery agents and providers as detailed in the rollup KB article.
+**Issue fixes/improvements** | A number of fixes and improvement as detailed in the rollup KB article.
+**Azure VM disaster recovery** | Added support for Oracle Linux 8.6 Linux distro.
+**VMware VM/physical disaster recovery to Azure** | Added support for Oracle Linux 8.6 Linux distro.<br/><br/> Introduced the migration capability to move existing replications from classic to modernized experience for disaster recovery of VMware virtual machines, enabled using Azure Site Recovery. [Learn more](move-from-classic-to-modernized-vmware-disaster-recovery.md).
+
+
 ## Updates (July 2022)
 
 ### Update Rollup 62

articles/defender-for-iot/organizations/media/how-to-manage-sensors-on-the-cloud/sensor-settings-subnet-setting.png

@@ -4,7 +4,7 @@ description: Configure your deployment control plane for the SAP deployment auto
 author: kimforss
 ms.author: kimforss
 ms.reviewer: kimforss
-ms.date: 11/17/2021
+ms.date: 8/8/2022
 ms.topic: conceptual
 ms.service: virtual-machines-sap
 ---

articles/defender-for-iot/organizations/media/how-to-manage-sensors-on-the-cloud/sensor-settings.png

@@ -1,20 +1,23 @@
 ---
-title: Configure a Deployer UX Web Application for SAP Deployment Automation Framework
+title: Configure a Deployer Web Application for SAP Deployment Automation Framework
 description: Configure a web app as a part of the control plane to help creating and deploying SAP workload zones and systems on Azure.
 author: wsheehan
 ms.author: wsheehan
 ms.reviewer: wsheehan
-ms.date: 06/21/2022
+ms.date: 08/1/2022
 ms.topic: conceptual
 ms.service: virtual-machines-sap
 ---
 
-# Configure the Control Plane UX Web Application
+# Configure the Control Plane Web Application
 
-As a part of the SAP automation framework control plane, you can optionally create an interactive web application that will assist you in creating the required configuration files and deploying SAP workload zones and systems using Azure DevOps Pipelines.
+As a part of the SAP automation framework control plane, you can optionally create an interactive web application that will assist you in creating the required configuration files and deploying SAP workload zones and systems using Azure Pipelines.
 
 :::image type="content" source="./media/automation-deployment-framework/webapp-front-page.png" alt-text="Web app front page":::
 
+> [!IMPORTANT]
+> Control Plane Web Application is currently in PREVIEW and not yet available in the main branch.
+
 ## Create an app registration 
 
 If you would like to use the web app, you must first create an app registration for authentication purposes. Open the Azure Cloud Shell and execute the following commands:
@@ -57,7 +60,7 @@ rm ./manifest.json
 ```
 ---
 
-## Deploy via Azure DevOps (pipelines)
+## Deploy via Azure Pipelines
 
 For full instructions on setting up the web app using Azure DevOps, see [Use SAP Deployment Automation Framework from Azure DevOps Services](automation-configure-devops.md)
 
@@ -91,7 +94,7 @@ For full instructions on setting up the web app using the Azure CLI, see [Deploy
 
 ## Using the web app
 
-The web app allows you to create SAP workload zone objects and system infrastructure objects. These are essentially another representation of the Terraform configuration file.
+The web app allows you to create SAP workload zone objects and system infrastructure objects. These objects are essentially another representation of the Terraform configuration file.
 If deploying using Azure Pipelines, you have ability to deploy these workload zones and system infrastructures right from the web app.
 If deploying using the Azure CLI, you can download the parameter file for any landscape or system object you create, and use that in your command line deployments.
 

articles/site-recovery/site-recovery-whats-new.md

@@ -281,7 +281,10 @@ cd sap-automation/deploy/scripts
 The script will install Terraform and Ansible and configure the deployer.
 
 
-## Deploy the web app software
+## Deploy the Control Plane Web Application
+
+> [!IMPORTANT]
+> Control Plane Web Application is currently in PREVIEW and not yet available in the main branch.
    
 If you would like to use the web app, follow the steps below. If not, ignore this section.