Skip to content

Commit 9c17913

Browse files
committed
Syncing with main. Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into work-whatsnew-feb24
2 parents f02dc00 + 881cc7b commit 9c17913

File tree

2,330 files changed

+21124
-14511
lines changed

Some content is hidden

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

2,330 files changed

+21124
-14511
lines changed

.openpublishing.publish.config.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1222,6 +1222,7 @@
12221222
".openpublishing.redirection.machine-configuration.json",
12231223
".openpublishing.redirection.marketplace.json",
12241224
".openpublishing.redirection.openshift.json",
1225+
".openpublishing.redirection.purview.json",
12251226
".openpublishing.redirection.security-benchmark.json",
12261227
".openpublishing.redirection.sentinel.json",
12271228
".openpublishing.redirection.spring-cloud.json",
@@ -1283,7 +1284,6 @@
12831284
"articles/operator-nexus/.openpublishing.redirection.operator-nexus.json",
12841285
"articles/peering-service/.openpublishing.redirection.peering-service.json",
12851286
"articles/postgresql/.openpublishing.redirection.postgresql.json",
1286-
"articles/purview/.openpublishing.redirection.purview.json",
12871287
"articles/route-server/.openpublishing.redirection.route-server.json",
12881288
"articles/sap/.openpublishing.redirection.sap.json",
12891289
"articles/security/.openpublishing.redirection.security.json",

.openpublishing.redirection.azure-kubernetes-service.json

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -461,11 +461,6 @@
461461
"source_path_from_root": "/articles/aks/command-invoke.md",
462462
"redirect_url": "/azure/aks/access-private-cluster",
463463
"redirect_document_id": false
464-
},
465-
{
466-
"source_path_from_root": "/articles/aks/ai-toolchain-operator.md",
467-
"redirect_url": "https://azure.microsoft.com/updates/preview-ai-toolchain-operator-addon-for-aks/",
468-
"redirect_document_id": false
469464
}
470465
]
471466
}

.openpublishing.redirection.azure-monitor.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6264,6 +6264,11 @@
62646264
"redirect_url": "/azure/azure-monitor/reference/supported-metrics/metrics-index",
62656265
"redirect_document_id": false
62666266
},
6267+
{
6268+
"source_path_from_root": "/articles/azure-monitor/essentials/platform-logs-overview.md",
6269+
"redirect_url": "/azure/azure-monitor/data-sources",
6270+
"redirect_document_id": false
6271+
},
62676272
{
62686273
"source_path_from_root": "/articles/azure-monitor/essentials/resource-logs-categories.md",
62696274
"redirect_url": "/azure/azure-monitor/reference/supported-logs/logs-index",

.openpublishing.redirection.certification.json

Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -74,6 +74,21 @@
7474
"source_path_from_root": "/articles/certification/how-to-indirectly-connected-devices.md",
7575
"redirect_url": "/azure/certification/overview",
7676
"redirect_document_id": false
77+
},
78+
{
79+
"source_path_from_root": "/articles/certification/program-requirements-pnp.md",
80+
"redirect_url": "/azure/certification/overview",
81+
"redirect_document_id": false
82+
},
83+
{
84+
"source_path_from_root": "/articles/certification/how-to-troubleshoot-pnp.md",
85+
"redirect_url": "/azure/certification/overview",
86+
"redirect_document_id": false
87+
},
88+
{
89+
"source_path_from_root": "/articles/certification/how-to-test-pnp.md",
90+
"redirect_url": "/azure/certification/overview",
91+
"redirect_document_id": false
7792
}
7893
]
7994
}

.openpublishing.redirection.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -980,6 +980,11 @@
980980
"redirect_url": "/analysis-services/tabular-models/compatibility-level-for-tabular-models-in-analysis-services",
981981
"redirect_document_id": false
982982
},
983+
{
984+
"source_path_from_root": "/articles/analysis-services/analysis-services-monitor.md",
985+
"redirect_url": "/azure/analysis-services/monitor-analysis-services",
986+
"redirect_document_id": false
987+
},
983988
{
984989
"source_path_from_root": "/articles/frontdoor/front-door-whats-new.md",
985990
"redirect_url": "https://azure.microsoft.com/updates/?category=networking\u0026query=Azure%20Front%20Door",

articles/active-directory-b2c/add-captcha.md

Lines changed: 7 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: kengaderdus
55
manager: mwongerapk
66
ms.service: active-directory
77
ms.topic: how-to
8-
ms.date: 01/17/2024
8+
ms.date: 03/01/2024
99
ms.custom: project-no-code
1010
ms.author: kengaderdus
1111
ms.subservice: B2C
@@ -19,7 +19,7 @@ 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-
Azure Active Directory B2C (Azure AD B2C) allows you to enable CAPTCHA prevent to automated attacks on your consumer-facing applications. Azure AD B2C’s CAPTCHA supports both audio and visual CAPTCHA challenges. You can enable this security feature in both sign-up and sign-in flows for your local accounts. CAPTCHA isn't applicable for social identity providers' sign-in.
22+
Azure Active Directory B2C (Azure AD B2C) allows you to enable CAPTCHA to prevent automated attacks on your consumer-facing applications. Azure AD B2C’s CAPTCHA supports both audio and visual CAPTCHA challenges. You can enable this security feature in both sign-up and sign-in flows for your local accounts. CAPTCHA isn't applicable for social identity providers' sign-in.
2323

2424
> [!NOTE]
2525
> This feature is in public preview
@@ -314,22 +314,20 @@ To enable CAPTCHA in MFA flow, you need to make an update in two technical profi
314314
...
315315
</TechnicalProfile>
316316
```
317-
::: zone-end
318-
319-
> [!NOTE]
320-
> - You can't add CAPTCHA to an MFA step in a sign-up only user flow.
321-
> - In an MFA flow, CAPTCHA is applicable where the MFA method you select is SMS or phone call, SMS only or Phone call only.
322-
323-
::: zone pivot="b2c-user-flow"
324317
## Upload the custom policy files
325318

326319
Use the steps in [Upload the policies](tutorial-create-user-flows.md?pivots=b2c-custom-policy&branch=pr-en-us-260336#upload-the-policies) to upload your custom policy files.
327320

328321
## Test the custom policy
329322

330323
Use the steps in [Test the custom policy](tutorial-create-user-flows.md?pivots=b2c-custom-policy#test-the-custom-policy) to test and confirm that CAPTCHA is enabled for your chosen flow. You should be prompted to enter the characters you see or hear depending on the CAPTCHA type, visual or audio, you choose.
324+
331325
::: zone-end
332326

327+
> [!NOTE]
328+
> - You can't add CAPTCHA to an MFA step in a sign-up only user flow.
329+
> - In an MFA flow, CAPTCHA is applicable where the MFA method you select is SMS or phone call, SMS only or Phone call only.
330+
333331
## Next steps
334332

335333
- Learn how to [Define a CAPTCHA technical profile](captcha-technical-profile.md).

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: kengaderdus
66
manager: CelesteDG
77
ms.service: active-directory
88
ms.topic: how-to
9-
ms.date: 02/14/2024
9+
ms.date: 03/01/2024
1010
ms.author: kengaderdus
1111
ms.subservice: B2C
1212
ms.custom: "b2c-support"
@@ -52,7 +52,7 @@ When using custom domains, consider the following:
5252

5353
- You can set up multiple custom domains. For the maximum number of supported custom domains, see [Microsoft Entra service limits and restrictions](/entra/identity/users/directory-service-limits-restrictions) for Azure AD B2C and [Azure subscription and service limits, quotas, and constraints](/azure/azure-resource-manager/management/azure-subscription-service-limits#azure-front-door-classic-limits) for Azure Front Door.
5454
- Azure Front Door is a separate Azure service, so extra charges will be incurred. For more information, see [Front Door pricing](https://azure.microsoft.com/pricing/details/frontdoor).
55-
- If you've multiple applications, migrate all oft them to the custom domain because the browser stores the Azure AD B2C session under the domain name currently being used.
55+
- If you've multiple applications, migrate all of them to the custom domain because the browser stores the Azure AD B2C session under the domain name currently being used.
5656
- After you configure custom domains, users will still be able to access the Azure AD B2C default domain name *&lt;tenant-name&gt;.b2clogin.com*. You need to block access to the default domain so that attackers can't use it to access your apps or run distributed denial-of-service (DDoS) attacks. [Submit a support ticket](find-help-open-support-ticket.md) to request for the blocking of access to the default domain.
5757

5858
> [!WARNING]

articles/active-directory-b2c/implicit-flow-single-page-application.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ ms.author: kengaderdus
1414
ms.subservice: B2C
1515

1616

17-
#Customer intent: As a developer building a single-page application (SPA) with a JavaScript framework, I want to implement OAuth 2.0 implicit flow for sign-in using Azure Active Directory B2C, so that I can securely authenticate users without server-to-server exchange and handle user flows like sign-up and profile management.
17+
#Customer intent: As a developer building a single-page application (SPA) with a JavaScript framework, I want to implement OAuth 2.0 implicit flow for sign-in using Azure AD B2C, so that I can securely authenticate users without server-to-server exchange and handle user flows like sign-up and profile management.
1818

1919
---
2020

articles/active-directory-b2c/index-desktop.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
11
### YamlMime:Landing
22

3-
title: Desktop app authentication documentation
3+
title: Azure AD B2C desktop app authentication documentation
44
summary: >
55
Learn how to sign in users and access web APIs in your desktop application using our how-to guides.
66
77
metadata:
88
author: kengaderdus
99
manager: CelesteDG
1010
ms.author: kengaderdus
11-
ms.date: 08/31/2022
11+
ms.date: 03/01/2024
1212
ms.service: active-directory
1313
ms.subservice: B2C
1414
ms.topic: landing-page

0 commit comments

Comments
 (0)