Skip to content

Commit 0f683f3

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into azure-communication-services-10dlc-articles
2 parents d242573 + 1e00801 commit 0f683f3

File tree

1,798 files changed

+2344
-370
lines changed

Some content is hidden

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

1,798 files changed

+2344
-370
lines changed
78.3 KB
Loading

articles/active-directory-b2c/partner-nok-nok.md

Lines changed: 22 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ To enable passkey authentication for your users, enable Nok Nok as an identity p
4040

4141
The following diagram illustrates the Nok Nok solution as an IdP for Azure AD B2C by using OpenID Connect (OIDC) for passkey authentication.
4242

43-
![Diagram of Nok Nok as IdP for Azure AD B2C using OpenID Connect (OIDC) for passkey authentication.](./media/partner-nok-nok/nok-nok-architecture-diagram.png)
43+
![Diagram for passkey authentication with Nok Nok as an IdP.](./media/partner-nok-nok/nok-nok-architecture-diagram.png)
4444

4545
### Scenario 1: Passkey registration
4646
1. The user navigates to the Nok Nok tutorial web app using the link provided by Nok Nok.
@@ -52,9 +52,11 @@ The following diagram illustrates the Nok Nok solution as an IdP for Azure AD B2
5252
### Scenario 2: Passkey authentication
5353
1. The user selects the sign-in with Nok Nok Cloud button on the Azure AD B2C sign-in page.
5454
2. Azure AD B2C redirects the user to the Nok Nok sign-in app.
55-
3. The user authenticates with their passkey.
56-
4. The Nok Nok server validates the passkey assertion and sends an OIDC authentication response to Azure AD B2C.
57-
5. Based on the authentication result, Azure AD B2C either grants or denies access to the target application.
55+
3. The user requests passkey authentication
56+
4. The user authenticates with their passkey.
57+
5. The Nok Nok Cloud validates the passkey assertion
58+
6. The Nok Nok Cloud sends an OIDC authentication response to Azure AD B2C.
59+
7. Based on the authentication result, Azure AD B2C either grants or denies access to the target application.
5860

5961
## Get started with Nok Nok
6062

@@ -125,6 +127,22 @@ For the following instructions, Nok Nok is a new OIDC IdP in the B2C identity pr
125127

126128
If the flow is incomplete, confirm the user is or isn't saved in the directory.
127129

130+
## Alternate flow for Authentication
131+
132+
The following diagram illustrates an alternate passkey sign in or sign up flow using the ID Token Hint feature of Azure AD B2C. With this approach, an Azure custom policy verifies the ID Token Hint produced by the Nok Nok Cloud. For more details, please refer to the article, [Define an ID token hint technical profile in an Azure Active Directory B2C custom policy](./id-token-hint.md). Please contact Nok Nok support for help with integrated the required Azure custom policy.
133+
134+
![Diagram for passkey authentication using ID Token Hint from Nok Nok.](./media/partner-nok-nok/nok-nok-id-token-hint-architecture-diagram.png)
135+
136+
The following are the steps
137+
1. The user selects the sign-in with Nok Nok Cloud button.
138+
2. The Nok Nok Cloud request passkey authentication.
139+
3. The user authenticates with their passkey.
140+
4. The Nok Nok Cloud validates the passkey assertion.
141+
5. The ID Token Hint is returned.
142+
6. The App posts an OIDC request with the ID Token Hint to Azure AD B2C.
143+
7. Azure AD B2C Custom Policy verifies the ID Token Hint.
144+
8. Based on the authentication result, Azure AD B2C either grants or denies access to the target application.
145+
128146
## Next steps
129147

130148
* [Azure AD B2C custom policy overview](./custom-policy-overview.md)

articles/active-directory-b2c/whats-new-docs.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: "What's new in Azure Active Directory business-to-customer (B2C)"
33
description: "New and updated documentation for the Azure Active Directory business-to-customer (B2C)."
4-
ms.date: 04/01/2025
4+
ms.date: 07/03/2025
55
ms.service: azure-active-directory
66
ms.subservice: b2c
77
ms.topic: whats-new
@@ -18,6 +18,15 @@ manager: CelesteDG
1818

1919
Welcome to what's new in Azure Active Directory B2C documentation. This article lists new and significantly updated docs from the past three months. To learn what's new with the B2C service, see [What's new in Microsoft Entra ID](../active-directory/fundamentals/whats-new.md), [Azure AD B2C developer release notes](custom-policy-developer-notes.md) and [What's new in Microsoft Entra External ID](/entra/external-id/whats-new-docs).
2020

21+
## June 2025
22+
23+
### Updated articles
24+
25+
- [Configure Cloudflare Web Application Firewall with Azure Active Directory B2C](partner-cloudflare.md) - Added a note about Azure Front Door-managed certificates
26+
- [Azure AD B2C: Frequently asked questions (FAQ)](faq.yml) - Updated the note in the Azure AD B2C end-of-sale section
27+
- [Page layout versions](page-layout.md) - Added updates related to CAPTCHA
28+
- [Securing phone-based multifactor authentication](phone-based-mfa.md) - Added information on preventing fraudulent sign-ups
29+
2130
## April 2025
2231

2332
### Updated articles
@@ -32,12 +41,3 @@ This month, we added an important note to our articles stating that starting May
3241
### Updated articles
3342
- [Error codes: Azure Active Directory B2C](error-codes.md) - Updated error messages
3443

35-
## February 2025
36-
37-
### Updated articles
38-
39-
- [Enable multifactor authentication in Azure Active Directory B2C](multi-factor-authentication.md) - Added SMS pricing
40-
- [Page layout versions](page-layout.md) - Updated the latest versions of the self-asserted and MFA pages
41-
- [Azure AD B2C: Frequently asked questions (FAQ)](faq.yml) - Added billing name change for SMS phone
42-
- [Enable CAPTCHA in Azure Active Directory B2C](add-captcha.md) - Added CAPTCHA feature flag
43-

articles/api-management/virtual-network-workspaces-resources.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -30,6 +30,8 @@ The virtual network must be in the same region and Azure subscription as the API
3030

3131
* The subnet used for virtual network integration or injection can only be used by a single workspace gateway. It can't be shared with another Azure resource.
3232

33+
[!INCLUDE [api-management-virtual-network-address-prefix](../../includes/api-management-virtual-network-address-prefix.md)]
34+
3335
## Subnet size
3436

3537
* Minimum: /27 (32 addresses)

articles/app-service/overview-hosting-plans.md

Lines changed: 14 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how App Service plans work in Azure App Service, how they're
44
keywords: app service, azure app service, scale, scalable, scalability, app service plan, app service cost
55
ms.assetid: dea3f41e-cf35-481b-a6bc-33d7fc9d01b1
66
ms.topic: overview
7-
ms.date: 03/28/2025
7+
ms.date: 07/02/2025
88
ms.update-cycle: 1095-days
99
ms.author: msangapu
1010
author: msangapu-msft
@@ -123,7 +123,19 @@ However, keep in mind that apps in the same App Service plan all share the same
123123

124124
Isolate your app in a new App Service plan when:
125125

126-
- The app is resource intensive.
126+
- The app is resource intensive. For general guidance, use this table:
127+
128+
| App Service plan | Maximum apps |
129+
|--|--|
130+
| B1, S1, P1v2, I1v1 | 8 |
131+
| B2, S2, P2v2, I2v1 | 16 |
132+
| B3, S3, P3v2, I3v1 | 32 |
133+
| P0v3 | 8 |
134+
| P1v3, I1v2 | 16 |
135+
| P2v3, I2v2, P1mv3 | 32 |
136+
| P3v3, I3v2, P2mv3 | 64 |
137+
| I4v2, I5v2, I6v2 | Maximum density bound by vCPU usage |
138+
| P3mv3, P4mv3, P5mv3 | Maximum density bound by vCPU usage |
127139
- You want to scale the app independently from the other apps in the existing plan.
128140
- The app needs resources in a different geographical region. This way, you can allocate a new set of resources for your app and gain greater control of your apps.
129141

articles/automanage/arm-deploy.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,7 @@ ms.service: azure-automanage
55
ms.custom: devx-track-arm-template
66
ms.topic: how-to
77
ms.date: 12/10/2021
8+
# Customer intent: "As an IT administrator, I want to onboard a machine to Azure Automanage using an ARM template, so that I can automate configuration management and ensure adherence to best practices efficiently."
89
---
910

1011
# Onboard a machine to Automanage with an Azure Resource Manager (ARM) template

articles/automanage/automanage-account.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,7 @@ description: Learn how an Automanage Account works and how to create one.
44
ms.service: azure-automanage
55
ms.topic: concept-article
66
ms.date: 12/10/2021
7+
# Customer intent: As a system administrator, I want to create and configure an Automanage Account, so that I can enable automated operations on my virtual machines and manage permissions effectively across multiple subscriptions.
78
---
89

910
# Automanage Accounts

articles/automanage/automanage-arc.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,7 @@ ms.service: azure-automanage
55
ms.collection: linux
66
ms.topic: concept-article
77
ms.date: 05/12/2022
8+
# Customer intent: As an IT administrator managing Arc-enabled servers, I want to configure Azure services using Automanage best practices, so that I can streamline monitoring, updates, and compliance for my virtual machines efficiently before the service retirement.
89
---
910

1011
# Azure Automanage for Machines Best Practices - Azure Arc-enabled servers

articles/automanage/automanage-linux.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,7 @@ ms.collection: linux
88
ms.topic: concept-article
99
ms.date: 12/10/2021
1010
ms.author: memccror
11+
# Customer intent: As a system administrator managing Linux virtual machines, I want to automate the onboarding and configuration of best practices services, so that I can ensure optimal performance, security, and compliance without manual intervention.
1112
---
1213

1314
# Azure Automanage for Machines Best Practices - Linux

articles/automanage/automanage-smb-over-quic.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,7 @@ ms.service: azure-automanage
66
ms.topic: concept-article
77
ms.date: 11/1/2021
88
ms.author: jol
9+
# Customer intent: "As an IT administrator managing virtual machines, I want to implement Automanage machine best practices for SMB over QUIC, so that I can ensure secure connectivity and compliance with certificate management without manual oversight."
910
---
1011

1112
# SMB over QUIC with Automanage machine best practices

0 commit comments

Comments
 (0)