Skip to content

Commit 703fb04

Browse files
committed
Resolving merge conflict.
2 parents 148cafa + 36d7b48 commit 703fb04

File tree

2,542 files changed

+39370
-21146
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,542 files changed

+39370
-21146
lines changed

.openpublishing.redirection.api-management.json

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -149,6 +149,16 @@
149149
"source_path_from_root": "/articles/api-management/validation-policies.md",
150150
"redirect_url": "/azure/api-management/api-management-policies#validation-policies",
151151
"redirect_document_id": false
152+
},
153+
{
154+
"source_path_from_root": "/articles/api-management/authorizations-how-to.md",
155+
"redirect_url": "/azure/api-management/authorizations-how-to-github",
156+
"redirect_document_id": false
157+
},
158+
{
159+
"source_path_from_root": "/articles/api-management/authorizations-reference.md",
160+
"redirect_url": "/azure/api-management/authorizations-configure-common-providers",
161+
"redirect_document_id": false
152162
}
153163
]
154164
}

.openpublishing.redirection.azure-monitor.json

Lines changed: 26 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,11 @@
11
{
22
"redirections": [
3-
{
3+
{
4+
"source_path_from_root": "/articles/azure-monitor/snapshot-debugger/snapshot-collector-release-notes.md",
5+
"redirect_url": "/azure/azure-monitor/snapshot-debugger/snapshot-debugger#release-notes-for-microsoftapplicationinsightssnapshotcollector",
6+
"redirect_document_id": false
7+
},
8+
{
49
"source_path_from_root": "/articles/azure-monitor/best-practices.md",
510
"redirect_url": "/azure/azure-monitor/getting-started",
611
"redirect_document_id": false
@@ -45,6 +50,26 @@
4550
"redirect_url": "/azure/azure-monitor/app/app-insights-overview",
4651
"redirect_document_id": false
4752
},
53+
{
54+
"source_path_from_root": "/articles/azure-monitor/app/tutorial-runtime-exceptions.md",
55+
"redirect_url": "/previous-versions/azure/azure-monitor/app/tutorial-runtime-exceptions",
56+
"redirect_document_id": false
57+
},
58+
{
59+
"source_path_from_root": "/articles/azure-monitor/app/tutorial-performance.md",
60+
"redirect_url": "/previous-versions/azure/azure-monitor/app/tutorial-performance",
61+
"redirect_document_id": false
62+
},
63+
{
64+
"source_path_from_root": "/articles/azure-monitor/app/tutorial-users.md",
65+
"redirect_url": "/previous-versions/azure/azure-monitor/app/tutorial-users",
66+
"redirect_document_id": false
67+
},
68+
{
69+
"source_path_from_root": "/articles/azure-monitor/app/custom-data-correlation.md",
70+
"redirect_url": "/previous-versions/azure/azure-monitor/app/custom-data-correlation",
71+
"redirect_document_id": false
72+
},
4873
{
4974
"source_path_from_root": "/articles/azure-monitor/app/correlation.md",
5075
"redirect_url": "/previous-versions/azure/azure-monitor/app/distributed-tracing-telemetry-correlation",

.openpublishing.redirection.healthcare-apis.json

Lines changed: 17 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -586,15 +586,19 @@
586586
"redirect_document_id": false
587587
},
588588
{ "source_path_from_root": "/articles/healthcare-apis/iot/iot-data-flow.md",
589-
"redirect_url": "/azure/healthcare-apis/iot/understand-service",
589+
"redirect_url": "/azure/healthcare-apis/iot/overview-of-device-data-processing-stages",
590590
"redirect_document_id": false
591591
},
592592
{ "source_path_from_root": "/articles/healthcare-apis/iot/data-flow.md",
593-
"redirect_url": "/azure/healthcare-apis/iot/overview-of-device-message-processing-stages",
593+
"redirect_url": "/azure/healthcare-apis/iot/overview-of-device-data-processing-stages",
594594
"redirect_document_id": false
595595
},
596596
{ "source_path_from_root": "/articles/healthcare-apis/iot/understand-service.md",
597-
"redirect_url": "/azure/healthcare-apis/iot/overview-of-device-message-processing-stages",
597+
"redirect_url": "/azure/healthcare-apis/iot/overview-of-device-data-processing-stages",
598+
"redirect_document_id": false
599+
},
600+
{ "source_path_from_root": "/articles/healthcare-apis/iot/overview-of-device-message-processing-stages.md",
601+
"redirect_url": "/azure/healthcare-apis/iot/overview-of-device-data-processing-stages",
598602
"redirect_document_id": false
599603
},
600604
{ "source_path_from_root": "/articles/healthcare-apis/iot/how-to-use-device-mappings.md",
@@ -606,7 +610,11 @@
606610
"redirect_document_id": false
607611
},
608612
{ "source_path_from_root": "/articles/healthcare-apis/iot/how-to-use-fhir-mappings.md",
609-
"redirect_url": "/azure/healthcare-apis/iot/how-to-configure-fhir-mappings",
613+
"redirect_url": "/azure/healthcare-apis/iot/overview-of-fhir-destination-mapping",
614+
"redirect_document_id": false
615+
},
616+
{ "source_path_from_root": "/articles/healthcare-apis/iot/how-to-configure-fhir-mappings.md",
617+
"redirect_url": "/azure/healthcare-apis/iot/overview-of-fhir-destination-mapping",
610618
"redirect_document_id": false
611619
},
612620
{ "source_path_from_root": "/articles/healthcare-apis/iot/iot-connector-machine-learning.md",
@@ -654,7 +662,11 @@
654662
"redirect_document_id": false
655663
},
656664
{ "source_path_from_root": "/articles/healthcare-apis/iot/how-to-use-iot-jsonpath-content-mappings.md",
657-
"redirect_url": "/azure/healthcare-apis/iot/how-to-use-iotjsonpathcontenttemplate-mappings",
665+
"redirect_url": "/azure/healthcare-apis/iot/how-to-use-iotjsonpathcontent-mappings",
666+
"redirect_document_id": false
667+
},
668+
{ "source_path_from_root": "/articles/healthcare-apis/iot/how-to-use-iotjsonpathcontenttemplate-mappings.md",
669+
"redirect_url": "/azure/healthcare-apis/iot/how-to-use-iotjsonpathcontent-mappings",
658670
"redirect_document_id": false
659671
},
660672
{ "source_path_from_root": "/articles/healthcare-apis/iot/deploy-new-button.md",

.openpublishing.redirection.iot-hub-device-update.json

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4,6 +4,16 @@
44
"source_path_from_root": "/articles/iot-hub-device-update/migration-pp-to-ppr.md",
55
"redirect_url": "/azure/iot-hub-device-update/migration-public-preview-refresh-to-ga",
66
"redirect_document_id": true
7+
},
8+
{
9+
"source_path_from_root": "/articles/iot-hub-device-update/connected-cache-configure.md",
10+
"redirect_url": "/azure/iot-hub-device-update/connected-cache-disconnected-device-update",
11+
"redirect_document_id": false
12+
},
13+
{
14+
"source_path_from_root": "/articles/iot-hub-device-update/connected-cache-industrial-iot-nested.md",
15+
"redirect_url": "/azure/iot-hub-device-update/connected-cache-nested-level",
16+
"redirect_document_id": false
717
}
818
]
919
}

articles/active-directory-b2c/custom-policies-series-call-rest-api.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ In this article, you'll learn how to:
3131

3232
## Scenario overview
3333

34-
In [Create branching in user journey by using Azure AD B2C custom policies](custom-policies-series-branch-user-journey.md), users who select *Personal Account* need to provide a valid invitation access code to proceed. We use a static access code, but real world apps don't work this way. If the service that issues the access codes is external to your custom policy, you must make a call to that service, and pass the access code input by the user for validation. If the access code is valid, the service returns an HTTP 200 (OK) response, and Azure AD B2C issues JWT token. Otherwise, the service returns an HTTP 409 (Conflict) response, and the use must re-enter an access code.
34+
In [Create branching in user journey by using Azure AD B2C custom policies](custom-policies-series-branch-user-journey.md), users who select *Personal Account* need to provide a valid invitation access code to proceed. We use a static access code, but real world apps don't work this way. If the service that issues the access codes is external to your custom policy, you must make a call to that service, and pass the access code input by the user for validation. If the access code is valid, the service returns an HTTP 200 (OK) response, and Azure AD B2C issues JWT token. Otherwise, the service returns an HTTP 409 (Conflict) response, and the user must re-enter an access code.
3535

3636
:::image type="content" source="media/custom-policies-series-call-rest-api/screenshot-of-call-rest-api-call.png" alt-text="A flowchart of calling a R E S T A P I.":::
3737

@@ -88,7 +88,7 @@ You need to deploy an app, which will serve as your external app. Your custom po
8888
"code" : "errorCode",
8989
"requestId": "requestId",
9090
"userMessage" : "The access code you entered is incorrect. Please try again.",
91-
"developerMessage" : `The The provided code ${req.body.accessCode} does not match the expected code for user.`,
91+
"developerMessage" : `The provided code ${req.body.accessCode} does not match the expected code for user.`,
9292
"moreInfo" :"https://docs.microsoft.com/en-us/azure/active-directory-b2c/string-transformations"
9393
};
9494
res.status(409).send(errorResponse);
@@ -133,7 +133,7 @@ You need to deploy an app, which will serve as your external app. Your custom po
133133
"code": "errorCode",
134134
"requestId": "requestId",
135135
"userMessage": "The access code you entered is incorrect. Please try again.",
136-
"developerMessage": "The The provided code 54321 does not match the expected code for user.",
136+
"developerMessage": "The provided code 54321 does not match the expected code for user.",
137137
"moreInfo": "https://docs.microsoft.com/en-us/azure/active-directory-b2c/string-transformations"
138138
}
139139
```
@@ -316,4 +316,4 @@ Next, learn:
316316
317317
- About [RESTful technical profile](restful-technical-profile.md).
318318
319-
- How to [Create and read a user account by using Azure Active Directory B2C custom policy](custom-policies-series-store-user.md)
319+
- How to [Create and read a user account by using Azure Active Directory B2C custom policy](custom-policies-series-store-user.md)

articles/active-directory-b2c/index.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,8 +7,8 @@ summary: >
77
brand: azure
88

99
metadata:
10-
title: Azure Active Directory B2C documentation # Required; page title displayed in search results. Include the brand. < 60 chars.
11-
description: Learn how to use Azure Active Directory B2C to customize and control how customers sign up, sign in, and manage their profiles when using your applications. # Required; article description that is displayed in search results. < 160 chars.
10+
title: Azure Active Directory B2C documentation
11+
description: Learn how to use Azure Active Directory B2C to customize and control how customers sign up, sign in, and manage their profiles when using your applications.
1212
services: active-directory-b2c
1313
ms.service: active-directory
1414
ms.subservice: B2C

articles/active-directory-b2c/quickstart-web-app-dotnet.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ In this quickstart, you use an ASP.NET application to sign in using a social ide
3939
## Run the application in Visual Studio
4040
4141
1. In the sample application project folder, open the **B2C-WebAPI-DotNet.sln** solution in Visual Studio.
42-
1. For this quickstart, you run both the **TaskWebApp** and **TaskService** projects at the same time. Right-click the **B2C-WebAPI-DotNet** solution in Solution Explorer, and then select **Set StartUp Projects**.
42+
1. For this quickstart, you run both the **TaskWebApp** and **TaskService** projects at the same time. Right-click the **B2C-WebAPI-DotNet** solution in Solution Explorer, and then select **Configure StartUp Projects...**.
4343
1. Select **Multiple startup projects** and change the **Action** for both projects to **Start**.
4444
1. Select **OK**.
4545
1. Press **F5** to debug both applications. Each application opens in its own browser tab:

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

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,29 @@ manager: CelesteDG
1515

1616
Welcome to what's new in Azure Active Directory B2C documentation. This article lists new docs that have been added and those that have had significant updates in the last three months. To learn what's new with the B2C service, see [What's new in Azure Active Directory](../active-directory/fundamentals/whats-new.md) and [Azure AD B2C developer release notes](custom-policy-developer-notes.md)
1717

18+
## March 2023
19+
20+
### Updated articles
21+
22+
- [Configure SAML identity provider options with Azure Active Directory B2C](identity-provider-generic-saml-options.md)
23+
- [Tutorial: Configure BioCatch with Azure Active Directory B2C](partner-biocatch.md)
24+
- [Tutorial: Configure Nok Nok Passport with Azure Active Directory B2C for passwordless FIDO2 authentication](partner-nok-nok.md)
25+
- [Pass an identity provider access token to your application in Azure Active Directory B2C](idp-pass-through-user-flow.md)
26+
- [Tutorial: Configure Haventec Authenticate with Azure Active Directory B2C for single-step, multi-factor passwordless authentication](partner-haventec.md)
27+
- [Configure Trusona Authentication Cloud with Azure Active Directory B2C](partner-trusona.md)
28+
- [Tutorial: Configure IDEMIA Mobile ID with Azure Active Directory B2C](partner-idemia.md)
29+
- [Configure Azure Active Directory B2C with Bluink eID-Me for identity verification](partner-eid-me.md)
30+
- [Tutorial: Configure Azure Active Directory B2C with BlokSec for passwordless authentication](partner-bloksec.md)
31+
- [Tutorial: Configure Azure Active Directory B2C with Azure Web Application Firewall](partner-azure-web-application-firewall.md)
32+
- [Tutorial to configure Saviynt with Azure Active Directory B2C](partner-saviynt.md)
33+
- [Tutorial: Configure Keyless with Azure Active Directory B2C](partner-keyless.md)
34+
- [Tutorial: Configure security analytics for Azure Active Directory B2C data with Microsoft Sentinel](azure-sentinel.md)
35+
- [Configure authentication in a sample Python web app by using Azure AD B2C](configure-authentication-sample-python-web-app.md)
36+
- [Billing model for Azure Active Directory B2C](billing.md)
37+
- [Azure Active Directory B2C: Region availability & data residency](data-residency.md)
38+
- ['Azure AD B2C: Frequently asked questions (FAQ)'](faq.yml)
39+
- [Tutorial: Create an Azure Active Directory B2C tenant](tutorial-create-tenant.md)
40+
1841
## February 2023
1942

2043
### Updated articles

0 commit comments

Comments
 (0)