Skip to content

Commit 2655904

Browse files
authored
Merge branch 'main' into refresh-functions-articles-3
2 parents 9b3a1a7 + 10a39a9 commit 2655904

File tree

3,836 files changed

+55500
-42208
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,836 files changed

+55500
-42208
lines changed

.openpublishing.redirection.json

Lines changed: 184 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,154 @@
11
{
22
"redirections": [
3+
{
4+
"source_path": "articles/cdn/edgio-retirement-faq.md",
5+
"redirect_url": "/previous-versions/azure/cdn/edgio-retirement-faq",
6+
"redirect_document_id": false
7+
},
8+
{
9+
"source_path": "articles/cdn/cdn-edge-performance.md",
10+
"redirect_url": "/previous-versions/azure/cdn/cdn-edge-performance",
11+
"redirect_document_id": false
12+
},
13+
{
14+
"source_path": "articles/cdn/migrate-cdn-to-front-door-retain-edge-domain.md",
15+
"redirect_url": "/previous-versions/azure/cdn/migrate-cdn-to-front-door-retain-edge-domain",
16+
"redirect_document_id": false
17+
},
18+
{
19+
"source_path": "articles/internet-peering/howto-subscription-association-powershell.md",
20+
"redirect_url": "/previous-versions/azure/internet-peering/howto-subscription-association-powershell",
21+
"redirect_document_id": false
22+
},
23+
{
24+
"source_path": "articles/internet-peering/howto-peering-service-powershell.md",
25+
"redirect_url": "/previous-versions/azure/internet-peering/howto-peering-service-powershell",
26+
"redirect_document_id": false
27+
},
28+
{
29+
"source_path": "articles/internet-peering/howto-direct-powershell.md",
30+
"redirect_url": "/previous-versions/azure/internet-peering/howto-direct-powershell",
31+
"redirect_document_id": false
32+
},
33+
{
34+
"source_path": "articles/internet-peering/howto-legacy-direct-powershell.md",
35+
"redirect_url": "/previous-versions/azure/internet-peering/howto-legacy-direct-powershell",
36+
"redirect_document_id": false
37+
},
38+
{
39+
"source_path": "articles/internet-peering/howto-exchange-powershell.md",
40+
"redirect_url": "/previous-versions/azure/internet-peering/howto-exchange-powershell",
41+
"redirect_document_id": false
42+
},
43+
{
44+
"source_path": "articles/internet-peering/howto-legacy-exchange-powershell.md",
45+
"redirect_url": "/previous-versions/azure/internet-peering/howto-legacy-exchange-powershell",
46+
"redirect_document_id": false
47+
},
48+
{
49+
"source_path": "articles/databox-online/azure-stack-edge-overview.md",
50+
"redirect_url": "/previous-versions/azure/databox-online/azure-stack-edge-overview",
51+
"redirect_document_id": false
52+
},
53+
{
54+
"source_path": "articles/databox-online/azure-stack-edge-deploy-prep.md",
55+
"redirect_url": "/previous-versions/azure/databox-online/azure-stack-edge-deploy-prep",
56+
"redirect_document_id": false
57+
},
58+
{
59+
"source_path": "articles/databox-online/azure-stack-edge-deploy-install.md",
60+
"redirect_url": "/previous-versions/azure/databox-online/azure-stack-edge-deploy-install",
61+
"redirect_document_id": false
62+
},
63+
{
64+
"source_path": "articles/databox-online/azure-stack-edge-deploy-connect-setup-activate.md",
65+
"redirect_url": "/previous-versions/azure/databox-online/azure-stack-edge-deploy-connect-setup-activate",
66+
"redirect_document_id": false
67+
},
68+
{
69+
"source_path": "articles/databox-online/azure-stack-edge-deploy-add-shares.md",
70+
"redirect_url": "/previous-versions/azure/databox-online/azure-stack-edge-deploy-add-shares",
71+
"redirect_document_id": false
72+
},
73+
{
74+
"source_path": "articles/databox-online/azure-stack-edge-deploy-configure-compute-advanced.md",
75+
"redirect_url": "/previous-versions/azure/databox-online/azure-stack-edge-deploy-configure-compute-advanced",
76+
"redirect_document_id": false
77+
},
78+
{
79+
"source_path": "articles/databox-online/azure-stack-edge-deploy-configure-compute.md",
80+
"redirect_url": "/previous-versions/azure/databox-online/azure-stack-edge-deploy-configure-compute",
81+
"redirect_document_id": false
82+
},
83+
{
84+
"source_path": "articles/databox-online/azure-stack-edge-system-requirements.md",
85+
"redirect_url": "/previous-versions/azure/databox-online/azure-stack-edge-system-requirements",
86+
"redirect_document_id": false
87+
},
88+
{
89+
"source_path": "articles/databox-online/azure-stack-edge-technical-specifications-compliance.md",
90+
"redirect_url": "/previous-versions/azure/databox-online/azure-stack-edge-technical-specifications-compliance",
91+
"redirect_document_id": false
92+
},
93+
{
94+
"source_path": "articles/databox-online/azure-stack-edge-create-iot-edge-module.md",
95+
"redirect_url": "/previous-versions/azure/databox-online/azure-stack-edge-create-iot-edge-module",
96+
"redirect_document_id": false
97+
},
98+
{
99+
"source_path": "articles/databox-online/azure-stack-edge-manage-compute.md",
100+
"redirect_url": "/previous-versions/azure/databox-online/azure-stack-edge-manage-compute",
101+
"redirect_document_id": false
102+
},
103+
{
104+
"source_path": "articles/databox-online/azure-stack-edge-manage-shares.md",
105+
"redirect_url": "/previous-versions/azure/databox-online/azure-stack-edge-manage-shares",
106+
"redirect_document_id": false
107+
},
108+
{
109+
"source_path": "articles/databox-online/azure-stack-edge-manage-users.md",
110+
"redirect_url": "/previous-versions/azure/databox-online/azure-stack-edge-manage-users",
111+
"redirect_document_id": false
112+
},
113+
{
114+
"source_path": "articles/databox-online/azure-stack-edge-manage-bandwidth-schedules.md",
115+
"redirect_url": "/previous-versions/azure/databox-online/azure-stack-edge-manage-bandwidth-schedules",
116+
"redirect_document_id": false
117+
},
118+
{
119+
"source_path": "articles/databox-online/azure-stack-edge-manage-access-power-connectivity-mode.md",
120+
"redirect_url": "/previous-versions/azure/databox-online/azure-stack-edge-manage-access-power-connectivity-mode",
121+
"redirect_document_id": false
122+
},
123+
{
124+
"source_path": "articles/databox-online/azure-stack-edge-troubleshoot.md",
125+
"redirect_url": "/previous-versions/azure/databox-online/azure-stack-edge-troubleshoot",
126+
"redirect_document_id": false
127+
},
128+
{
129+
"source_path": "articles/databox-online/azure-stack-edge-troubleshoot-iot-edge.md",
130+
"redirect_url": "/previous-versions/azure/databox-online/azure-stack-edge-troubleshoot-iot-edge",
131+
"redirect_document_id": false
132+
},
133+
{
134+
"source_path": "articles/databox-online/azure-stack-edge-migrate-fpga-gpu.md",
135+
"redirect_url": "/previous-versions/azure/databox-online/azure-stack-edge-migrate-fpga-gpu",
136+
"redirect_document_id": false
137+
},
138+
{
139+
"source_path": "articles/databox-online/azure-stack-edge-2101-release-notes.md",
140+
"redirect_url": "/previous-versions/azure/databox-online/azure-stack-edge-2101-release-notes",
141+
"redirect_document_id": false
142+
},
143+
{
144+
"source_path": "articles/databox-online/azure-stack-edge-2301-release-notes.md",
145+
"redirect_url": "/previous-versions/azure/databox-online/azure-stack-edge-2301-release-notes",
146+
},
147+
{
148+
"source_path": "articles/network-watcher/nsg-flow-logs-rest.md",
149+
"redirect_url": "/previous-versions/azure/network-watcher/nsg-flow-logs-rest",
150+
"redirect_document_id": false
151+
},
3152
{
4153
"source_path": "articles/automation/update-management/configure-alerts.md",
5154
"redirect_url": "/azure/update-manager/manage-alerts",
@@ -2715,6 +2864,11 @@
27152864
"redirect_url": "/azure/bastion/bastion-connect-vm-ssh-linux",
27162865
"redirect_document_id": false
27172866
},
2867+
{
2868+
"source_path_from_root": "/articles/bastion/quickstart-developer-sku.md",
2869+
"redirect_url": "/azure/bastion/quickstart-developer",
2870+
"redirect_document_id": false
2871+
},
27182872
{
27192873
"source_path_from_root": "/articles/bastion/bastion-connect-vm-rdp.md",
27202874
"redirect_url": "/azure/bastion/bastion-connect-vm-rdp-windows",
@@ -3255,6 +3409,16 @@
32553409
"redirect_url": "/azure/databox/data-box-quickstart-export?pivots=dbx-ng",
32563410
"redirect_document_id": false
32573411
},
3412+
{
3413+
"source_path_from_root": "/articles/databox/data-box-next-gen-safety.md",
3414+
"redirect_url": "/azure/databox/data-box-safety?pivots=dbx-ng",
3415+
"redirect_document_id": false
3416+
},
3417+
{
3418+
"source_path_from_root": "/articles/databox/data-box-next-gen-security.md",
3419+
"redirect_url": "/azure/databox/data-box-security?pivots=dbx-ng",
3420+
"redirect_document_id": false
3421+
},
32583422
{
32593423
"source_path_from_root": "/articles/ddos-protection/ddos-disaster-recovery-guidance.md",
32603424
"redirect_url": "../reliability/reliability-ddos.md",
@@ -6185,6 +6349,16 @@
61856349
"redirect_url": "/azure/virtual-network/vnet-integration-for-azure-services",
61866350
"redirect_document_id": false
61876351
},
6352+
{
6353+
"source_path_from_root": "/articles/reliability/availability-zones-region-support.md",
6354+
"redirect_url": "/azure/reliability/regions-list",
6355+
"redirect_document_id": false
6356+
},
6357+
{
6358+
"source_path_from_root": "/articles/cyclecloud/how-to/ccws/cleanup-roles.md",
6359+
"redirect_url": "/azure/cyclecloud/how-to/ccws/deploy-with-cli",
6360+
"redirect_document_id": false
6361+
},
61886362
{
61896363
"source_path": "articles/cloud-services/applications-dont-support-tls-1-2.md",
61906364
"redirect_url": "/previous-versions/azure/cloud-services/applications-dont-support-tls-1-2",
@@ -6509,6 +6683,16 @@
65096683
"source_path": "articles/cloud-services/schema-csdef-workerrole.md",
65106684
"redirect_url": "/previous-versions/azure/cloud-services/schema-csdef-workerrole",
65116685
"redirect_document_id": false
6686+
},
6687+
{
6688+
"source_path": "articles/reliability/migrate-sql-managed-instance.md",
6689+
"redirect_url": "/azure/azure-sql/managed-instance/instance-zone-redundancy-configure",
6690+
"redirect_document_id": false
6691+
},
6692+
{
6693+
"source_path": "articles/operational-excellence/relocation-managed-identity.md",
6694+
"redirect_url": "/entra/identity/managed-identities-azure-resources/how-to-managed-identity-regional-move",
6695+
"redirect_document_id": false
65126696
}
65136697
]
65146698
}

articles/active-directory-b2c/billing.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: kengaderdus
55
manager: CelesteDG
66
ms.service: azure-active-directory
77
ms.topic: reference
8-
ms.date: 09/11/2024
8+
ms.date: 03/10/2025
99
ms.author: kengaderdus
1010
ms.subservice: b2c
1111
ms.custom: fasttrack-edit
@@ -29,7 +29,7 @@ A monthly active user (MAU) is a unique user that performs an authentication wit
2929

3030
If Azure AD B2C [Go-Local add-on](data-residency.md#go-local-add-on) is available in your country/region, and you enable it, you'll be charged per MAU, which is an added charge to your Azure AD B2C [Premium P1 or P2 pricing](https://azure.microsoft.com/pricing/details/active-directory-b2c/) license. Learn more [About Local Data Residency add-on](#about-go-local-add-on)
3131

32-
Also, if you choose to provide higher levels of assurance by using multifactor authentication (MFA) for Voice and SMS, you'll be charged a worldwide flat fee for each MFA attempt that month, whether the sign in is successful or unsuccessful.
32+
Also, if you choose to provide higher levels of assurance by using multifactor authentication (MFA) for Voice and SMS, you'll be charged a fee for each MFA attempt that month, whether the sign in is successful or unsuccessful.
3333

3434

3535
> [!IMPORTANT]
@@ -85,7 +85,7 @@ A subscription linked to an Azure AD B2C tenant can be used for the billing of A
8585
### Create the link
8686

8787
1. Sign in to the [Azure portal](https://portal.azure.com).
88-
1. If you have access to multiple tenants, select the **Settings** icon in the top menu to switch to your Azure AD B2C tenant from the **Directories + subscriptions** menu.
88+
1. If you have access to multiple tenants, select the **Settings** icon in the top menu to switch to your Microsoft Entra tenant from the **Directories + subscriptions** menu.
8989
1. Select **Create a resource**, and then, in the **Search services and Marketplace** field, search for and select **Azure Active Directory B2C**.
9090
1. Select **Create**.
9191
1. Select **Link an existing Azure AD B2C Tenant to my Azure subscription**.

articles/active-directory-b2c/claimsschema.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
11
---
22
title: "ClaimsSchema: Azure Active Directory B2C"
3-
description: Specify the ClaimsSchema element of a custom policy in Azure Active Directory B2C.
3+
description: Specify the ClaimsSchema element of a custom policy in Azure AD B2C. Define and manage claim types for user attributes and input controls.
44

55
author: kengaderdus
66
manager: CelesteDG
77

88
ms.service: azure-active-directory
99

1010
ms.topic: reference
11-
ms.date: 01/11/2024
11+
ms.date: 03/21/2025
1212
ms.author: kengaderdus
1313
ms.subservice: b2c
1414
ms.custom: "b2c-support"

articles/active-directory-b2c/custom-policies-series-branch-user-journey.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Create branching in user journey by using Azure AD B2C custom policy
33
titleSuffix: Azure AD B2C
4-
description: Learn how to enable or disable Technical Profiles based on claims values. Learn how to branch in user journeys by enabling and disabling Azure AD B2C custom policy technical profiles.
4+
description: Learn how to create branching in user journeys using Azure AD B2C custom policies. Enable or disable technical profiles based on claim values.
55

66
author: kengaderdus
77
manager: CelesteDG
@@ -10,7 +10,7 @@ ms.service: azure-active-directory
1010

1111
ms.topic: how-to
1212
ms.custom: b2c-docs-improvements
13-
ms.date: 10/11/2024
13+
ms.date: 03/21/2025
1414
ms.author: kengaderdus
1515
ms.reviewer: yoelh
1616
ms.subservice: b2c
@@ -233,12 +233,12 @@ Follow the steps in [Test the custom policy](custom-policies-series-validate-use
233233
1. Repeat step 5, but this time, select **Account Type**, select **Contoso Employee Account**, and then follow the prompts.
234234

235235

236-
## Next steps
236+
## Related content
237237

238238
In [step 3](#step-3---configure-or-update-technical-profiles), we enable or disable the technical profile by using the `EnabledForUserJourneys` element. Alternatively, you can use [Preconditions](userjourneys.md#preconditions) inside the user journey orchestration steps to execute or skip an orchestration step as we learn later in this series.
239239

240240
Next, learn:
241241

242242
- About [User Journey Orchestration Steps Preconditions](userjourneys.md#preconditions).
243243

244-
- How to [Use the TrustFrameworkPolicy schema file to validate Azure AD B2C policy files](custom-policies-series-install-xml-extensions.md).
244+
- How to [Use the TrustFrameworkPolicy schema file to validate Azure AD B2C policy files](custom-policies-series-install-xml-extensions.md).

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
@@ -1,7 +1,7 @@
11
---
2-
title: Call a REST API by using Azure Active Directory B2C custom policy
2+
title: Call a REST API by using Azure AD B2C custom policy
33
titleSuffix: Azure AD B2C
4-
description: Learn how to make an HTTP call to external API by using Azure Active Directory B2C custom policy.
4+
description: Learn how to call a REST API using Azure AD B2C custom policy. Make HTTP calls to external APIs to send and receive data from external services.
55

66
author: kengaderdus
77
manager: CelesteDG
@@ -10,7 +10,7 @@ ms.service: azure-active-directory
1010

1111
ms.topic: how-to
1212
ms.custom: b2c-docs-improvements, devx-track-js
13-
ms.date: 10/11/2024
13+
ms.date: 03/21/2025
1414
ms.author: kengaderdus
1515
ms.reviewer: yoelh
1616
ms.subservice: b2c
@@ -313,7 +313,7 @@ If your REST API returns data, which you want to include as claims in your polic
313313
314314
Use the steps in [Receiving data](api-connectors-overview.md?pivots=b2c-custom-policy#receiving-data) to learn how to format the data the custom policy expects, how to handle nulls values, and how to parse REST the API's nested JSON body.
315315

316-
## Next steps
316+
## Related content
317317

318318
Next, learn:
319319

articles/active-directory-b2c/custom-policies-series-collect-user-input.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ ms.service: azure-active-directory
1010

1111
ms.topic: how-to
1212
ms.custom: b2c-docs-improvements
13-
ms.date: 10/11/2024
13+
ms.date: 03/21/2025
1414
ms.author: kengaderdus
1515
ms.reviewer: yoelh
1616
ms.subservice: b2c
@@ -504,10 +504,10 @@ After the policy finishes execution, you're redirected to `https://jwt.ms`, and
504504
}.[Signature]
505505
```
506506

507-
## Next steps
507+
## Related content
508508

509509
Next, learn:
510510

511511
- About the [types of Technical Profiles](technicalprofiles.md#types-of-technical-profiles) in Azure AD B2C's custom policies.
512512

513-
- How to [Validate user inputs by using custom policy](custom-policies-series-validate-user-input.md).
513+
- How to [Validate user inputs by using custom policy](custom-policies-series-validate-user-input.md).

articles/active-directory-b2c/custom-policies-series-hello-world.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Write your first Azure AD B2C custom policy - Hello World!
33
titleSuffix: Azure AD B2C
4-
description: Learn how to write your first custom policy. A custom that shows of returns Hello World message.
4+
description: Learn how to write your first Azure AD B2C custom policy. Configure keys, build the policy file, upload it to Azure, and test the custom policy.
55

66
author: kengaderdus
77
manager: CelesteDG
@@ -10,7 +10,7 @@ ms.service: azure-active-directory
1010

1111
ms.topic: how-to
1212
ms.custom: b2c-docs-improvements
13-
ms.date: 10/11/2024
13+
ms.date: 03/21/2025
1414
ms.author: kengaderdus
1515
ms.reviewer: yoelh
1616
ms.subservice: b2c
@@ -286,7 +286,7 @@ After the policy finishes execution, you're redirected to `https://jwt.ms`, and
286286

287287
Notice the `message` and `sub` claims, which we set as [output claims](relyingparty.md#outputclaims) in the `RelyingParty` section.
288288

289-
## Next steps
289+
## Related content
290290

291291
In this article, you learned and used four sections that are included in an Azure AD B2C custom policy. These sections are added as child elements the `TrustFrameworkPolicy` root element:
292292

0 commit comments

Comments
 (0)