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

Author: PatAltimore

.openpublishing.publish.config.json

@@ -990,6 +990,7 @@
     "articles/azure-netapp-files/.openpublishing.redirection.azure-netapp-files.json",
     "articles/azure-relay/.openpublishing.redirection.relay.json",
     "articles/communication-services/.openpublishing.redirection.communication-services.json",
+    "articles/confidential-computing/.openpublishing.redirection.json",
     "articles/cosmos-db/.openpublishing.redirection.cosmos-db.json",
     "articles/cost-management-billing/.openpublishing.redirection.cost-management-billing.json",
     "articles/data-catalog/.openpublishing.redirection.data-catalog.json",

.openpublishing.redirection.active-directory.json

@@ -30,11 +30,6 @@
       "redirect_url": "/azure/active-directory/saas-apps/tutorial-list",
       "redirect_document_id": false
     },
-    {
-      "source_path_from_root": "/articles/active-directory/saas-apps/netmotion-mobility-tutorial.md",
-      "redirect_url": "/azure/active-directory/saas-apps/tutorial-list",
-      "redirect_document_id": false
-    },
     {
       "source_path_from_root": "/articles/active-directory/fundamentals/whats-new-microsoft-365-government.md",
       "redirect_url": "/azure/active-directory/fundamentals/whats-new",
@@ -2043,7 +2038,7 @@
     {
       "source_path_from_root": "/articles/active-directory/conditional-access/conditional-access-for-exo-and-spo.md",
       "redirect_url": "/azure/active-directory/conditional-access/block-legacy-authentication",
-      "redirect_document_id": true
+      "redirect_document_id": false
     },
     {
       "source_path_from_root": "/articles/active-directory/conditional-access/baseline-protection.md",
@@ -4258,7 +4253,12 @@
     },
     {
       "source_path_from_root": "/articles/active-directory/conditional-access/concept-conditional-access-block-legacy-authentication.md",
-      "redirect_url": "/azure/active-directory/fundamentals/concept-fundamentals-block-legacy-authentication",
+      "redirect_url": "/azure/active-directory/conditional-access/block-legacy-authentication",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/active-directory/fundamentals/concept-fundamentals-block-legacy-authentication.md",
+      "redirect_url": "/azure/active-directory/conditional-access/block-legacy-authentication",
       "redirect_document_id": true
     },
     {
@@ -10837,11 +10837,20 @@
       "redirect_document_id": true
     },
     {
-      "source_path_from_root": "/articles/active-directory/manage-apps/recover-deleted-apps-faq.md",
+      "source_path": "articles/active-directory/manage-apps/recover-deleted-apps-faq.md",
       "redirect_url": "/azure/active-directory/manage-apps/delete-recover-faq",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/azure-percept/voice-control-your-inventory-then-visualize-with-power-bi-dashboard.md",
+      "redirect_url": "/azure/azure-percept/index",
+      "redirect_document_id": false
+    },
+    {
+      "source_path_from_root": "/articles/active-directory/fundamentals/keep-me-signed-in.md",
+      "redirect_url": "/azure/active-directory/fundamentals/customize-branding",
+      "redirect_document_id": false
     }
 
-
   ]
 }

.openpublishing.redirection.azure-monitor.json

@@ -510,6 +510,11 @@
             "source_path_from_root": "/articles/azure-monitor/logs/workspace-design-service-providers.md" ,
             "redirect_url": "/azure/azure-monitor/logs/workspace-design",
             "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-monitor/containers/container-insights-transition-hybrid.md" ,
+            "redirect_url": "/azure/azure-monitor/containers/container-insights-onboard",
+            "redirect_document_id": false
         }
     ]
 }

.openpublishing.redirection.azure-percept.json

@@ -4,6 +4,28 @@
             "source_path_from_root": "/articles/azure-percept/how-to-select-update-package.md",
             "redirect_url": "/azure/azure-percept/how-to-determine-your-update-strategy",
             "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-percept/deepstream/azure-percept-for-deepstream-overview.md",
+            "redirect_url": "/azure/azure-percept/index",
+            "redirect_document_id": false
+        },
+        { 
+            "source_path_from_root": "/articles/azure-percept/hci/azure-percept-on-azure-stack-hci-overview.md",
+            "redirect_url": "/azure/azure-percept/index",
+            "redirect_document_id": false   
+        },
+        {
+            "source_path_from_root": "/articles/azure-percept/studio/azure-percept-studio-overview.md",
+            "redirect_url": "/azure/azure-percept/index",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-percept/open-source/azure-percept-open-source-project-overview.md",
+            "redirect_url": "/azure/azure-percept/index",
+            "redirect_document_id": false
         }
+
     ]
 }
+

.openpublishing.redirection.json

@@ -1,10 +1,15 @@
 {
 	"redirections": [
-		{
+{
     "source_path":  "articles/api-management/zone-redundancy.md",
     "redirect_url":  "/azure/availability-zones/migrate-api-mgt",
     "redirect_document_id":  false
 },
+{
+    "source_path":  "articles/api-management/developer-portal-implement-widgets.md",
+    "redirect_url":  "/azure/api-management/developer-portal-extend-custom-functionality",
+    "redirect_document_id":  false
+},
 {
     "source_path":  "articles/virtual-machines/linux/find-unattached-nics.md",
     "redirect_url":  "/previous-versions/azure/virtual-machines/linux/find-unattached-nics",
@@ -533,6 +538,11 @@
     "redirect_url":  "/azure/frontdoor/front-door-geo-filtering",
     "redirect_document_id":  false
 },
+{
+    "source_path_from_root":  "/articles/frontdoor/front-door-geo-filtering.md",
+    "redirect_url":  "/azure/web-application-firewall/afds/waf-front-door-geo-filtering",
+    "redirect_document_id":  false
+},
 {
     "source_path_from_root":  "/articles/frontdoor/standard-premium/edge-locations.md",
     "redirect_url":  "/azure/frontdoor/edge-locations-by-region",
@@ -6813,6 +6823,11 @@
     "redirect_url":  "/azure/azure-functions/functions-bindings-error-pages",
     "redirect_document_id":  false
 },
+{
+    "source_path_from_root":  "/articles/azure-functions/functions-debug-event-grid-trigger-local.md",
+    "redirect_url":  "/azure/azure-functions/functions-event-grid-blob-trigger",
+    "redirect_document_id":  false
+},
 {
     "source_path_from_root":  "/articles/azure-government/documentation-government-k8.md",
     "redirect_url":  "/azure/azure-government",
@@ -6913,6 +6928,11 @@
     "redirect_url":  "/azure/azure-government/compare-azure-government-global-azure",
     "redirect_document_id":  false
 },
+{
+    "source_path_from_root":  "/articles/azure-government/documentation-government-overview.md",
+    "redirect_url":  "/azure/azure-government/documentation-government-plan-security",
+    "redirect_document_id":  false
+},
 {
     "source_path_from_root":  "/articles/security/compliance/azure-services-in-fedramp-auditscope.md",
     "redirect_url":  "/azure/azure-government/compliance/azure-services-in-fedramp-auditscope",
@@ -18319,14 +18339,19 @@
     "redirect_document_id":  false
 },
 {
-    "source_path_from_root":  "/articles/connectors/connectors-create-api-bingsearch.md",
+    "source_path_from_root": "/articles/connectors/connectors-create-api-bingsearch.md",
     "redirect_url":  "/connectors/bingsearch",
-    "redirect_document_id":  false
+    "redirect_document_id": false
 },
 {
-  "source_path_from_root": "/articles/connectors/connectors-create-api-twilio.md",
-  "redirect_url": "/connectors/twilio",
-  "redirect_document_id": false
+    "source_path_from_root": "/articles/connectors/connectors-create-api-twilio.md",
+    "redirect_url": "/connectors/twilio",
+    "redirect_document_id": false
+},
+{
+    "source_path_from_root": "/articles/connectors/connectors-create-api-sendgrid.md",
+    "redirect_url": "/connectors/sendgrid",
+    "redirect_document_id": false
 },
 {
   "source_path_from_root":  "/articles/connectors/connectors-schema-migration.md",
@@ -22333,6 +22358,11 @@
     "redirect_url":  "/azure/storage/common/customer-managed-keys-configure-key-vault",
     "redirect_document_id":  false
 },
+{
+    "source_path_from_root":  "/articles/storage/common/customer-managed-keys-configure-key-vault.md",
+    "redirect_url":  "/azure/storage/common/customer-managed-keys-configure-existing-account",
+    "redirect_document_id":  false
+},
 {
     "source_path_from_root":  "/articles/storage/common/encryption-customer-managed-keys.md",
     "redirect_url":  "/azure/storage/common/customer-managed-keys-overview",

articles/active-directory-b2c/TOC.yml

@@ -482,6 +482,8 @@
     - name: Identity verification and proofing partners
       href: identity-verification-proofing.md
       displayName: id verify, id verification, azure ad b2c proofing, id proofing
+    - name: Deduce
+      href: partner-deduce.md
     - name: eID-Me
       href: partner-eid-me.md
     - name: Experian

articles/active-directory-b2c/configure-authentication-in-azure-static-app.md

@@ -7,7 +7,7 @@ manager: CelesteDG
 ms.service: active-directory
 ms.workload: identity
 ms.topic: reference
-ms.date: 06/28/2022
+ms.date: 08/22/2022
 ms.author: kengaderdus
 ms.subservice: B2C
 ms.custom: "b2c-support"
@@ -30,7 +30,7 @@ OpenID Connect (OIDC) is an authentication protocol that's built on OAuth 2.0. U
 When the access token expires or the app session is invalidated, Azure Static Web App initiates a new authentication request and redirects users to Azure AD B2C. If the Azure AD B2C [SSO session](session-behavior.md) is active, Azure AD B2C issues an access token without prompting users to sign in again. If the Azure AD B2C session expires or becomes invalid, users are prompted to sign in again.
 
 ## Prerequisites
-
+- A premium Azure subscription. 
 - If you haven't created an app yet, follow the guidance how to create an [Azure Static Web App](../static-web-apps/overview.md).
 - Familiarize yourself with the Azure Static Web App [staticwebapp.config.json](../static-web-apps/configuration.md) configuration file.
 - Familiarize yourself with the Azure Static Web App [App Settings](../static-web-apps/application-settings.md).

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

@@ -7,15 +7,15 @@ manager: CelesteDG
 ms.service: active-directory
 ms.workload: identity
 ms.topic: how-to
-ms.date: 07/07/2022
+ms.date: 08/25/2022
 ms.author: kengaderdus
 ms.subservice: B2C
 ms.custom: "b2c-support"
 ---
 
 # Configure authentication in a sample React single-page application by using Azure Active Directory B2C
 
-This article uses a sample React single-page application (SPA) to illustrate how to add Azure Active Directory B2C (Azure AD B2C) authentication to your React apps.
+This article uses a sample React single-page application (SPA) to illustrate how to add Azure Active Directory B2C (Azure AD B2C) authentication to your React apps. The React SPA also calls an API that's protected by Azure AD B2C itself. 
 
 ## Overview
 
@@ -121,7 +121,7 @@ Now that you've obtained the SPA sample, update the code with your Azure AD B2C
 | b2cPolicies | authorities | Replace `your-tenant-name` with your Azure AD B2C [tenant name](tenant-management.md#get-your-tenant-name). For example, use `contoso.onmicrosoft.com`. Then, replace the policy name with the user flow or custom policy that you created in [step 1](#step-1-configure-your-user-flow). For example: `https://<your-tenant-name>.b2clogin.com/<your-tenant-name>.onmicrosoft.com/<your-sign-in-sign-up-policy>`. |
 | b2cPolicies | authorityDomain|Your Azure AD B2C [tenant name](tenant-management.md#get-your-tenant-name). For example: `contoso.onmicrosoft.com`. |
 | Configuration | clientId | The React application ID from [step 2.3](#23-register-the-react-app). |
-| protectedResources| endpoint| The URL of the web API: `http://localhost:5000/api/todolist`. |
+| protectedResources| endpoint| The URL of the web API: `http://localhost:5000/hello`. |
 | protectedResources| scopes| The web API scopes that you created in [step 2.2](#22-configure-scopes). For example: `b2cScopes: ["https://<your-tenant-name>.onmicrosoft.com/tasks-api/tasks.read"]`. |
 
 Your resulting *src/authConfig.js* code should look similar to the following sample:
@@ -156,7 +156,7 @@ export const msalConfig: Configuration = {
 
 export const protectedResources = {
   todoListApi: {
-    endpoint: "http://localhost:5000/api/todolist",
+    endpoint: "http://localhost:5000/hello",
     scopes: ["https://your-tenant-namee.onmicrosoft.com/tasks-api/tasks.read"],
   },
 }
@@ -171,7 +171,7 @@ In the sample folder, open the *config.json* file. This file contains informatio
 
 |Section  |Key  |Value  |
 |---------|---------|---------|
-|credentials|tenantName| The first part of your Azure AD B2C [tenant name](tenant-management.md#get-your-tenant-name). For example: `contoso`.|
+|credentials|tenantName| Your Azure AD B2C [domain/tenant name](tenant-management.md#get-your-tenant-name). For example: `contoso.ommicrosoft.com`.|
 |credentials|clientID| The web API application ID from step [2.1](#21-register-the-web-api-application). In the [earlier diagram](#app-registration), it's the application with **App ID: 2**.|
 |credentials| issuer| (Optional) The token issuer `iss` claim value. Azure AD B2C by default returns the token in the following format: `https://<your-tenant-name>.b2clogin.com/<your-tenant-ID>/v2.0/`. Replace `<your-tenant-name>` with the first part of your Azure AD B2C [tenant name](tenant-management.md#get-your-tenant-name). Replace `<your-tenant-ID>` with your [Azure AD B2C tenant ID](tenant-management.md#get-your-tenant-id). |
 |policies|policyName|The user flow or custom policy that you created in [step 1](#step-1-configure-your-user-flow). If your application uses multiple user flows or custom policies, specify only one. For example, use the sign-up or sign-in user flow.|
@@ -182,7 +182,7 @@ Your final configuration file should look like the following JSON:
 ```json
 {
     "credentials": {
-        "tenantName": "<your-tenant-name>",
+        "tenantName": "<your-tenant-name>.ommicrosoft.com",
         "clientID": "<your-webapi-application-ID>",
         "issuer": "https://<your-tenant-name>.b2clogin.com/<your-tenant-ID>/v2.0/"
     },
@@ -201,7 +201,7 @@ Your final configuration file should look like the following JSON:
 
 ## Step 5: Run the React SPA and web API
 
-You're now ready to test the React scoped access to the API. In this step, run both the web API and the sample React application on your local machine. Then, sign in to the React application, and select the **TodoList** button to start a request to the protected API.
+You're now ready to test the React scoped access to the API. In this step, run both the web API and the sample React application on your local machine. Then, sign in to the React application, and select the **HelloAPI** button to start a request to the protected API.
 
 ### Run the web API
 
@@ -251,11 +251,13 @@ You're now ready to test the React scoped access to the API. In this step, run b
     ![Screenshot that shows the React sample app with the login link.](./media/configure-authentication-sample-react-spa-app/sample-app-sign-in.png)
 
 1. Choose **Sign in using Popup**, or **Sign in using Redirect**. 
-1. Complete the sign-up or sign in process. Upon successful sign in, you should see your profile. 
-1. From the menu, select **Hello API**. 
-1. Check out the result of the REST API call. The following screenshot shows the React sample REST API return value.
-
+1. Complete the sign-up or sign in process. Upon successful sign-in, you should see a page with three buttons, **HelloAPI**, **Edit Profile** and **Sign Out**. 
     ![Screenshot that shows the React sample app with the user profile, and the call to the A P I.](./media/configure-authentication-sample-react-spa-app/sample-app-call-api.png)
+1. From the menu, select **HelloAPI** button. 
+1. Check out the result of the REST API call. The following screenshot shows the React sample REST API return value:
+
+    :::image type="content" source="./media/configure-authentication-sample-react-spa-app/sample-app-call-api-result.png" alt-text="Screenshot of the React sample app with the user profile, and the result of calling the web A P I.":::
+
 
 ## Deploy your application 
 

articles/active-directory-b2c/enable-authentication-web-api.md

@@ -443,7 +443,7 @@ Under the project root folder, create a *config.json* file, and then add to it t
 ```json
 {
     "credentials": {
-        "tenantName": "<your-tenant-name>",
+        "tenantName": "<your-tenant-name>.onmicrosoft.com",
         "clientID": "<your-webapi-application-ID>",
         "issuer": "https://<your-tenant-name>.b2clogin.com/<your-tenant-ID>/v2.0/"
     },
@@ -470,7 +470,7 @@ In the *config.json* file, update the following properties:
 
 |Section  |Key  |Value  |
 |---------|---------|---------|
-| credentials | tenantName | The first part of your Azure AD B2C [tenant name](tenant-management.md#get-your-tenant-name) (for example, `contoso`).|
+| credentials | tenantName | Your Azure AD B2C [tenant name/domain name](tenant-management.md#get-your-tenant-name) (for example, `contoso.onmicrosoft.com`).|
 | credentials |clientID | The web API application ID. In the [preceding diagram](#app-registration-overview), it's the application with *App ID: 2*. To learn how to get your web API application registration ID, see [Prerequisites](#prerequisites). |
 | credentials | issuer| The token issuer `iss` claim value. By default, Azure AD B2C returns the token in the following format: `https://<your-tenant-name>.b2clogin.com/<your-tenant-ID>/v2.0/`. Replace `<your-tenant-name>` with the first part of your Azure AD B2C [tenant name](tenant-management.md#get-your-tenant-name). Replace `<your-tenant-ID>` with your [Azure AD B2C tenant ID](tenant-management.md#get-your-tenant-id). |
 | policies | policyName | The user flows, or custom policy. To learn how to get your user flow or policy, see [Prerequisites](#prerequisites).|

articles/active-directory-b2c/identity-verification-proofing.md

@@ -27,6 +27,7 @@ Microsoft partners with the following ISV partners.
 
 | ISV partner | Description and integration walkthroughs |
 |:-------------------------|:--------------|
+| ![Screenshot of a deduce logo.](./media/partner-gallery/deduce-logo.png) | [Deduce](./partner-deduce.md) is an identity verification and proofing provider focused on stopping account takeover and registration fraud. It helps combat identity fraud and creates a trusted user experience. |
 | ![Screenshot of a eid-me logo](./media/partner-gallery/eid-me-logo.png) | [eID-Me](./partner-eid-me.md) is an identity verification and decentralized digital identity solution for Canadian citizens. It enables organizations to meet Identity Assurance Level (IAL) 2 and Know Your Customer (KYC) requirements. |
 |![Screenshot of an Experian logo.](./media/partner-gallery/experian-logo.png) | [Experian](./partner-experian.md) is an Identity verification and proofing provider that performs risk assessments based on user attributes to prevent fraud. |
 |![Screenshot of an IDology logo.](./media/partner-gallery/idology-logo.png) | [IDology](./partner-idology.md) is an Identity verification and proofing provider with ID verification solutions, fraud prevention solutions, compliance solutions, and others.|