Skip to content

Commit 8c82b56

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into nw-nsg-portal
2 parents 7d18558 + 32788d3 commit 8c82b56

File tree

794 files changed

+6771
-5117
lines changed

Some content is hidden

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

794 files changed

+6771
-5117
lines changed

.openpublishing.redirection.active-directory.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1875,6 +1875,11 @@
18751875
"redirect_url": "/azure/active-directory/hybrid/migrate-from-federation-to-cloud-authentication",
18761876
"redirect_document_id": true
18771877
},
1878+
{
1879+
"source_path_from_root": "/articles/active-directory/fundamentals/active-directory-deployment-checklist-p2.md",
1880+
"redirect_url": "/azure/active-directory/fundamentals/concept-secure-remote-workers",
1881+
"redirect_document_id": true
1882+
},
18781883
{
18791884
"source_path_from_root": "/articles/active-directory/conditional-access/app-based-mfa.md",
18801885
"redirect_url": "/azure/active-directory/authentication/tutorial-enable-azure-mfa",

.openpublishing.redirection.azure-monitor.json

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,10 @@
11
{
22
"redirections": [
3+
{
4+
"source_path_from_root": "/articles/azure-monitor/snapshot-debugger/snapshot-debugger-troubleshoot.md",
5+
"redirect_url": "https://learn.microsoft.com/troubleshoot/azure/azure-monitor/app-insights/snapshot-debugger-troubleshoot",
6+
"redirect_document_id": false
7+
},
38
{
49
"source_path_from_root": "/articles/azure-monitor/best-practices.md",
510
"redirect_url": "/azure/azure-monitor/getting-started",
@@ -87,7 +92,7 @@
8792
},
8893
{
8994
"source_path_from_root": "/articles/azure-monitor/app/snapshot-debugger-troubleshoot.md",
90-
"redirect_url": "/azure/azure-monitor/snapshot-debugger/snapshot-debugger-troubleshoot",
95+
"redirect_url": "https://learn.microsoft.com/troubleshoot/azure/azure-monitor/app-insights/snapshot-debugger-troubleshoot",
9196
"redirect_document_id": false
9297
},
9398
{

.openpublishing.redirection.defender-for-cloud.json

Lines changed: 32 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -383,7 +383,7 @@
383383
{
384384
"source_path_from_root": "/articles/security-center/defender-for-cloud-introduction.md",
385385
"redirect_url": "/azure/defender-for-cloud/defender-for-cloud-introduction",
386-
"redirect_document_id": true
386+
"redirect_document_id": false
387387
},
388388
{
389389
"source_path_from_root": "/articles/security-center/defender-for-container-registries-cicd.md",
@@ -473,7 +473,7 @@
473473
{
474474
"source_path_from_root": "/articles/security-center/enable-data-collection.md",
475475
"redirect_url": "/azure/defender-for-cloud/enable-data-collection",
476-
"redirect_document_id": true
476+
"redirect_document_id": false
477477
},
478478
{
479479
"source_path_from_root": "/articles/security-center/enable-enhanced-security.md",
@@ -508,7 +508,7 @@
508508
{
509509
"source_path_from_root": "/articles/security-center/get-started.md",
510510
"redirect_url": "/azure/defender-for-cloud/get-started",
511-
"redirect_document_id": true
511+
"redirect_document_id": false
512512
},
513513
{
514514
"source_path_from_root": "/articles/security-center/harden-docker-hosts.md",
@@ -553,7 +553,7 @@
553553
{
554554
"source_path_from_root": "/articles/security-center/os-coverage.md",
555555
"redirect_url": "/azure/defender-for-cloud/os-coverage",
556-
"redirect_document_id": true
556+
"redirect_document_id": false
557557
},
558558
{
559559
"source_path_from_root": "/articles/security-center/other-threat-protections.md",
@@ -568,7 +568,7 @@
568568
{
569569
"source_path_from_root": "/articles/security-center/permissions.md",
570570
"redirect_url": "/azure/defender-for-cloud/permissions",
571-
"redirect_document_id": true
571+
"redirect_document_id": false
572572
},
573573
{
574574
"source_path_from_root": "/articles/security-center/protect-network-resources.md",
@@ -653,7 +653,7 @@
653653
{
654654
"source_path_from_root": "/articles/security-center/supported-machines-endpoint-solutions-clouds.md",
655655
"redirect_url": "/azure/defender-for-cloud/supported-machines-endpoint-solutions-clouds-containers",
656-
"redirect_document_id": true
656+
"redirect_document_id": false
657657
},
658658
{
659659
"source_path_from_root": "/articles/security-center/tutorial-protect-resources.md",
@@ -779,6 +779,31 @@
779779
"source_path_from_root": "/articles/defender-for-cloud/security-center-planning-and-operations-guide.md",
780780
"redirect_url": "/azure/defender-for-cloud/defender-for-cloud-planning-and-operations-guide",
781781
"redirect_document_id": true
782+
},
783+
{
784+
"source_path_from_root": "/articles/defender-for-cloud/enhanced-security-features-overview.md",
785+
"redirect_url": "/azure/defender-for-cloud/defender-for-cloud-introduction",
786+
"redirect_document_id": true
787+
},
788+
{
789+
"source_path_from_root": "/articles/defender-for-cloud/os-coverage.md",
790+
"redirect_url": "/azure/defender-for-cloud/monitoring-components",
791+
"redirect_document_id": false
792+
},
793+
{
794+
"source_path_from_root": "/articles/defender-for-cloud/features-paas.md",
795+
"redirect_url": "/azure/defender-for-cloud/support-matrix-defender-for-cloud",
796+
"redirect_document_id": true
797+
},
798+
{
799+
"source_path_from_root": "/articles/defender-for-cloud/supported-machines-endpoint-solutions-clouds-containers.md",
800+
"redirect_url": "/azure/defender-for-cloud/support-matrix-defender-for-containers",
801+
"redirect_document_id": true
802+
},
803+
{
804+
"source_path_from_root": "/articles/defender-for-cloud/supported-machines-endpoint-solutions-clouds-servers.md",
805+
"redirect_url": "/azure/defender-for-cloud/support-matrix-defender-for-servers",
806+
"redirect_document_id": true
782807
}
783-
]
808+
]
784809
}

.openpublishing.redirection.json

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5968,6 +5968,16 @@
59685968
"redirect_url": "/azure/architecture/service-fabric/migrate-from-cloud-services",
59695969
"redirect_document_id": false
59705970
},
5971+
{
5972+
"source_path_from_root": "/articles/batch/batch-custom-image-pools-to-azure-compute-gallery-migration-guide.md",
5973+
"redirect_url": "/azure/batch",
5974+
"redirect_document_id": false
5975+
},
5976+
{
5977+
"source_path_from_root": "/articles/batch/batch-pools-to-simplified-compute-node-communication-model-migration-guide.md",
5978+
"redirect_url": "/azure/batch",
5979+
"redirect_document_id": false
5980+
},
59715981
{
59725982
"source_path_from_root": "/articles/batch/big-compute-resources.md",
59735983
"redirect_url": "/azure/architecture/topics/high-performance-computing/",

articles/active-directory-b2c/custom-policies-series-overview.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ In Azure Active Directory B2C (Azure AD B2C), you can create user experiences by
2222

2323
User flows are already customizable such as [changing UI](customize-ui.md), [customizing language](language-customization.md) and using [custom attributes](user-flow-custom-attributes.md). However, these customizations might not cover all your business specific needs, which is the reason why you need custom policies.
2424

25-
While you can use pre-made [custom policy starter pack](/tutorial-create-user-flows.md?pivots=b2c-custom-policy#custom-policy-starter-pack), it's important for you understand how custom policy is built from scratch. In this how-to guide series, you'll learn what you need to understand for you to customize the behavior of your user experience by using custom policies. At the end of this how-to guide series, you should be able to read and understand existing custom policies or write your own from scratch.
25+
While you can use pre-made [custom policy starter pack](/azure/active-directory-b2c/tutorial-create-user-flows?pivots=b2c-custom-policy#custom-policy-starter-pack), it's important for you understand how custom policy is built from scratch. In this how-to guide series, you'll learn what you need to understand for you to customize the behavior of your user experience by using custom policies. At the end of this how-to guide series, you should be able to read and understand existing custom policies or write your own from scratch.
2626

2727
## Prerequisites
2828

@@ -48,4 +48,4 @@ This how-to guide series consists of multiple articles. We recommend that you st
4848

4949
- Learn about [Azure AD B2C TrustFrameworkPolicy BuildingBlocks](buildingblocks.md)
5050

51-
- [Write your first Azure Active Directory B2C custom policy - Hello World!](custom-policies-series-hello-world.md)
51+
- [Write your first Azure Active Directory B2C custom policy - Hello World!](custom-policies-series-hello-world.md)

articles/active-directory-b2c/enable-authentication-react-spa-app.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ The sample code is made up of the following components. Add these components fro
7777
> [!IMPORTANT]
7878
> If the App component file name is `App.js`, change it to `App.jsx`.
7979
80-
- [src/pages/Hello.jsx](https://github.com/Azure-Samples/ms-identity-javascript-react-tutorial/blob/main/6-AdvancedScenarios/1-call-api-obo/SPA/src/pages/Hello.jsx) - Demonstrate how to call a protected resource with OAuth2 bearer token.
80+
- [src/pages/Hello.jsx](https://github.com/Azure-Samples/ms-identity-javascript-react-tutorial/blob/main/6-AdvancedScenarios/1-call-api-obo/SPA/src/pages/Home.jsx) - Demonstrate how to call a protected resource with OAuth2 bearer token.
8181
- It uses the [useMsal](https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/dev/lib/msal-react/docs/hooks.md) hook that returns the PublicClientApplication instance.
8282
- With PublicClientApplication instance, it acquires an access token to call the REST API.
8383
- Invokes the [callApiWithToken](https://github.com/Azure-Samples/ms-identity-javascript-react-tutorial/blob/main/4-Deployment/2-deploy-static/App/src/fetch.js) function to fetch the data from the REST API and renders the result using the **DataDisplay** component.

articles/active-directory-b2c/manage-users-portal.md

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,14 +2,14 @@
22
title: Create & delete Azure AD B2C consumer user accounts in the Azure portal
33
description: Learn how to use the Azure portal to create and delete consumer users in your Azure AD B2C directory.
44
services: active-directory-b2c
5-
author: kengaderdus
5+
author: garrodonnell
66
manager: CelesteDG
77

88
ms.service: active-directory
99
ms.workload: identity
1010
ms.topic: how-to
11-
ms.date: 09/20/2021
12-
ms.author: kengaderdus
11+
ms.date: 02/24/2023
12+
ms.author: godonnell
1313
ms.subservice: B2C
1414
---
1515

@@ -59,9 +59,7 @@ To reset a user's password:
5959
1. In your Azure AD B2C directory, select **Users**, and then select the user you want to reset the password.
6060
1. Search for and select the user that needs the reset, and then select **Reset Password**.
6161

62-
The **Alain Charon - Profile** page appears with the **Reset password** option.
63-
64-
![User's profile page, with Reset password option highlighted](media/manage-users-portal/user-profile-reset-password-link.png)
62+
:::image type="content" source="media/manage-users-portal/user-profile-reset-password-link.png" alt-text="Screenshot User's profile page with Reset Password option highlighted." lightbox="media/manage-users-portal/user-profile-reset-password-link.png":::
6563

6664
1. In the **Reset password** page, select **Reset password**.
6765
1. Copy the password and give it to the user. The user will be required to change the password during the next sign-in process.
26 KB
Loading

articles/active-directory-b2c/partner-dynamics-365-fraud-protection.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.reviewer: kengaderdus
99
ms.service: active-directory
1010
ms.workload: identity
1111
ms.topic: how-to
12-
ms.date: 11/29/2022
12+
ms.date: 02/27/2023
1313
ms.author: gasinh
1414
ms.subservice: B2C
1515
---
@@ -120,6 +120,7 @@ In the provided [custom policies](https://github.com/azure-ad-b2c/partner-integr
120120
|{Settings:DfpTenantId}|The ID of the Azure AD tenant (not B2C) where DFP is licensed and installed|`01234567-89ab-cdef-0123-456789abcdef` or `consoto.onmicrosoft.com` |
121121
|{Settings:DfpAppClientIdKeyContainer}|Name of the policy key-in which you save the DFP client ID|`B2C_1A_DFPClientId`|
122122
|{Settings:DfpAppClientSecretKeyContainer}|Name of the policy key-in which you save the DFP client secret |`B2C_1A_DFPClientSecret`|
123+
|{Settings:DfpEnvironment}| The ID of the DFP environment.|Environment ID is a global unique identifier of the DFP environment that you sends the data to. Your custom policy should invoke the API endpoint including the `x-ms-dfpenvid=<your-env-id>` in the query string parameter.|
123124

124125
*You can set up application insights in an Azure AD tenant or subscription. This value is optional but [recommended to assist with debugging](./troubleshoot-with-application-insights.md).
125126

articles/active-directory-b2c/phone-based-mfa.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,9 @@ ms.subservice: B2C
1818

1919
With Azure Active Directory (Azure AD) Multi-Factor Authentication (MFA), users can choose to receive an automated voice call at a phone number they register for verification. Malicious users could take advantage of this method by creating multiple accounts and placing phone calls without completing the MFA registration process. These numerous failed sign-ups could exhaust the allowed sign-up attempts, preventing other users from signing up for new accounts in your Azure AD B2C tenant. To help protect against these attacks, you can use Azure Monitor to monitor phone authentication failures and mitigate fraudulent sign-ups.
2020

21+
> [!IMPORTANT]
22+
> Authenticator app (TOTP) provides stronger security than SMS/Phone multi-factor authentication. To set this up please read our instructions for [enabling multi-factor authentication in Azure Active Directory B2C](multi-factor-authentication.md).
23+
2124
## Prerequisites
2225

2326
Before you begin, create a [Log Analytics workspace](azure-monitor.md).

0 commit comments

Comments
 (0)