Skip to content

Commit c09daca

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into patricka-config-include
2 parents 80fd281 + c869dea commit c09daca

File tree

213 files changed

+3707
-1460
lines changed

Some content is hidden

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

213 files changed

+3707
-1460
lines changed

.openpublishing.redirection.virtual-desktop.json

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -409,6 +409,16 @@
409409
"source_path_from_root": "/articles/virtual-desktop/autoscale-scaling-plan.md",
410410
"redirect_url": "/azure/virtual-desktop/autoscale-create-assign-scaling-plan",
411411
"redirect_document_id": true
412+
},
413+
{
414+
"source_path_from_root": "/articles/virtual-desktop/getting-started-feature.md",
415+
"redirect_url": "/azure/virtual-desktop/quickstart",
416+
"redirect_document_id": true
417+
},
418+
{
419+
"source_path_from_root": "/articles/virtual-desktop/troubleshoot-getting-started.md",
420+
"redirect_url": "/azure/virtual-desktop/troubleshoot-quickstart",
421+
"redirect_document_id": true
412422
}
413423
]
414424
}

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -78,7 +78,7 @@ To create the web app registration, use the following steps:
7878
1. Under **Name**, enter a name for the application (for example, *webapp1*).
7979
1. Under **Supported account types**, select **Accounts in any identity provider or organizational directory (for authenticating users with user flows)**.
8080
1. Under **Redirect URI**, select **Web** and then, in the URL box, enter `https://localhost:44316/signin-oidc`.
81-
1. Under **Authentication**, go to **Implicit grant and hybrid flows**, select the **ID tokens (used for implicit and hybrid flows)** checkbox.
81+
1. Under **Manage**, select the **Authentication**, go to **Implicit grant and hybrid flows**, select the **ID tokens (used for implicit and hybrid flows)** checkbox.
8282
1. Under **Permissions**, select the **Grant admin consent to openid and offline access permissions** checkbox.
8383
1. Select **Register**.
8484
1. Select **Overview**.

articles/active-directory-b2c/custom-domain.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -185,7 +185,7 @@ To create a CNAME record for your custom domain:
185185
1. Find the page for managing DNS records by consulting the provider's documentation or searching for areas of the web site labeled **Domain Name**, **DNS**, or **Name Server Management**.
186186

187187
1. Create a new TXT DNS record and complete the fields as shown below:
188-
1. Name: `_dnsauth.contoso.com`, but you need to enter just `_dnsauth`.
188+
1. Name: `_dnsauth.login.contoso.com`, but you need to enter just `_dnsauth`.
189189
1. Type: `TXT`
190190
1. Value: Something like `75abc123t48y2qrtsz2bvk......`.
191191

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

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.service: active-directory
1010

1111
ms.topic: how-to
1212
ms.custom: b2c-docs-improvements
13-
ms.date: 01/11/2024
13+
ms.date: 05/11/2024
1414
ms.author: kengaderdus
1515
ms.reviewer: yoelh
1616
ms.subservice: B2C
@@ -206,7 +206,7 @@ We use the `ClaimGenerator` technical profile to execute three claims transforma
206206
</Precondition>
207207
</Preconditions>
208208
</ValidationTechnicalProfile>
209-
<ValidationTechnicalProfile ReferenceId="DisplayNameClaimGenerator"/>
209+
<ValidationTechnicalProfile ReferenceId="UserInputDisplayNameGenerator"/>
210210
<ValidationTechnicalProfile ReferenceId="AAD-UserWrite"/>
211211
</ValidationTechnicalProfiles>
212212
<!--</TechnicalProfile>-->
@@ -407,15 +407,14 @@ To configure a display control, use the following steps:
407407

408408
1. Use the procedure in [step 6](#step-6---upload-policy) and [step 7](#step-7---test-policy) to upload your policy file, and test it. This time, you must verify your email address before a user account is created.
409409

410-
<a name='update-user-account-by-using-azure-ad-technical-profile'></a>
411410

412411
## Update user account by using Microsoft Entra ID technical profile
413412

414-
You can configure a Microsoft Entra ID technical profile to update a user account instead of attempting to create a new one. To do so, set the Microsoft Entra ID technical profile to throw an error if the specified user account doesn't already exist in the `Metadata` collection by using the following code. The *Operation* needs to be set to *Write*:
413+
You can configure a Microsoft Entra ID technical profile to update a user account instead of attempting to create a new one. To do so, set the Microsoft Entra ID technical profile to throw an error if the specified user account doesn't already exist in the metadata collection by using the following code. Also, remove the `Key="UserMessageIfClaimsPrincipalAlreadyExists` metadata entry. The *Operation* needs to be set to *Write*:
415414

416415
```xml
417416
<Item Key="Operation">Write</Item>
418-
<Item Key="RaiseErrorIfClaimsPrincipalDoesNotExist">true</Item>
417+
<Item Key="RaiseErrorIfClaimsPrincipalDoesNotExist">false</Item>
419418
```
420419

421420
## Use custom attributes

articles/active-directory-b2c/index.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -228,7 +228,7 @@ conceptualContent:
228228
- text: Deploy with GitHub actions
229229
url: deploy-custom-policies-github-action.md
230230
itemType: how-to-guide
231-
- text: Manage resources using Microsoft Powershell
231+
- text: Manage resources using Microsoft PowerShell
232232
url: manage-custom-policies-powershell.md
233233
itemType: how-to-guide
234234

0 commit comments

Comments
 (0)