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

Author: batamig

.github/policies/disallow-edits.yml

@@ -0,0 +1,89 @@
+name: GitOps.PullRequestIssueManagement
+description: GitOps.PullRequestIssueManagement primitive
+resource: repository
+
+configuration:
+  resourceManagementConfiguration:
+    eventResponderTasks:
+      - description: Close PRs that contain content for services that have been migrated out of the azure-docs-pr repository.
+        if:
+          - payloadType: Pull_Request
+          - isAction:
+              action: Opened
+          - or:              
+              - filesMatchPattern:
+                  pattern: articles/aks/*
+              - filesMatchPattern:
+                  pattern: articles/defender-for-cloud/*
+              - filesMatchPattern:
+                  pattern: articles/attestation/*
+              - filesMatchPattern:
+                  pattern: articles/confidential-ledger/*
+              - filesMatchPattern:
+                  pattern: articles/dedicated-hsm/*
+              - filesMatchPattern:
+                  pattern: articles/key-vault/*
+              - filesMatchPattern:
+                  pattern: articles/payment-hsm/*
+              - filesMatchPattern:
+                  pattern: articles/postgresql/*
+              - filesMatchPattern:
+                  pattern: articles/cosmos-db/*
+              - filesMatchPattern:
+                  pattern: articles/dms/*
+              - filesMatchPattern:
+                  pattern: articles/mariadb/*
+              - filesMatchPattern:
+                  pattern: articles/mysql/*
+              - filesMatchPattern:
+                  pattern: articles/managed-instance-apache-cassandra/*
+              - filesMatchPattern:
+                  pattern: articles/virtual-machines/*
+              - filesMatchPattern:
+                  pattern: articles/virtual-machines-scale-sets/*
+              - filesMatchPattern:
+                  pattern: articles/container-instances/*
+              - filesMatchPattern:
+                  pattern: articles/service-fabric/*
+              - filesMatchPattern:
+                  pattern: articles/machine-learning/*
+              - filesMatchPattern:
+                  pattern: articles/ai-studio/*
+              - filesMatchPattern:
+                  pattern: articles/ai-services/*
+              - filesMatchPattern:
+                  pattern: articles/genomics/*
+              - filesMatchPattern:
+                  pattern: articles/open-datasets/*
+              - filesMatchPattern:
+                  pattern: articles/search/*
+              - filesMatchPattern:
+                  pattern: articles/azure-monitor/*
+              - filesMatchPattern:
+                  pattern: articles/advisor/*
+              - filesMatchPattern:
+                  pattern: articles/chaos-studio/*
+              - filesMatchPattern:
+                  pattern: articles/service-health/*
+              - filesMatchPattern:
+                  pattern: articles/azure-arc/*
+              - filesMatchPattern:
+                  pattern: articles/azure-linux/*
+              - filesMatchPattern:
+                  pattern: articles/azure-portal/*
+              - filesMatchPattern:
+                  pattern: articles/copilot/*
+              - filesMatchPattern:
+                  pattern: articles/lighthouse/*
+              - filesMatchPattern:
+                  pattern: articles/quotas/*
+              - filesMatchPattern:
+                  pattern: articles/container-registry/*
+              - filesMatchPattern:
+                  pattern: articles/kubernetes-fleet/*
+        then:
+          - addReply:
+              reply: >-
+                @${issueAuthor} - You tried to add content to a folder path that has been removed from this repository. Your pull request will be automatically closed. Submit your changes to the updated repository, which can be identified by clicking the Edit this Document link at the top of any published article for that product or service.
+          - closePullRequest
+          

.openpublishing.publish.config.json

@@ -254,12 +254,6 @@
             "branch": "main",
             "branch_mapping": {}
         },
-        {
-            "path_to_root": "azure-reference-other-repo",
-            "url": "https://github.com/MicrosoftDocs/azure-reference-other-pr",
-            "branch": "main",
-            "branch_mapping": {}
-        },
         {
             "path_to_root": "azure-sdk-for-go-samples",
             "url": "https://github.com/Azure-Samples/azure-sdk-for-go-samples",

articles/active-directory-b2c/add-web-api-application.md

@@ -6,7 +6,7 @@ author: kengaderdus
 manager: CelesteDG
 
 ms.author: kengaderdus
-ms.date: 01/11/2024
+ms.date: 10/11/2024
 ms.custom: mvc
 ms.topic: how-to
 ms.service: azure-active-directory
@@ -21,9 +21,7 @@ ms.subservice: b2c
 
 This article shows you how to register web API resources in your Azure Active Directory B2C (Azure AD B2C) tenant so that they can accept and respond to requests by client applications that present an access token.
 
-To register an application in your Azure AD B2C tenant, you can use the Azure portal's new unified **App registrations** experience or the legacy **Applications (Legacy)** experience. [Learn more about the new experience](./app-registrations-training-guide.md).
-
-#### [App registrations](#tab/app-reg-ga/)
+To register an application in your Azure AD B2C tenant, you can use the following steps:
 
 1. Sign in to the [Azure portal](https://portal.azure.com).
 1. If you have access to multiple tenants, select the **Settings** icon in the top menu to switch to your Azure AD B2C tenant from the **Directories + subscriptions** menu.
@@ -34,22 +32,6 @@ To register an application in your Azure AD B2C tenant, you can use the Azure po
 1. Select **Register**.
 1. Record the **Application (client) ID** for use in your web API's code.
 
-
-#### [Applications (Legacy)](#tab/applications-legacy/)
-
-1. Sign in to the [Azure portal](https://portal.azure.com).
-1. If you have access to multiple tenants, select the **Settings** icon in the top menu to switch to your Azure AD B2C tenant from the **Directories + subscriptions** menu.
-1. Choose **All services** in the top-left corner of the Azure portal, and then search for and select **Azure AD B2C**.
-1. Select **Applications (Legacy)**, and then select **Add**.
-1. Enter a name for the application. For example, *webapi1*.
-1. For **Include web app/ web API** and **Allow implicit flow**, select **Yes**.
-1. For **Reply URL**, enter an endpoint where Azure AD B2C should return any tokens that your application requests. In your production application, you might set the reply URL to a value such as `https://localhost:44332`. For testing purposes, set the reply URL to `https://jwt.ms`.
-1. For **App ID URI**, enter the identifier used for your web API. The full identifier URI including the domain is generated for you. For example, `https://contosotenant.onmicrosoft.com/api`.
-1. Select **Create**.
-1. On the properties page, record the application ID that you'll use when you configure the web application.
-
-* * *
-
 ## Configure scopes
 
 Scopes provide a way to govern access to protected resources. Scopes are used by the web API to implement scope-based access control. For example, users of the web API could have both read and write access, or users of the web API might have only read access. In this tutorial, you use scopes to define read and write permissions for the web API.
@@ -62,4 +44,4 @@ To call a protected web API from an application, you need to grant your applicat
 
 [!INCLUDE [active-directory-b2c-permissions-api](../../includes/active-directory-b2c-permissions-api.md)]
 
-Your application is registered to call the protected web API. A user authenticates with Azure AD B2C to use the application. The application obtains an authorization grant from Azure AD B2C to access the protected web API.
+Your application is registered to call the protected web API. A user authenticates with Azure AD B2C to use the application. The application obtains an authorization grant from Azure AD B2C to access the protected web API.

articles/active-directory-b2c/age-gating.md

@@ -1,12 +1,9 @@
 ---
 title: Enable age gating in Azure Active Directory B2C  
 description: Learn about how to identify minors using your application.
-
 author: kengaderdus
 manager: CelesteDG
-
 ms.service: azure-active-directory
-
 ms.topic: how-to
 ms.date: 01/11/2024
 ms.author: kengaderdus

articles/active-directory-b2c/application-types.md

@@ -2,19 +2,14 @@
 title: Application types supported by Azure AD B2C
 titleSuffix: Azure AD B2C
 description: Learn about the types of applications you can use with Azure Active Directory B2C.
-
 author: kengaderdus
+ms.author: kengaderdus
 manager: CelesteDG
-
 ms.service: azure-active-directory
-
 ms.topic: concept-article
-ms.date: 01/11/2024
-ms.author: kengaderdus
+ms.date: 10/11/2024
 ms.subservice: b2c
 
-
-
 #Customer intent: As a developer building an application that requires user authentication, I want to understand the different types of applications that can be used with Azure Active Directory B2C, so that I can choose the appropriate authentication method for my application.
 
 ---
@@ -94,12 +89,13 @@ To take advantage of this flow, your application can use an authentication libra
 
 ### Implicit grant flow
 
-Some libraries, like [MSAL.js 1.x](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/lib), only support the [implicit grant flow](implicit-flow-single-page-application.md) or your application is implemented to use implicit flow. In these cases, Azure AD B2C supports the [OAuth 2.0 implicit flow](implicit-flow-single-page-application.md). The implicit grant flow allows the application to get **ID** and **Access** tokens. Unlike the authorization code flow, implicit grant flow doesn't return a **Refresh token**.
-
-We **don't recommended** this approach.  
+Some libraries, like [MSAL.js 1.x](https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/lib), only support the [implicit grant flow](implicit-flow-single-page-application.md) or your application is implemented to use implicit flow. In these cases, Azure AD B2C supports the [OAuth 2.0 implicit flow](implicit-flow-single-page-application.md). The implicit grant flow allows the application to get **ID** and **Access** tokens. Unlike the authorization code flow, implicit grant flow doesn't return a **Refresh token**. 
 
 This authentication flow doesn't include application scenarios that use cross-platform JavaScript frameworks such as Electron and React-Native. Those scenarios require further capabilities for interaction with the native platforms.
 
+> [!WARNING]
+> Microsoft recommends you do *not* use the implicit grant flow. The recommended way of supporting SPAs is [OAuth 2.0 Authorization code flow (with PKCE)](./authorization-code-flow.md). Certain configurations of this flow requires a very high degree of trust in the application, and carries risks that are not present in other flows. You should only use this flow when other more secure flows aren't viable. For more information, see the [security concerns with implicit grant flow](/entra/identity-platform/v2-oauth2-implicit-grant-flow#security-concerns-with-implicit-grant-flow).
+
 ## Web APIs
 
 You can use Azure AD B2C to secure web services such as your application's RESTful web API. Web APIs can use OAuth 2.0 to secure their data, by authenticating incoming HTTP requests using tokens. The caller of a web API appends a token in the authorization header of an HTTP request:

articles/active-directory-b2c/client-credentials-grant-flow.md

@@ -6,7 +6,7 @@ author: kengaderdus
 manager: CelesteDG
 ms.service: azure-active-directory
 ms.topic: how-to
-ms.date: 01/11/2024
+ms.date: 10/11/2024
 ms.author: kengaderdus
 ms.subservice: b2c
 zone_pivot_groups: b2c-policy-type
@@ -263,9 +263,4 @@ The following example shows a client credentials user journey. The first and the
 ```
 
 
-::: zone-end
-
-
-## Next steps
-
-Learn how to [set up a resource owner password credentials flow in Azure AD B2C](add-ropc-policy.md)
+::: zone-end

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

@@ -7,7 +7,7 @@ manager: CelesteDG
 ms.service: azure-active-directory
 
 ms.topic: reference
-ms.date: 01/11/2024
+ms.date: 10/11/2024
 ms.author: kengaderdus
 ms.subservice: b2c
 ms.custom: "b2c-support"
@@ -100,15 +100,20 @@ Record the **Application (client) ID** to use later, when you configure the web
 
 ### Step 2.4: Enable the implicit grant flow
 
-In your own environment, if your SPA app uses MSAL.js 1.3 or earlier and the implicit grant flow or you configure [https://jwt.ms/](https://jwt.ms/) app for testing a user flow or custom policy, you need to enable the implicit grant flow in the app registration:
+You can enable implicit grant flow for two reasons, when you’re using MSAL.js version 1.3 or earlier version or when you use an app registration to [test a user flow for testing purposes](add-sign-up-and-sign-in-policy.md?pivots=b2c-user-flow#test-the-user-flow).
 
-1. In the left menu, under **Manage**, select **Authentication**.
+Use these steps to enable implicit grant flow for your app:
+
+1. Select the app registration you created.
+
+1. Under **Manage**, select **Authentication**.
 
 1. Under **Implicit grant and hybrid flows**, select both the **Access tokens (used for implicit flows)** and **ID tokens (used for implicit and hybrid flows)** check boxes.
 
 1. Select **Save**.
 
-If your app uses MSAL.js 2.0 or later, don't enable implicit flow grant as MSAL.js 2.0+ supports the authorization code flow with PKCE. The SPA app in this article uses PKCE flow, and so you don't need to enable implicit grant flow.   
+> [!NOTE]
+> If your app uses MSAL.js 2.0 or later, don't enable implicit grant flow as MSAL.js 2.0+ supports the [OAuth 2.0 Authorization code flow (with PKCE)](./authorization-code-flow.md). If you enable implicit grant to test a user flow, make sure you disable the implicit grant flow settings before you deploy your app to production.  
 
 ### Step 2.5: Grant permissions
 

articles/active-directory-b2c/custom-policies-series-branch-user-journey.md

@@ -10,7 +10,7 @@ ms.service: azure-active-directory
 
 ms.topic: how-to
 ms.custom: b2c-docs-improvements
-ms.date: 01/11/2024
+ms.date: 10/11/2024
 ms.author: kengaderdus
 ms.reviewer: yoelh
 ms.subservice: b2c
@@ -37,7 +37,7 @@ In this article, you learn how to use `EnabledForUserJourneys` element inside a
 
 - If you don't have one already, [create an Azure AD B2C tenant](tutorial-create-tenant.md) that is linked to your Azure subscription.
 
-- [Register a web application](tutorial-register-applications.md), and [enable ID token implicit grant](tutorial-register-applications.md#enable-id-token-implicit-grant). For the Redirect URI, use https://jwt.ms. 
+- [Register a web application](tutorial-register-applications.md). 
 
 - You must have [Visual Studio Code (VS Code)](https://code.visualstudio.com/) installed in your computer. 
 

articles/active-directory-b2c/custom-policies-series-call-rest-api.md

@@ -10,7 +10,7 @@ ms.service: azure-active-directory
 
 ms.topic: how-to
 ms.custom: b2c-docs-improvements, devx-track-js
-ms.date: 01/22/2024
+ms.date: 10/11/2024
 ms.author: kengaderdus
 ms.reviewer: yoelh
 ms.subservice: b2c
@@ -43,7 +43,7 @@ In [Create branching in user journey by using Azure AD B2C custom policies](cust
 
 - If you don't have one already, [create an Azure AD B2C tenant](tutorial-create-tenant.md) that is linked to your Azure subscription.
 
-- [Register a web application](tutorial-register-applications.md), and [enable ID token implicit grant](tutorial-register-applications.md#enable-id-token-implicit-grant). For the Redirect URI, use https://jwt.ms. 
+- [Register a web application](tutorial-register-applications.md). 
 
 - You must have [Node.js](https://nodejs.org) installed in your computer. 
 

articles/active-directory-b2c/custom-policies-series-collect-user-input.md

@@ -10,7 +10,7 @@ ms.service: azure-active-directory
 
 ms.topic: how-to
 ms.custom: b2c-docs-improvements
-ms.date: 01/11/2024
+ms.date: 10/11/2024
 ms.author: kengaderdus
 ms.reviewer: yoelh
 ms.subservice: b2c
@@ -42,7 +42,8 @@ In this article, you learn how to write a custom policy that collects user input
 
 - If you don't have one already, [create an Azure AD B2C tenant](tutorial-create-tenant.md) that is linked to your Azure subscription.
 
-- [Register a web application](tutorial-register-applications.md), and [enable ID token implicit grant](tutorial-register-applications.md#enable-id-token-implicit-grant). For the Redirect URI, use https://jwt.ms. 
+- [Register a web application](tutorial-register-applications.md).
+ 
 - You must have [Visual Studio Code (VS Code)](https://code.visualstudio.com/) installed in your computer. 
 
 - Complete the steps in [Write your first Azure AD B2C custom policy - Hello World!](custom-policies-series-hello-world.md). This article is a part of [Create and run your own custom policies how-to guide series](custom-policies-series-overview.md).