Skip to content

Commit 624af60

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into fhir-destination-mapping-updates
2 parents 4b7b817 + 61c09bc commit 624af60

File tree

3,547 files changed

+50521
-22378
lines changed

Some content is hidden

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

3,547 files changed

+50521
-22378
lines changed

.openpublishing.redirection.active-directory.json

Lines changed: 14 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -60,6 +60,11 @@
6060
"redirect_url": "/azure/active-directory/saas-apps/atlassian-cloud-tutorial",
6161
"redirect_document_id": false
6262
},
63+
{
64+
"source_path_from_root": "/articles/active-directory/saas-apps/easy-metrics-auth0-connector-tutorial.md",
65+
"redirect_url": "/azure/active-directory/saas-apps/easy-metrics-connector-tutorial",
66+
"redirect_document_id": false
67+
},
6368
{
6469
"source_path_from_root": "/articles/active-directory/saas-apps/iauditor-tutorial.md",
6570
"redirect_url": "/azure/active-directory/saas-apps/safety-culture-tutorial",
@@ -135,7 +140,7 @@
135140
"redirect_url": "/azure/active-directory/saas-apps/f5-big-ip-headers-easy-button",
136141
"redirect_document_id": false
137142
},
138-
{
143+
{
139144
"source_path_from_root": "/articles/active-directory/saas-apps/tripactions-tutorial.md",
140145
"redirect_url": "/azure/active-directory/saas-apps/navan-tutorial",
141146
"redirect_document_id": false
@@ -7229,7 +7234,7 @@
72297234
{
72307235
"source_path_from_root": "/articles/active-directory/active-directory-privileged-identity-management-how-to-add-role-to-user.md",
72317236
"redirect_url": "/azure/active-directory/privileged-identity-management/pim-how-to-add-role-to-user",
7232-
"redirect_document_id": true
7237+
"redirect_document_id": false
72337238
},
72347239
{
72357240
"source_path_from_root": "/articles/active-directory/active-directory-privileged-identity-management-how-to-change-default-settings.md",
@@ -7546,6 +7551,11 @@
75467551
"redirect_url": "/azure/active-directory/roles/view-assignments",
75477552
"redirect_document_id": false
75487553
},
7554+
{
7555+
"source_path_from_root": "/articles/active-directory/roles/groups-pim-eligible.md",
7556+
"redirect_url": "/azure/active-directory/privileged-identity-management/pim-how-to-add-role-to-user",
7557+
"redirect_document_id": true
7558+
},
75497559
{
75507560
"source_path_from_root": "/articles/active-directory/users-groups-roles/directory-administrative-units.md",
75517561
"redirect_url": "/azure/active-directory/roles/administrative-units",
@@ -7663,8 +7673,8 @@
76637673
},
76647674
{
76657675
"source_path_from_root": "/articles/active-directory/users-groups-roles/roles-groups-pim-eligible.md",
7666-
"redirect_url": "/azure/active-directory/roles/groups-pim-eligible",
7667-
"redirect_document_id": true
7676+
"redirect_url": "/azure/active-directory/privileged-identity-management/pim-how-to-add-role-to-user",
7677+
"redirect_document_id": false
76687678
},
76697679
{
76707680
"source_path_from_root": "/articles/active-directory/users-groups-roles/roles-groups-remove-assignment.md",

.openpublishing.redirection.azure-monitor.json

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -45,6 +45,26 @@
4545
"redirect_url": "/azure/azure-monitor/app/app-insights-overview",
4646
"redirect_document_id": false
4747
},
48+
{
49+
"source_path_from_root": "/articles/azure-monitor/app/tutorial-runtime-exceptions.md",
50+
"redirect_url": "/previous-versions/azure/azure-monitor/app/tutorial-runtime-exceptions",
51+
"redirect_document_id": false
52+
},
53+
{
54+
"source_path_from_root": "/articles/azure-monitor/app/tutorial-performance.md",
55+
"redirect_url": "/previous-versions/azure/azure-monitor/app/tutorial-performance",
56+
"redirect_document_id": false
57+
},
58+
{
59+
"source_path_from_root": "/articles/azure-monitor/app/tutorial-users.md",
60+
"redirect_url": "/previous-versions/azure/azure-monitor/app/tutorial-users",
61+
"redirect_document_id": false
62+
},
63+
{
64+
"source_path_from_root": "/articles/azure-monitor/app/custom-data-correlation.md",
65+
"redirect_url": "/previous-versions/azure/azure-monitor/app/custom-data-correlation",
66+
"redirect_document_id": false
67+
},
4868
{
4969
"source_path_from_root": "/articles/azure-monitor/app/correlation.md",
5070
"redirect_url": "/previous-versions/azure/azure-monitor/app/distributed-tracing-telemetry-correlation",

.openpublishing.redirection.azure-resource-manager.json

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1919,6 +1919,11 @@
19191919
"source_path_from_root": "/articles/azure-resource-manager/managed-applications/scripts/managed-application-powershell-sample-get-managed-group-resize-vm.md",
19201920
"redirect_url": "/azure/azure-resource-manager/managed-applications/overview",
19211921
"redirect_document_id": false
1922-
}
1922+
},
1923+
{
1924+
"source_path_from_root": "/articles/governance/policy/tutorials/policy-as-code-github.md",
1925+
"redirect_url": "/azure/governance/policy/concepts/policy-as-code",
1926+
"redirect_document_id": false
1927+
}
19231928
]
19241929
}

.openpublishing.redirection.healthcare-apis.json

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -658,7 +658,11 @@
658658
"redirect_document_id": false
659659
},
660660
{ "source_path_from_root": "/articles/healthcare-apis/iot/how-to-use-iot-jsonpath-content-mappings.md",
661-
"redirect_url": "/azure/healthcare-apis/iot/how-to-use-iotjsonpathcontenttemplate-mappings",
661+
"redirect_url": "/azure/healthcare-apis/iot/how-to-use-iotjsonpathcontent-mappings",
662+
"redirect_document_id": false
663+
},
664+
{ "source_path_from_root": "/articles/healthcare-apis/iot/how-to-use-iotjsonpathcontenttemplate-mappings.md",
665+
"redirect_url": "/azure/healthcare-apis/iot/how-to-use-iotjsonpathcontent-mappings",
662666
"redirect_document_id": false
663667
},
664668
{ "source_path_from_root": "/articles/healthcare-apis/iot/deploy-new-button.md",

.openpublishing.redirection.json

Lines changed: 11 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,10 @@
11
{
22
"redirections": [
3+
{
4+
"source_path": "articles/route-server/routing-preference.md",
5+
"redirect_url": "/azure/route-server/overview",
6+
"redirect_document_id": false
7+
},
38
{
49
"source_path": "articles/storage/queues/storage-ruby-how-to-use-queue-storage.md",
510
"redirect_url": "/previous-versions/azure/storage/queues/storage-ruby-how-to-use-queue-storage",
@@ -22522,7 +22527,11 @@
2252222527
"source_path_from_root": "/articles/sentinel/data-connectors/microsoft-defender-threat-intelligence.md",
2252322528
"redirect_url": "/azure/sentinel/understand-threat-intelligence",
2252422529
"redirect_document_id": false
22525-
}
22526-
22530+
},
22531+
{
22532+
"source_path_from_root": "/articles/principles-for-ai-generated-content.md",
22533+
"redirect_url": "https://aka.ms/ai-content-principles",
22534+
"redirect_document_id": false
22535+
}
2252722536
]
2252822537
}

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

Lines changed: 2 additions & 2 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

@@ -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/custom-policies-series-hello-world.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -143,8 +143,10 @@ If you haven't already done so, create the following encryption keys. To automat
143143

144144
```xml
145145
<UserJourney Id="HelloWorldJourney">
146-
<OrchestrationStep Order="1" Type="SendClaims" CpimIssuerTechnicalProfileReferenceId="JwtIssuer" />
147-
</UserJourney>
146+
<OrchestrationSteps>
147+
<OrchestrationStep Order="1" Type="SendClaims" CpimIssuerTechnicalProfileReferenceId="JwtIssuer" />
148+
</OrchestrationSteps>
149+
</UserJourney>
148150
```
149151

150152
We've added a [UserJourney](userjourneys.md). The user journey specifies the business logic the end user goes through as Azure AD B2C processes a request. This user journey has only one step that issues a JTW token with the claims that you'll define in the next step.

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/manage-custom-policies-powershell.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,7 @@ manager: CelesteDG
77

88
ms.service: active-directory
99
ms.workload: identity
10+
ms.custom: devx-track-azurepowershell
1011
ms.topic: how-to
1112
ms.date: 02/14/2020
1213
ms.author: kengaderdus
-4.51 KB
Loading

0 commit comments

Comments
 (0)