Skip to content

Commit 371cea9

Browse files
authored
Merge branch 'MicrosoftDocs:main' into Broken-link-fix-dominicbetts
2 parents 9079db2 + a7e548f commit 371cea9

File tree

2,549 files changed

+35158
-21972
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,549 files changed

+35158
-21972
lines changed

.openpublishing.publish.config.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -755,7 +755,7 @@
755755
{
756756
"path_to_root": "azure-spring-apps-reference-architecture",
757757
"url": "https://github.com/Azure/azure-spring-apps-reference-architecture",
758-
"branch": "main",
758+
"branch": "reference-architecture",
759759
"branch_mapping": {}
760760
},
761761
{

.openpublishing.redirection.active-directory.json

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1942,8 +1942,8 @@
19421942
},
19431943
{
19441944
"source_path_from_root": "/articles/active-directory/active-directory-b2b-add-user-without-invite.md",
1945-
"redirect_url": "/azure/active-directory/b2b/add-user-without-invite",
1946-
"redirect_document_id": true
1945+
"redirect_url": "/azure/active-directory/external-identities/redemption-experience",
1946+
"redirect_document_id": false
19471947
},
19481948
{
19491949
"source_path_from_root": "/articles/active-directory/active-directory-b2b-allow-deny-list.md",
@@ -3908,8 +3908,8 @@
39083908
},
39093909
{
39103910
"source_path_from_root": "/articles/active-directory/b2b/add-user-without-invite.md",
3911-
"redirect_url": "/azure/active-directory/external-identities/add-user-without-invite",
3912-
"redirect_document_id": true
3911+
"redirect_url": "/azure/active-directory/external-identities/redemption-experience",
3912+
"redirect_document_id": false
39133913
},
39143914
{
39153915
"source_path_from_root": "/articles/active-directory/b2b/allow-deny-list.md",
@@ -4089,7 +4089,7 @@
40894089
{
40904090
"source_path_from_root": "/articles/active-directory/b2b/redemption-experience.md",
40914091
"redirect_url": "/azure/active-directory/external-identities/redemption-experience",
4092-
"redirect_document_id": true
4092+
"redirect_document_id": false
40934093
},
40944094
{
40954095
"source_path_from_root": "/articles/active-directory/b2b/self-service-portal.md",

.openpublishing.redirection.defender-for-iot.json

Lines changed: 15 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,19 @@
11
{
22
"redirections": [
3+
{
4+
"source_path_from_root": "/articles/defender-for-iot/organizations/resources-training-sessions.md",
5+
"redirect_url": "https://techcommunity.microsoft.com/t5/microsoft-defender-for-iot-blog/microsoft-defender-for-iot-ninja-training/ba-p/2428899",
6+
"redirect_document_id": false
7+
},
8+
{
9+
"source_path_from_root": "/articles/defender-for-iot/organizations/how-to-manage-the-alert-event.md",
10+
"redirect_url": "/azure/defender-for-iot/organizations/how-to-view-alerts",
11+
"redirect_document_id": false
12+
},
13+
{ "source_path_from_root": "/articles/defender-for-iot/organizations/how-to-install-software.md",
14+
"redirect_url": "/azure/defender-for-iot/organizations/ot-deploy/install-software-ot-sensor",
15+
"redirect_document_id": false
16+
},
317
{
418
"source_path_from_root": "/articles/defender-for-iot/organizations/how-to-create-and-manage-users.md",
519
"redirect_url": "/azure/defender-for-iot/organizations/manage-users-overview",
@@ -117,7 +131,7 @@
117131
},
118132
{
119133
"source_path_from_root": "/articles/defender-for-iot/how-to-install-software.md",
120-
"redirect_url": "/azure/defender-for-iot/organizations/how-to-install-software",
134+
"redirect_url": "/azure/defender-for-iot/organizations/ot-deploy/install-software-ot-sensor",
121135
"redirect_document_id": false
122136
},
123137
{

.openpublishing.redirection.healthcare-apis.json

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -625,6 +625,18 @@
625625
"redirect_url": "/azure/healthcare-apis/iot/git-projects",
626626
"redirect_document_id": false
627627
},
628+
{ "source_path_from_root": "/articles/healthcare-apis/iot/how-to-use-calculated-functions-mappings.md",
629+
"redirect_url": "/azure/healthcare-apis/iot/how-to-use-calculatedcontenttemplate-mappings",
630+
"redirect_document_id": false
631+
},
632+
{ "source_path_from_root": "/articles/healthcare-apis/iot/how-to-use-iot-jsonpath-content-mappings.md",
633+
"redirect_url": "/azure/healthcare-apis/iot/how-to-use-iotjsonpathcontenttemplate-mappings",
634+
"redirect_document_id": false
635+
},
636+
{ "source_path_from_root": "/articles/healthcare-apis/iot/deploy-new-button.md",
637+
"redirect_url": "/azure/healthcare-apis/iot/deploy-new-arm",
638+
"redirect_document_id": false
639+
},
628640
{ "source_path_from_root": "/articles/healthcare-apis/events/events-display-metrics.md",
629641
"redirect_url": "/azure/healthcare-apis/events/events-use-metrics",
630642
"redirect_document_id": false

.openpublishing.redirection.json

Lines changed: 97 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1163,6 +1163,11 @@
11631163
"redirect_url": "/azure",
11641164
"redirect_document_id": false
11651165
},
1166+
{
1167+
"source_path_from_root": "/articles/active-directory/external-identities/add-user-without-invite.md",
1168+
"redirect_url": "/azure/active-directory/external-identities/redemption-experience",
1169+
"redirect_document_id": true
1170+
},
11661171
{
11671172
"source_path_from_root": "/articles/active-directory-b2c/active-directory-b2c-landing-custom.md",
11681173
"redirect_url": "/azure/active-directory-b2c",
@@ -5988,6 +5993,11 @@
59885993
"redirect_url": "/azure/automation/create-azure-automation-account-portal",
59895994
"redirect_document_id": false
59905995
},
5996+
{
5997+
"source_path_from_root": "/articles/automation/automation-solution-vm-management-enable.md",
5998+
"redirect_url": "/azure/automation/automation-solution-vm-management",
5999+
"redirect_document_id": false
6000+
},
59916001
{
59926002
"source_path_from_root": "/articles/update-center/enable-machines.md",
59936003
"redirect_url": "/azure/update-center/updates-maintenance-schedules",
@@ -14758,6 +14768,12 @@
1475814768
"redirect_url": "/azure/load-balancer/load-balancer-security-controls",
1475914769
"redirect_document_id": false
1476014770
},
14771+
{
14772+
"source_path_from_root": "/articles/load-balancer/update-load-balancer-with-vm-scale-set.md",
14773+
"redirect_url": "/azure/load-balancer/configure-inbound-nat-rules-vm-scale-set",
14774+
"redirect_document_id": false
14775+
},
14776+
1476114777
{
1476214778
"source_path_from_root": "/articles/load-balancer/load-balancer-get-started-internet-arm-cli.md",
1476314779
"redirect_url": "/azure/load-balancer/quickstart-create-basic-load-balancer-cli",
@@ -18328,6 +18344,16 @@
1832818344
"redirect_url": "/azure/sentinel/enable-monitoring",
1832918345
"redirect_document_id": false
1833018346
},
18347+
{
18348+
"source_path_from_root": "/articles/sentinel/dns-normalization-schema.md",
18349+
"redirect_url": "/azure/sentinel/normalization-schema-dns",
18350+
"redirect_document_id": true
18351+
},
18352+
{
18353+
"source_path_from_root": "/articles/sentinel/file-event-normalization-schema.md",
18354+
"redirect_url": "/azure/sentinel/normalization-schema-file-event",
18355+
"redirect_document_id": true
18356+
},
1833118357
{
1833218358
"source_path_from_root": "/articles/service-bus/index.md",
1833318359
"redirect_url": "/azure/service-bus-messaging/index",
@@ -27747,7 +27773,77 @@
2774727773
"source_path_from_root": "/articles/virtual-machines/workloads/sap/sap-high-availability-multi-sid.md",
2774827774
"redirect_url": "/azure/virtual-machines/workloads/sap/sap-ascs-ha-multi-sid-wsfc-shared-disk",
2774927775
"redirect_document_id": false
27750-
},
27776+
},
27777+
{
27778+
"source_path_from_root": "/articles/virtual-machines/workloads/sap/dbms_guide_sapase.md",
27779+
"redirect_url": "/azure/virtual-machines/workloads/sap/dbms-guide-sapase",
27780+
"redirect_document_id": false
27781+
},
27782+
{
27783+
"source_path_from_root": "/articles/virtual-machines/workloads/sap/dbms_guide_general.md",
27784+
"redirect_url": "/azure/virtual-machines/workloads/sap/dbms-guide-general",
27785+
"redirect_document_id": false
27786+
},
27787+
{
27788+
"source_path_from_root": "/articles/virtual-machines/workloads/sap/dbms_guide_ibm.md",
27789+
"redirect_url": "/azure/virtual-machines/workloads/sap/dbms-guide-ibm",
27790+
"redirect_document_id": false
27791+
},
27792+
{
27793+
"source_path_from_root": "/articles/virtual-machines/workloads/sap/dbms_guide_maxdb.md",
27794+
"redirect_url": "/azure/virtual-machines/workloads/sap/dbms-guide-maxdb",
27795+
"redirect_document_id": false
27796+
},
27797+
{
27798+
"source_path_from_root": "/articles/virtual-machines/workloads/sap/dbms_guide_oracle.md",
27799+
"redirect_url": "/azure/virtual-machines/workloads/sap/dbms-guide-oracle",
27800+
"redirect_document_id": false
27801+
},
27802+
{
27803+
"source_path_from_root": "/articles/virtual-machines/workloads/sap/dbms_guide_sqlserver.md",
27804+
"redirect_url": "/azure/virtual-machines/workloads/sap/dbms-guide-sqlserver",
27805+
"redirect_document_id": false
27806+
},
27807+
{
27808+
"source_path_from_root": "/articles/virtual-machines/workloads/sap/sap-supported-product-on-azure.md",
27809+
"redirect_url": "/azure/virtual-machines/workloads/sap/supported-product-on-azure",
27810+
"redirect_document_id": false
27811+
},
27812+
{
27813+
"source_path_from_root": "/articles/virtual-machines/workloads/sap/sap-rise-integration.md",
27814+
"redirect_url": "/azure/virtual-machines/workloads/sap/rise-integration",
27815+
"redirect_document_id": false
27816+
},
27817+
{
27818+
"source_path_from_root": "/articles/virtual-machines/workloads/sap/sap-proximity-placement-scenarios.md",
27819+
"redirect_url": "/azure/virtual-machines/workloads/sap/proximity-placement-scenarios",
27820+
"redirect_document_id": false
27821+
},
27822+
{
27823+
"source_path_from_root": "/articles/virtual-machines/workloads/sap/sap-planning-supported-configurations.md",
27824+
"redirect_url": "/azure/virtual-machines/workloads/sap/planning-supported-configurations",
27825+
"redirect_document_id": false
27826+
},
27827+
{
27828+
"source_path_from_root": "/articles/virtual-machines/workloads/sap/sap-iq-deployment-guide.md",
27829+
"redirect_url": "/azure/virtual-machines/workloads/sap/dbms-guide-sapiq",
27830+
"redirect_document_id": false
27831+
},
27832+
{
27833+
"source_path_from_root": "/articles/virtual-machines/workloads/sap/sap-certifications.md",
27834+
"redirect_url": "/azure/virtual-machines/workloads/sap/certifications",
27835+
"redirect_document_id": false
27836+
},
27837+
{
27838+
"source_path_from_root": "/articles/virtual-machines/workloads/sap/sap-ha-availability-zones.md",
27839+
"redirect_url": "/azure/virtual-machines/workloads/sap/high-availability-zones",
27840+
"redirect_document_id": false
27841+
},
27842+
{
27843+
"source_path_from_root": "/articles/virtual-machines/workloads/sap/sap-deployment-checklist.md",
27844+
"redirect_url": "/azure/virtual-machines/workloads/sap/deployment-checklist",
27845+
"redirect_document_id": false
27846+
},
2775127847
{
2775227848
"source_path_from_root": "/articles/migrate/how-to-scale-assessment.md",
2775327849
"redirect_url": "scale-hyper-v-assessment",

articles/active-directory-b2c/TOC.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -70,13 +70,13 @@
7070
items:
7171
- name: Global identity solutions
7272
href: azure-ad-b2c-global-identity-solutions.md
73-
- name: Funnel-based design considerations
73+
- name: Funnel-based design
7474
href: azure-ad-b2c-global-identity-funnel-based-design.md
75-
- name: Region-based design considerations
75+
- name: Region-based design
7676
href: azure-ad-b2c-global-identity-region-based-design.md
7777
- name: Funnel-based proof of concept
7878
href: azure-ad-b2c-global-identity-proof-of-concept-funnel.md
79-
- name: Regional-based proof of concept
79+
- name: Region-based proof of concept
8080
href: azure-ad-b2c-global-identity-proof-of-concept-regional.md
8181
- name: Azure AD B2C best practices
8282
href: best-practices.md

articles/active-directory-b2c/add-api-connector.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: active-directory-b2c
55
ms.service: active-directory
66
ms.subservice: B2C
77
ms.topic: how-to
8-
ms.date: 11/09/2021
8+
ms.date: 12/20/2022
99

1010
ms.author: kengaderdus
1111
author: kengaderdus
@@ -16,6 +16,8 @@ zone_pivot_groups: b2c-policy-type
1616

1717
# Add an API connector to a sign-up user flow
1818

19+
[!INCLUDE [active-directory-b2c-choose-user-flow-or-custom-policy](../../includes/active-directory-b2c-choose-user-flow-or-custom-policy.md)]
20+
1921
As a developer or IT administrator, you can use API connectors to integrate your sign-up user flows with REST APIs to customize the sign-up experience and integrate with external systems. At the end of this walkthrough, you'll be able to create an Azure AD B2C user flow that interacts with [REST API services](api-connectors-overview.md) to modify your sign-up experiences.
2022

2123
::: zone pivot="b2c-user-flow"

articles/active-directory-b2c/azure-ad-b2c-global-identity-funnel-based-design.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -22,14 +22,14 @@ The designs account for:
2222

2323
* Local Account sign up and sign in
2424
* Federated account sign up and sign in
25-
* Authenticating local accounts for users signing in from outside their registered region, supported by cross tenant API based authentication.
25+
* Authenticating local accounts for users signing in from outside their registered region, supported by cross tenant API based authentication
2626
* Authenticating federated accounts for users signing in from outside their registered region, supported by cross tenant API based look up
2727
* Prevents sign up from multiple different regions
2828
* Applications in each region have a single endpoint to connect with
2929

3030
## Local account sign-in use cases
3131

32-
The following use cases are typical in a global Azure AD B2C environment. The local account use cases also cover accounts where the user travels. Each provides a diagram and workflow steps for each use case.
32+
The following use cases are typical in a global Azure AD B2C environment. The local account use cases also cover accounts where the user travels. We provide a diagram and workflow steps for each use case.
3333

3434
### Local user sign-up
3535

@@ -99,8 +99,7 @@ This use case demonstrates how a user can travel across regions and maintain the
9999

100100
1. The EMEA Azure AD B2C tenant performs an Azure AD ROPC flow against the NOAM Azure AD B2C tenant to verify credentials.
101101
>[!NOTE]
102-
>This call will also fetch a token for the user to perform a Graph API call.
103-
The EMEA Azure AD B2C tenant performs a Graph API call to the NOAM Azure AD B2C tenant to fetch the user's profile. This call is authenticated by the access token for Graph API acquired in the last step.
102+
>This call will also fetch a token for the user to perform a Graph API call. The EMEA Azure AD B2C tenant performs a Graph API call to the NOAM Azure AD B2C tenant to fetch the user's profile. This call is authenticated by the access token for Graph API acquired in the last step.
104103
105104
1. The regional tenant issues a token back to the funnel tenant.
106105

@@ -312,6 +311,6 @@ This use case demonstrates how non-local users are able to perform account linki
312311

313312
- [Build a global identity solution with region-based approach](azure-ad-b2c-global-identity-region-based-design.md)
314313

315-
- [Azure AD B2C global identity proof of concept regional-based configuration](azure-ad-b2c-global-identity-proof-of-concept-regional.md)
314+
- [Azure AD B2C global identity proof of concept region-based configuration](azure-ad-b2c-global-identity-proof-of-concept-regional.md)
316315

317316
- [Azure AD B2C global identity proof of concept funnel-based configuration](azure-ad-b2c-global-identity-proof-of-concept-funnel.md)

articles/active-directory-b2c/azure-ad-b2c-global-identity-proof-of-concept-regional.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Azure Active Directory B2C global identity framework proof of concept for regional based configuration
2+
title: Azure Active Directory B2C global identity framework proof of concept for region-based configuration
33
description: Learn how to create a proof of concept regional based approach for Azure AD B2C to provide customer identity and access management for global customers.
44
services: active-directory-b2c
55
author: gargi-sinha
@@ -13,11 +13,11 @@ ms.author: gasinh
1313
ms.subservice: B2C
1414
---
1515

16-
# Azure Active Directory B2C global identity framework proof of concept regional based configuration
16+
# Azure Active Directory B2C global identity framework proof of concept for region-based configuration
1717

18-
The following section describes how to create proof of concept implementations for regional-based orchestration. The completed Azure Active Directory B2C (Azure AD B2C) custom policies can be found [here](https://github.com/azure-ad-b2c/samples/tree/master/policies/global-architecture-model/region-based-approach).
18+
The following section describes how to create proof of concept implementations for region-based orchestration. The completed Azure Active Directory B2C (Azure AD B2C) custom policies can be found [here](https://github.com/azure-ad-b2c/samples/tree/master/policies/global-architecture-model/region-based-approach).
1919

20-
## Regional-based approach
20+
## Region-based approach
2121

2222
Each regional Azure AD B2C tenant will require an Azure AD B2C Custom policy, which contains the following capabilities:
2323

0 commit comments

Comments
 (0)