Skip to content

Commit d4f5d7f

Browse files
committed
Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)
2 parents d9df40e + 4e2820a commit d4f5d7f

File tree

147 files changed

+2025
-1265
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

147 files changed

+2025
-1265
lines changed

articles/active-directory-b2c/force-password-reset.md

Lines changed: 31 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ manager: CelesteDG
99
ms.service: active-directory
1010
ms.workload: identity
1111
ms.topic: how-to
12-
ms.date: 09/16/2021
12+
ms.date: 01/24/2022
1313
ms.author: kengaderdus
1414
ms.subservice: B2C
1515
zone_pivot_groups: b2c-policy-type
@@ -19,8 +19,6 @@ zone_pivot_groups: b2c-policy-type
1919

2020
[!INCLUDE [active-directory-b2c-choose-user-flow-or-custom-policy](../../includes/active-directory-b2c-choose-user-flow-or-custom-policy.md)]
2121

22-
::: zone pivot="b2c-user-flow"
23-
2422
## Overview
2523

2624
As an administrator, you can [reset a user's password](manage-users-portal.md#reset-a-users-password) if the user forgets their password. Or you would like to force them to reset the password. In this article, you'll learn how to force a password reset in these scenarios.
@@ -31,13 +29,6 @@ When an administrator resets a user's password via the Azure portal, the value o
3129

3230
The password reset flow is applicable to local accounts in Azure AD B2C that use an [email address](sign-in-options.md#email-sign-in) or [username](sign-in-options.md#username-sign-in) with a password for sign-in.
3331

34-
::: zone-end
35-
36-
::: zone pivot="b2c-custom-policy"
37-
38-
This feature is currently only available for User Flows. For setup steps, choose **User Flow** above. For custom policies, use the force password reset first logon [GitHub sample](https://github.com/azure-ad-b2c/samples/tree/master/policies/force-password-reset-first-logon) with prerequisites below.
39-
40-
::: zone-end
4132

4233
## Prerequisites
4334

@@ -75,6 +66,36 @@ To enable the **Forced password reset** setting in a sign-up or sign-in user flo
7566
1. Sign in with the user account for which you reset the password.
7667
1. You now must change the password for the user. Change the password and select **Continue**. The token is returned to `https://jwt.ms` and should be displayed to you.
7768

69+
::: zone-end
70+
71+
::: zone pivot="b2c-custom-policy"
72+
73+
## Configure your custom policy
74+
75+
Get the example of the force password reset policy on [GitHub](https://github.com/azure-ad-b2c/samples/tree/master/policies/force-password-reset). In each file, replace the string `yourtenant` with the name of your Azure AD B2C tenant. For example, if the name of your B2C tenant is *contosob2c*, all instances of `yourtenant.onmicrosoft.com` become `contosob2c.onmicrosoft.com`.
76+
77+
## Upload and test the policy
78+
79+
1. Sign in to the [Azure portal](https://portal.azure.com/).
80+
1. Make sure you're using the directory that contains your Azure AD B2C tenant by selecting the **Directories + subscriptions** icon in the portal toolbar.
81+
1. On the **Portal settings | Directories + subscriptions** page, find your Azure AD B2C directory in the **Directory name** list, and then select **Switch**.
82+
1. Choose **All services** in the top-left corner of the Azure portal, and then search for and select **Azure AD B2C**.
83+
1. Select **Identity Experience Framework**.
84+
1. In **Custom Policies**, select **Upload Policy**.
85+
1. Select the *TrustFrameworkExtensionsCustomForcePasswordReset.xml* file.
86+
1. Select **Upload**.
87+
1. Repeat steps 6 through 8 for the relying party file *TrustFrameworkExtensionsCustomForcePasswordReset.xml*.
88+
89+
## Run the policy
90+
91+
1. Open the policy that you uploaded *B2C_1A_TrustFrameworkExtensions_custom_ForcePasswordReset*.
92+
1. For **Application**, select the application that you registered earlier. To see the token, the **Reply URL** should show `https://jwt.ms`.
93+
1. Select **Run now**.
94+
1. Sign in with the user account for which you reset the password.
95+
1. You now must change the password for the user. Change the password and select **Continue**. The token is returned to `https://jwt.ms` and should be displayed to you.
96+
97+
::: zone-end
98+
7899
## Force password reset on next login
79100

80101
To force reset the password on next login, update the account password profile using MS Graph [Update user](/graph/api/user-update) operation. The following example updates the password profile [forceChangePasswordNextSignIn](user-profile-attributes.md#password-profile-property) attribute to `true`, which forces the user to reset the password on next login.
@@ -123,8 +144,6 @@ Once a password expiration policy has been set, you must also configure force pa
123144

124145
The password expiry duration default value is **90** days. The value is configurable by using the [Set-MsolPasswordPolicy](/powershell/module/msonline/set-msolpasswordpolicy) cmdlet from the Azure Active Directory Module for Windows PowerShell. This command updates the tenant, so that all users' passwords expire after number of days you configure.
125146

126-
::: zone-end
127-
128147
## Next steps
129148

130149
Set up a [self-service password reset](add-password-reset-policy.md).

articles/active-directory-b2c/oauth2-error-technical-profile.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ manager: CelesteDG
99
ms.service: active-directory
1010
ms.workload: identity
1111
ms.topic: reference
12-
ms.date: 05/26/2021
12+
ms.date: 01/25/2022
1313
ms.author: kengaderdus
1414
ms.subservice: B2C
1515
---
@@ -41,7 +41,7 @@ https://jwt.ms/#error=access_denied&error_description=AAD_Custom_1234%3a+My+cust
4141

4242
## Protocol
4343

44-
The **Name** attribute of the **Protocol** element needs to be set to `None`. Set the **OutputTokenFormat** element to `OAuth2Error`.
44+
The **Name** attribute of the **Protocol** element needs to be set to `OAuth2`. Set the **OutputTokenFormat** element to `OAuth2Error`.
4545

4646
The following example shows a technical profile for `ReturnOAuth2Error`:
4747

@@ -53,7 +53,7 @@ The following example shows a technical profile for `ReturnOAuth2Error`:
5353
<TechnicalProfiles>
5454
<TechnicalProfile Id="ReturnOAuth2Error">
5555
<DisplayName>Return OAuth2 error</DisplayName>
56-
<Protocol Name="None" />
56+
<Protocol Name="OAuth2" />
5757
<OutputTokenFormat>OAuth2Error</OutputTokenFormat>
5858
<CryptographicKeys>
5959
<Key Id="issuer_secret" StorageReferenceId="B2C_1A_TokenSigningKeyContainer" />
@@ -121,4 +121,4 @@ In the following example:
121121

122122
## Next steps
123123

124-
Learn about [UserJourneys](userjourneys.md)
124+
Learn about [UserJourneys](userjourneys.md)

articles/active-directory/develop/desktop-app-quickstart.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ zone_pivot_groups: desktop-app-quickstart
2424
::: zone-end
2525

2626
::: zone pivot="devlang-windows-desktop"
27-
[!INCLUDE [Windows Desktop .NET](./includes/desktop-app/quickstart-windows-desktop.md)]
27+
[!INCLUDE [Windows Presentation Foundation](./includes/desktop-app/quickstart-windows-desktop.md)]
2828
::: zone-end
2929

3030
::: zone pivot="devlang-nodejs-electron"

articles/active-directory/develop/includes/desktop-app/quickstart-windows-desktop.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,11 +11,11 @@ ms.workload: identity
1111
ms.date: 01/14/2022
1212
ms.author: jmprieur
1313
ms.custom: aaddev, identityplatformtop40, mode-api
14-
#Customer intent: As an application developer, I want to learn how my Windows desktop .NET application can get an access token and call an API that's protected by the Microsoft identity platform.
14+
#Customer intent: As an application developer, I want to learn how my Windows Presentation Foundation (WPF) application can get an access token and call an API that's protected by the Microsoft identity platform.
1515
---
1616

1717

18-
In this quickstart, you download and run a code sample that demonstrates how a Windows desktop .NET (WPF) application can sign in users and get an access token to call the Microsoft Graph API.
18+
In this quickstart, you download and run a code sample that demonstrates how a Windows Presentation Foundation (WPF) application can sign in users and get an access token to call the Microsoft Graph API.
1919

2020
See [How the sample works](#how-the-sample-works) for an illustration.
2121

articles/active-directory/develop/scenario-daemon-app-configuration.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -84,8 +84,10 @@ CLIENT_ID=Enter_the_Application_Id_Here
8484
CLIENT_SECRET=Enter_the_Client_Secret_Here
8585
8686
# Endpoints
87-
AAD_ENDPOINT=Enter_the_Cloud_Instance_Id_Here
88-
GRAPH_ENDPOINT=Enter_the_Graph_Endpoint_Here
87+
// the AAD endpoint is the authority endpoint for token issuance
88+
AAD_ENDPOINT=Enter_the_Cloud_Instance_Id_Here // https://login.microsoftonline.com/
89+
// the graph endpoint is the application ID URI of Microsoft graph
90+
GRAPH_ENDPOINT=Enter_the_Graph_Endpoint_Here // https://graph.microsoft.com/
8991
```
9092

9193
# [Python](#tab/python)

articles/active-directory/hybrid/how-to-connect-install-prerequisites.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -59,6 +59,7 @@ To read more about securing your Active Directory environment, see [Best practic
5959
#### Installation prerequisites
6060

6161
- Azure AD Connect must be installed on a domain-joined Windows Server 2016 or later.
62+
- The minimum .Net Framework version required is 4.6.2, and newer versions of .Net are also supported.
6263
- Azure AD Connect can't be installed on Small Business Server or Windows Server Essentials before 2019 (Windows Server Essentials 2019 is supported). The server must be using Windows Server standard or better.
6364
- The Azure AD Connect server must have a full GUI installed. Installing Azure AD Connect on Windows Server Core isn't supported.
6465
- The Azure AD Connect server must not have PowerShell Transcription Group Policy enabled if you use the Azure AD Connect wizard to manage Active Directory Federation Services (AD FS) configuration. You can enable PowerShell transcription if you use the Azure AD Connect wizard to manage sync configuration.

0 commit comments

Comments
 (0)