Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into WI-86431-plan-image-fixes

Author: ElazarK

.openpublishing.redirection.azure-monitor.json

@@ -6135,7 +6135,12 @@
             "source_path_from_root": "/articles/azure-monitor/app/data-model-context.md",
             "redirect_url": "/azure/azure-monitor/app/data-model-complete",
             "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-monitor/logs/dashboard-upgrade.md",
+            "redirect_url": "/azure/azure-monitor/visualize/tutorial-logs-dashboards",
+            "redirect_document_id": false
         }
-
+        
     ]
 }

articles/active-directory-b2c/configure-authentication-sample-react-spa-app.md

@@ -7,7 +7,7 @@ manager: CelesteDG
 ms.service: active-directory
 ms.workload: identity
 ms.topic: how-to
-ms.date: 11/17/2022
+ms.date: 04/24/2023
 ms.author: kengaderdus
 ms.subservice: B2C
 ms.custom: "b2c-support"
@@ -213,7 +213,7 @@ You're now ready to test the React scoped access to the API. In this step, run b
 
     ```console
     npm install && npm update
-    node index.js
+    npm start
     ```
 
     The console window displays the port number where the application is hosted:

articles/active-directory-b2c/enable-authentication-react-spa-app.md

@@ -7,7 +7,7 @@ manager: CelesteDG
 ms.service: active-directory
 ms.workload: identity
 ms.topic: reference
-ms.date: 07/07/2022
+ms.date: 04/24/2023
 ms.author: kengaderdus
 ms.subservice: B2C
 ms.custom: "b2c-support"
@@ -31,7 +31,6 @@ You can use an existing React app, or [create a new React App](https://reactjs.o
 ```
 npx create-react-app my-app
 cd my-app
-npm start
 ```
 
 ## Step 2: Install the dependencies

articles/active-directory/fundamentals/scenario-azure-first-sap-identity-integration.md

@@ -51,6 +51,9 @@ Based on these assumptions, we focus mostly on the products and services present
 > [!NOTE]
 > Most of the guidance here applies to [Azure Active Directory B2C](../../active-directory-b2c/overview.md) as well, but there are some important differences. See [Using Azure AD B2C as the Identity Provider](#using-azure-ad-b2c-as-the-identity-provider) for more information.
 
+> [!WARNING]
+> Be aware of the SAP SAML assertion limits and impact of the length of SAP Cloud Foundry role collection names and amount of collections proxied by groups in SAP Cloud Identity Service. See SAP note [2732890](https://launchpad.support.sap.com/?sap-support-cross-site-visitor-id=b73c7292f9a46d52#/notes/2732890) for more information. Exceeded limits result in authorization issues.
+
 ## Recommendations
 
 ### Summary

articles/active-directory/saas-apps/howspace-provisioning-tutorial.md

@@ -157,7 +157,7 @@ This section guides you through the steps to configure the Azure AD provisioning
    |Attribute|Type|Supported for filtering|Required by Howspace|
    |---|---|---|---|
    |displayName|String|✓|✓
-   |externalId|String||
+   |externalId|String||✓
    |members|Reference||
 
 1. To configure scoping filters, refer to the following instructions provided in the [Scoping filter tutorial](../app-provisioning/define-conditional-rules-for-provisioning-user-accounts.md).

articles/active-directory/saas-apps/sauce-labs-tutorial.md

@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: saas-app-tutorial
 ms.workload: identity
 ms.topic: how-to
-ms.date: 03/26/2023
+ms.date: 04/24/2023
 ms.author: jeedes
 
 ---
@@ -25,7 +25,7 @@ In this article, you learn how to integrate Sauce Labs with Azure Active Directo
 You configure and test Azure AD single sign-on for Sauce Labs in a test environment. Sauce Labs supports both **SP** and **IDP** initiated single sign-on and **Just In Time** user provisioning.
 
 > [!NOTE]
-> Identifier of this application is a fixed string value so only one instance can be configured in one tenant.
+> Identifier of this application is a fixed string value so only one instance can be configured in one tenant. If your company has more than one organization at Sauce Labs to be integrated with SAML SSO within a single Azure tenant, please refer to the following [documentation](https://docs.saucelabs.com/basics/sso/setting-up-sso-special-cases/#single-identity-provider-and-multiple-organizations-at-sauce-labs).
 
 ## Prerequisites
 
@@ -77,7 +77,7 @@ Complete the following steps to enable Azure AD single sign-on in the Azure port
 
 ## Configure Sauce Labs SSO
 
-To configure single sign-on on **Sauce Labs** side, you need to send the downloaded **Federation Metadata XML** and appropriate copied URLs from Azure portal to [Sauce Labs support team](mailto:[email protected]). They set this setting to have the SAML SSO connection set properly on both sides.
+To configure single sign-on on Sauce Labs side, please refer this [documentation](https://docs.saucelabs.com/basics/sso/setting-up-sso/#integrating-with-sauce-labs-service-provider) to set up SAML SSO connection properly on both sides. For any help or queries, please contact [Sauce Labs support team](mailto:[email protected]).
 
 ### Create Sauce Labs test user
 

articles/app-service/deploy-local-git.md

@@ -145,9 +145,6 @@ When you push commits to your App Service repository, App Service deploys the fi
 
     You can also change the `DEPLOYMENT_BRANCH` app setting in the Azure Portal, by selecting **Configuration** under **Settings** and adding a new Application Setting with a name of `DEPLOYMENT_BRANCH` and value of `main`.
 
-> [!NOTE]
-> You can also change the `DEPLOYMENT_BRANCH` using the Azure Portal interface, by selecting **Deployment Center** under **Deployment** and modifying the `Branch`.
-
 ## Troubleshoot deployment
 
 You may see the following common error messages when you use Git to publish to an App Service app in Azure:

articles/automation/update-management/overview.md

@@ -3,12 +3,16 @@ title: Azure Automation Update Management overview
 description: This article provides an overview of the Update Management feature that implements updates for your Windows and Linux machines.
 services: automation
 ms.subservice: update-management
-ms.date: 11/25/2022
+ms.date: 04/22/2023
 ms.topic: conceptual
 ---
 
 # Update Management overview
 
+> [!Important]
+> - Automation Update management relies on [Log Analytics agent](../../azure-monitor/agents/log-analytics-agent.md) (aka MMA agent), which is on a deprecation path and won’t be supported after **August 31, 2024**. [Update management center (Preview)](../../update-center/overview.md) (UMC) is the v2 version of Automation Update management and the future of Update management in Azure. UMC is a native service in Azure and does not rely on [Log Analytics agent](../../azure-monitor/agents/log-analytics-agent.md) or [Azure Monitor agent](../../azure-monitor/agents/agents-overview.md).
+> - Guidance for migrating from Automation Update management to Update management center will be provided to customers once the latter is Generally Available. For customers using Automation Update management, we recommend continuing to use the Log Analytics agent and **NOT** migrate to Azure Monitoring agent until migration guidance is provided for Update management or else Automation Update management will not work. Also, the Log Analytics agent would not be deprecated before moving all Automation Update management customers to UMC.
+
 You can use Update Management in Azure Automation to manage operating system updates for your Windows and Linux virtual machines in Azure, physical or VMs in on-premises environments, and in other cloud environments. You can quickly assess the status of available updates and manage the process of installing required updates for your machines reporting to Update Management. 
 
 As a service provider, you may have onboarded multiple customer tenants to [Azure Lighthouse](../../lighthouse/overview.md). Update Management can be used to assess and schedule update deployments to machines in multiple subscriptions in the same Azure Active Directory (Azure AD) tenant, or across tenants using Azure Lighthouse.

articles/azure-monitor/logs/dashboard-upgrade.md

@@ -12,9 +12,7 @@ ms.custom: references_regions
 Search jobs are asynchronous queries that fetch records into a new search table within your workspace for further analytics. The search job uses parallel processing and can run for hours across large datasets. This article describes how to create a search job and how to query its resulting data.
 
 > [!NOTE]
-> The search job feature is currently not supported for the following cases:
-> - Workspaces with [customer-managed keys](customer-managed-keys.md). 
-> - Workspaces in the China East 2 region.
+> The search job feature is currently not supported for workspaces with [customer-managed keys](customer-managed-keys.md). 
 
 ## When to use search jobs