Skip to content

Commit dfe7231

Browse files
Merge branch 'release-migration-plan' into smh-migration-articles
2 parents b8702df + 23afa07 commit dfe7231

File tree

2,298 files changed

+14499
-12281
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,298 files changed

+14499
-12281
lines changed

.openpublishing.redirection.active-directory.json

Lines changed: 170 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,176 @@
1010
"redirect_url": "/azure/active-directory/develop/enterprise-app-role-management",
1111
"redirect_document_id": false
1212
},
13+
{
14+
"source_path_from_root": "/articles/global-secure-access/concept-global-secure-access-logs-monitoring.md",
15+
"redirect_url": "/entra/global-secure-access/concept-global-secure-access-logs-monitoring",
16+
"redirect_document_id": false
17+
},
18+
{
19+
"source_path_from_root": "/articles/global-secure-access/concept-private-access.md",
20+
"redirect_url": "/entra/global-secure-access/concept-private-access",
21+
"redirect_document_id": false
22+
},
23+
{
24+
"source_path_from_root": "/articles/global-secure-access/concept-remote-network-connectivity.md",
25+
"redirect_url": "/entra/global-secure-access/concept-remote-network-connectivity",
26+
"redirect_document_id": false
27+
},
28+
{
29+
"source_path_from_root": "/articles/global-secure-access/concept-traffic-dashboard.md",
30+
"redirect_url": "/entra/global-secure-access/concept-traffic-dashboard",
31+
"redirect_document_id": false
32+
},
33+
{
34+
"source_path_from_root": "/articles/global-secure-access/concept-traffic-forwarding.md",
35+
"redirect_url": "/entra/global-secure-access/concept-traffic-forwarding",
36+
"redirect_document_id": false
37+
},
38+
{
39+
"source_path_from_root": "/articles/global-secure-access/concept-universal-conditional-access.md",
40+
"redirect_url": "/entra/global-secure-access/concept-universal-conditional-access",
41+
"redirect_document_id": false
42+
},
43+
{
44+
"source_path_from_root": "/articles/global-secure-access/how-to-access-audit-logs.md",
45+
"redirect_url": "/entra/global-secure-access/how-to-access-audit-logs",
46+
"redirect_document_id": false
47+
},
48+
{
49+
"source_path_from_root": "/articles/global-secure-access/how-to-assign-traffic-profile-to-remote-network.md",
50+
"redirect_url": "/entra/global-secure-access/how-to-assign-traffic-profile-to-remote-network",
51+
"redirect_document_id": false
52+
},
53+
{
54+
"source_path_from_root": "/articles/global-secure-access/how-to-compliant-network.md",
55+
"redirect_url": "/entra/global-secure-access/how-to-compliant-network",
56+
"redirect_document_id": false
57+
},
58+
{
59+
"source_path_from_root": "/articles/global-secure-access/how-to-configure-connectors.md",
60+
"redirect_url": "/entra/global-secure-access/how-to-configure-connectors",
61+
"redirect_document_id": false
62+
},
63+
{
64+
"source_path_from_root": "/articles/global-secure-access/how-to-configure-customer-premises-equipment.md",
65+
"redirect_url": "/entra/global-secure-access/how-to-configure-customer-premises-equipment",
66+
"redirect_document_id": false
67+
},
68+
{
69+
"source_path_from_root": "/articles/global-secure-access/how-to-configure-per-app-access.md",
70+
"redirect_url": "/entra/global-secure-access/how-to-configure-per-app-access",
71+
"redirect_document_id": false
72+
},
73+
{
74+
"source_path_from_root": "/articles/global-secure-access/how-to-configure-quick-access.md",
75+
"redirect_url": "/entra/global-secure-access/how-to-configure-quick-access",
76+
"redirect_document_id": false
77+
},
78+
{
79+
"source_path_from_root": "/articles/global-secure-access/how-to-create-remote-network-custom-ike-policy.md",
80+
"redirect_url": "/entra/global-secure-access/how-to-create-remote-network-custom-ike-policy",
81+
"redirect_document_id": false
82+
},
83+
{
84+
"source_path_from_root": "/articles/global-secure-access/how-to-create-remote-networks.md",
85+
"redirect_url": "/entra/global-secure-access/how-to-create-remote-networks",
86+
"redirect_document_id": false
87+
},
88+
{
89+
"source_path_from_root": "/articles/global-secure-access/how-to-get-started-with-global-secure-access.md",
90+
"redirect_url": "/entra/global-secure-access/how-to-get-started-with-global-secure-access",
91+
"redirect_document_id": false
92+
},
93+
{
94+
"source_path_from_root": "/articles/global-secure-access/how-to-install-windows-client.md",
95+
"redirect_url": "/entra/global-secure-access/how-to-install-windows-client",
96+
"redirect_document_id": false
97+
},
98+
{
99+
"source_path_from_root": "/articles/global-secure-access/how-to-list-remote-networks.md",
100+
"redirect_url": "/entra/global-secure-access/how-to-list-remote-networks",
101+
"redirect_document_id": false
102+
},
103+
{
104+
"source_path_from_root": "/articles/global-secure-access/how-to-manage-microsoft-365-profile.md",
105+
"redirect_url": "/entra/global-secure-access/how-to-manage-microsoft-365-profile",
106+
"redirect_document_id": false
107+
},
108+
{
109+
"source_path_from_root": "/articles/global-secure-access/how-to-manage-private-access-profile.md",
110+
"redirect_url": "/entra/global-secure-access/how-to-manage-private-access-profile",
111+
"redirect_document_id": false
112+
},
113+
{
114+
"source_path_from_root": "/articles/global-secure-access/how-to-manage-remote-network-device-links.md",
115+
"redirect_url": "/entra/global-secure-access/how-to-manage-remote-network-device-links",
116+
"redirect_document_id": false
117+
},
118+
{
119+
"source_path_from_root": "/articles/global-secure-access/how-to-manage-remote-networks.md",
120+
"redirect_url": "/entra/global-secure-access/how-to-manage-remote-networks",
121+
"redirect_document_id": false
122+
},
123+
{
124+
"source_path_from_root": "/articles/global-secure-access/how-to-simulate-remote-network.md",
125+
"redirect_url": "/entra/global-secure-access/how-to-simulate-remote-network",
126+
"redirect_document_id": false
127+
},
128+
{
129+
"source_path_from_root": "/articles/global-secure-access/how-to-source-ip-restoration.md",
130+
"redirect_url": "/entra/global-secure-access/how-to-source-ip-restoration",
131+
"redirect_document_id": false
132+
},
133+
{
134+
"source_path_from_root": "/articles/global-secure-access/how-to-target-resource-microsoft-365-profile.md",
135+
"redirect_url": "/entra/global-secure-access/how-to-target-resource-microsoft-365-profile",
136+
"redirect_document_id": false
137+
},
138+
{
139+
"source_path_from_root": "/articles/global-secure-access/how-to-target-resource-private-access-apps.md",
140+
"redirect_url": "/entra/global-secure-access/how-to-target-resource-private-access-apps",
141+
"redirect_document_id": false
142+
},
143+
{
144+
"source_path_from_root": "/articles/global-secure-access/how-to-universal-tenant-restrictions.md",
145+
"redirect_url": "/entra/global-secure-access/how-to-universal-tenant-restrictions",
146+
"redirect_document_id": false
147+
},
148+
{
149+
"source_path_from_root": "/articles/global-secure-access/how-to-view-enriched-logs.md",
150+
"redirect_url": "/entra/global-secure-access/how-to-view-enriched-logs",
151+
"redirect_document_id": false
152+
},
153+
{
154+
"source_path_from_root": "/articles/global-secure-access/how-to-view-traffic-logs.md",
155+
"redirect_url": "/entra/global-secure-access/how-to-view-traffic-logs",
156+
"redirect_document_id": false
157+
},
158+
{
159+
"source_path_from_root": "/articles/global-secure-access/index.yml",
160+
"redirect_url": "/entra/global-secure-access/index",
161+
"redirect_document_id": false
162+
},
163+
{
164+
"source_path_from_root": "/articles/global-secure-access/overview-what-is-global-secure-access.md",
165+
"redirect_url": "/entra/global-secure-access/overview-what-is-global-secure-access",
166+
"redirect_document_id": false
167+
},
168+
{
169+
"source_path_from_root": "/articles/global-secure-access/reference-points-of-presence.md",
170+
"redirect_url": "/entra/global-secure-access/reference-points-of-presence",
171+
"redirect_document_id": false
172+
},
173+
{
174+
"source_path_from_root": "/articles/global-secure-access/reference-remote-network-configurations.md",
175+
"redirect_url": "/entra/global-secure-access/reference-remote-network-configurations",
176+
"redirect_document_id": false
177+
},
178+
{
179+
"source_path_from_root": "/articles/global-secure-access/resource-faq.yml",
180+
"redirect_url": "/entra/global-secure-access/resource-faq",
181+
"redirect_document_id": false
182+
},
13183
{
14184
"source_path_from_root": "/articles/active-directory/governance/tutorial-prepare-azure-ad-user-accounts.md",
15185
"redirect_url": "/azure/active-directory/governance/tutorial-prepare-user-accounts",

.openpublishing.redirection.json

Lines changed: 43 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,10 @@
11
{
22
"redirections": [
3+
{
4+
"source_path": "articles/communication-services/tutorials/file-sharing-tutorial.md",
5+
"redirect_URL": "/azure/communication-services/tutorials/file-sharing-tutorial-acs-chat",
6+
"redirect_document_id": false
7+
},
38
{
49
"source_path": "articles/azure-resource-manager/bicep/bicep-import-providers.md",
510
"redirect_URL": "bicep-import",
@@ -24477,9 +24482,9 @@
2447724482
"redirect_document_id": false
2447824483
},
2447924484
{
24480-
"source_path": "articles/azure-cache-for-redis/cache-how-to-functions.md",
24481-
"redirect_url": "/azure/azure-functions/functions-bindings-cache",
24482-
"redirect_document_id": false
24485+
"source_path": "articles/azure-cache-for-redis/cache-how-to-functions.md",
24486+
"redirect_url": "/azure/azure-functions/functions-bindings-cache",
24487+
"redirect_document_id": false
2448324488
},
2448424489
{
2448524490
"source_path_from_root": "/articles/active-directory/external-identities/customers/how-to-single-page-app-vanillajs-configure-authentication.md",
@@ -24511,6 +24516,21 @@
2451124516
"redirect_url": "/azure/bastion/bastion-connect-vm-ssh-linux",
2451224517
"redirect_document_id": false
2451324518
},
24519+
{
24520+
"source_path_from_root": "/articles/app-service/overview-disaster-recovery.md",
24521+
"redirect_url": "/azure/reliability/reliability-app-service",
24522+
"redirect_document_id": false
24523+
},
24524+
{
24525+
"source_path_from_root": "/articles/azure-functions/functions-geo-disaster-recovery.md",
24526+
"redirect_url": "/azure/reliability/reliability-functions",
24527+
"redirect_document_id": false
24528+
},
24529+
{
24530+
"source_path_from_root": "/articles/hdinsight/hdinsight-business-continuity.md",
24531+
"redirect_url": "/azure/reliability/reliability-hdinsight",
24532+
"redirect_document_id": false
24533+
},
2451424534
{
2451524535
"source_path_from_root": "/articles/reliability/reliability-postgre-flexible.md",
2451624536
"redirect_url": "/azure/reliability/reliability-postgresql-flexible-server",
@@ -24530,9 +24550,26 @@
2453024550
"source_path_from_root": "/articles/orbital/space-partner-program-overview.md",
2453124551
"redirect_url": "/azure/orbital/overview",
2453224552
"redirect_document_id": false
24553+
},
24554+
{
24555+
"source_path_from_root": "/articles/active-directory/develop/single-page-app-tutorial-01-register-app.md",
24556+
"redirect_url": "/azure/active-directory/develop/tutorial-single-page-app-react-register-app.md",
24557+
"redirect_document_id": false
24558+
},
24559+
{
24560+
"source_path_from_root": "/articles/active-directory/develop/single-page-app-tutorial-02-prepare-spa.md",
24561+
"redirect_url": "/azure/active-directory/develop/tutorial-single-page-app-react-prepare-spa.md",
24562+
"redirect_document_id": false
24563+
},
24564+
{
24565+
"source_path_from_root": "/articles/active-directory/develop/single-page-app-tutorial-03-sign-in-users.md",
24566+
"redirect_url": "/azure/active-directory/develop/tutorial-single-page-app-react-sign-in-users.md",
24567+
"redirect_document_id": false
24568+
},
24569+
{
24570+
"source_path_from_root": "/articles/active-directory/develop/single-page-app-tutorial-04-call-api.md",
24571+
"redirect_url": "/azure/active-directory/develop/tutorial-single-page-app-react-call-api.md",
24572+
"redirect_document_id": false
2453324573
}
24534-
24535-
24536-
2453724574
]
2453824575
}

CODEOWNERS

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ articles/service-health @rboucher
6969
/articles/lighthouse/ @JnHs
7070

7171
# Healthcare APIs
72-
/articles/healthcare-apis/ @ranvijaykumar @mikaelweave
72+
/articles/healthcare-apis/ @ranvijaykumar @chachachachami
7373

7474
# Configuration
7575
*.json @SyntaxC4 @snoviking

articles/active-directory-b2c/active-directory-technical-profile.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,14 +20,16 @@ ms.subservice: B2C
2020

2121
[!INCLUDE [active-directory-b2c-advanced-audience-warning](../../includes/active-directory-b2c-advanced-audience-warning.md)]
2222

23+
<!-- docutune:ignored "AAD-" -->
24+
2325
Azure Active Directory B2C (Azure AD B2C) provides support for the Microsoft Entra user management. This article describes the specifics of a technical profile for interacting with a claims provider that supports this standardized protocol.
2426

2527
## Protocol
2628

2729
The **Name** attribute of the **Protocol** element needs to be set to `Proprietary`. The **handler** attribute must contain the fully qualified name of the protocol handler assembly `Web.TPEngine.Providers.AzureActiveDirectoryProvider, Web.TPEngine, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null`.
2830

2931
Following [custom policy starter pack](tutorial-create-user-flows.md?pivots=b2c-custom-policy#custom-policy-starter-pack) Microsoft Entra technical profiles include the **AAD-Common** technical profile. The Microsoft Entra technical profiles don't specify the protocol because the protocol is configured in the **AAD-Common** technical profile:
30-
32+
3133
- **AAD-UserReadUsingAlternativeSecurityId** and **AAD-UserReadUsingAlternativeSecurityId-NoError** - Look up a social account in the directory.
3234
- **AAD-UserWriteUsingAlternativeSecurityId** - Create a new social account.
3335
- **AAD-UserReadUsingEmailAddress** - Look up a local account in the directory.

articles/active-directory-b2c/azure-monitor.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ Watch this video to learn how to configure monitoring for Azure AD B2C using Azu
3838
3939
## Deployment overview
4040

41-
Azure AD B2C uses [Microsoft Entra ID monitoring](../active-directory/reports-monitoring/overview-monitoring-health.md). Unlike Microsoft Entra tenants, an Azure AD B2C tenant can't have a subscription associated with it. So, we need to take extra steps to enable the integration between Azure AD B2C and Log Analytics, which is where we send the logs.
41+
Azure AD B2C uses [Microsoft Entra monitoring](../active-directory/reports-monitoring/overview-monitoring-health.md). Unlike Microsoft Entra tenants, an Azure AD B2C tenant can't have a subscription associated with it. So, we need to take extra steps to enable the integration between Azure AD B2C and Log Analytics, which is where we send the logs.
4242
To enable _Diagnostic settings_ in Microsoft Entra ID within your Azure AD B2C tenant, you use [Azure Lighthouse](../lighthouse/overview.md) to [delegate a resource](../lighthouse/concepts/architecture.md), which allows your Azure AD B2C (the **Service Provider**) to manage a Microsoft Entra ID (the **Customer**) resource.
4343

4444
> [!TIP]
@@ -365,4 +365,4 @@ To stop collecting logs to your Log Analytics workspace, delete the diagnostic s
365365

366366
- For more information about adding and configuring diagnostic settings in Azure Monitor, see [Tutorial: Collect and analyze resource logs from an Azure resource](../azure-monitor/essentials/monitor-azure-resource.md).
367367

368-
- For information about streaming Microsoft Entra ID logs to an event hub, see [Tutorial: Stream Microsoft Entra ID logs to an Azure event hub](../active-directory/reports-monitoring/tutorial-azure-monitor-stream-logs-to-event-hub.md).
368+
- For information about streaming Microsoft Entra logs to an event hub, see [Tutorial: Stream Microsoft Entra logs to an Azure event hub](../active-directory/reports-monitoring/tutorial-azure-monitor-stream-logs-to-event-hub.md).

articles/active-directory-b2c/custom-policies-series-sign-up-or-sign-in.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -303,7 +303,7 @@ When the custom policy runs:
303303
- **Orchestration Step 4** - This step runs if the user signs up (objectId doesn't exist), so we display the sign-up form by invoking the
304304
*UserInformationCollector* self-asserted technical profile. This step runs whether a user signs up or signs in.
305305

306-
- **Orchestration Step 5** - This step reads account information from Microsoft Entra ID (we invoke *AAD-UserRead* Microsoft Entra technical profile), so it runs whether a user signs up or signs in.
306+
- **Orchestration Step 5** - This step reads account information from Microsoft Entra ID (we invoke `AAD-UserRead` Microsoft Entra technical profile), so it runs whether a user signs up or signs in.
307307

308308
- **Orchestration Step 6** - This step invokes the *UserInputMessageClaimGenerator* technical profile to assemble the user’s greeting message.
309309

articles/active-directory-b2c/customize-ui.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -231,7 +231,7 @@ If you'd like to brand all pages in the user flow, set the page layout version f
231231

232232
## Enable company branding in custom policy pages
233233

234-
Once you've configured company branding, enable it in your custom policy. Configure the [page layout version](contentdefinitions.md#migrating-to-page-layout) with page `contract` version for *all* of the content definitions in your custom policy. The format of the value must contain the word `contract`: _urn:com:microsoft:aad:b2c:elements:**contract**:page-name:version_. To specify a page layout in your custom policies that use an old **DataUri** value. For more information, learn how to [migrate to page layout](contentdefinitions.md#migrating-to-page-layout) with page version.
234+
Once you've configured company branding, enable it in your custom policy. Configure the [page layout version](contentdefinitions.md#migrating-to-page-layout) with page `contract` version for *all* of the content definitions in your custom policy. The format of the value must contain the word `contract`: *urn:com:microsoft:aad:b2c:elements:**contract**:page-name:version*. To specify a page layout in your custom policies that use an old **DataUri** value. For more information, learn how to [migrate to page layout](contentdefinitions.md#migrating-to-page-layout) with page version.
235235

236236
The following example shows the content definitions with their corresponding the page contract, and *Ocean Blue* page template:
237237

articles/active-directory-b2c/force-password-reset.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -149,7 +149,7 @@ Once a password expiration policy has been set, you must also configure force pa
149149

150150
### Password expiry duration
151151

152-
By default, the password is set not to expire. However, the value is configurable by using the [Set-MsolPasswordPolicy](/powershell/module/msonline/set-msolpasswordpolicy) cmdlet from the Azure AD Module for Windows PowerShell. This command updates the tenant, so that all users' passwords expire after number of days you configure.
152+
By default, the password is set not to expire. However, the value is configurable by using the [Set-MsolPasswordPolicy](/powershell/module/msonline/set-msolpasswordpolicy) cmdlet from the Azure AD PowerShell module. This command updates the tenant, so that all users' passwords expire after number of days you configure.
153153

154154
## Next steps
155155

articles/active-directory-b2c/javascript-and-page-layout.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,7 @@ For information about the different page layout versions, see the [Page layout v
6868
To specify a page layout version for your custom policy pages:
6969

7070
1. Select a [page layout](contentdefinitions.md#select-a-page-layout) for the user interface elements of your application.
71-
1. Define a [page layout version](contentdefinitions.md#migrating-to-page-layout) with page `contract` version for *all* of the content definitions in your custom policy. The format of the value must contain the word `contract`: _urn:com:microsoft:aad:b2c:elements:**contract**:page-name:version_.
71+
1. Define a [page layout version](contentdefinitions.md#migrating-to-page-layout) with page `contract` version for *all* of the content definitions in your custom policy. The format of the value must contain the word `contract`: *urn:com:microsoft:aad:b2c:elements:**contract**:page-name:version*.
7272

7373
The following example shows the content definition identifiers and the corresponding **DataUri** with page contract:
7474

0 commit comments

Comments
 (0)