Skip to content

Commit 25c9f47

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into update-howto-schedule-broadcast-jobs
Need updated related files from main.
2 parents ecc6d15 + 96a358d commit 25c9f47

File tree

765 files changed

+15959
-15957
lines changed

Some content is hidden

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

765 files changed

+15959
-15957
lines changed

.openpublishing.redirection.json

Lines changed: 138 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,110 @@
11
{
22
"redirections": [
3+
{
4+
"source_path": "articles/defender-for-iot/organizations/appliance-catalog/virtual-management-hyper-v.md",
5+
"redirect_url": "/previous-versions/azure/defender-for-iot/organizations/appliance-catalog/virtual-management-hyper-v",
6+
"redirect_document_id": false
7+
},
8+
{
9+
"source_path": "articles/defender-for-iot/organizations/appliance-catalog/virtual-management-vmware.md",
10+
"redirect_url": "/previous-versions/azure/defender-for-iot/organizations/appliance-catalog/virtual-management-vmware",
11+
"redirect_document_id": false
12+
},
13+
{
14+
"source_path": "articles/defender-for-iot/organizations/api/management-alert-apis.md",
15+
"redirect_url": "/previous-versions/azure/defender-for-iot/organizations/api/management-alert-apis",
16+
"redirect_document_id": false
17+
},
18+
{
19+
"source_path": "articles/defender-for-iot/organizations/api/management-inventory-apis.md",
20+
"redirect_url": "/previous-versions/azure/defender-for-iot/organizations/api/management-inventory-apis",
21+
"redirect_document_id": false
22+
},
23+
{
24+
"source_path": "articles/defender-for-iot/organizations/api/management-appliances-apis.md",
25+
"redirect_url": "/previous-versions/azure/defender-for-iot/organizations/api/management-appliances-apis",
26+
"redirect_document_id": false
27+
},
28+
{
29+
"source_path": "articles/defender-for-iot/organizations/api/management-auth-apis.md",
30+
"redirect_url": "/previous-versions/azure/defender-for-iot/organizations/api/management-auth-apis",
31+
"redirect_document_id": false
32+
},
33+
{
34+
"source_path": "articles/defender-for-iot/organizations/api/management-integration-apis.md",
35+
"redirect_url": "/previous-versions/azure/defender-for-iot/organizations/api/management-integration-apis",
36+
"redirect_document_id": false
37+
},
38+
{
39+
"source_path": "articles/defender-for-iot/organizations/legacy-central-management/back-up-sensors-from-management.md",
40+
"redirect_url": "/previous-versions/azure/defender-for-iot/organizations/legacy-central-management/back-up-sensors-from-management",
41+
"redirect_document_id": false
42+
},
43+
{
44+
"source_path": "articles/defender-for-iot/organizations/legacy-central-management/back-up-restore-management.md",
45+
"redirect_url": "/previous-versions/azure/defender-for-iot/organizations/legacy-central-management/back-up-restore-management",
46+
"redirect_document_id": false
47+
},
48+
{
49+
"source_path": "articles/defender-for-iot/organizations/legacy-central-management/how-to-set-up-high-availability.md",
50+
"redirect_url": "/previous-versions/azure/defender-for-iot/organizations/legacy-central-management/how-to-set-up-high-availability",
51+
"redirect_document_id": false
52+
},
53+
{
54+
"source_path": "articles/defender-for-iot/organizations/legacy-central-management/how-to-manage-sensors-from-the-on-premises-management-console.md",
55+
"redirect_url": "/previous-versions/azure/defender-for-iot/organizations/legacy-central-management/how-to-manage-sensors-from-the-on-premises-management-console",
56+
"redirect_document_id": false
57+
},
58+
{
59+
"source_path": "articles/defender-for-iot/organizations/legacy-central-management/how-to-manage-the-on-premises-management-console.md",
60+
"redirect_url": "/previous-versions/azure/defender-for-iot/organizations/legacy-central-management/how-to-manage-the-on-premises-management-console",
61+
"redirect_document_id": false
62+
},
63+
{
64+
"source_path": "articles/defender-for-iot/organizations/legacy-central-management/how-to-troubleshoot-on-premises-management-console.md",
65+
"redirect_url": "/previous-versions/azure/defender-for-iot/organizations/legacy-central-management/how-to-troubleshoot-on-premises-management-console",
66+
"redirect_document_id": false
67+
},
68+
{
69+
"source_path": "articles/defender-for-iot/organizations/legacy-central-management/legacy-air-gapped-deploy.md",
70+
"redirect_url": "/previous-versions/azure/defender-for-iot/organizations/legacy-central-management/legacy-air-gapped-deploy",
71+
"redirect_document_id": false
72+
},
73+
{
74+
"source_path": "articles/defender-for-iot/organizations/legacy-central-management/prepare-management-appliance.md",
75+
"redirect_url": "/previous-versions/azure/defender-for-iot/organizations/legacy-central-management/prepare-management-appliance",
76+
"redirect_document_id": false
77+
},
78+
{
79+
"source_path": "articles/defender-for-iot/organizations/legacy-central-management/install-software-on-premises-management-console.md",
80+
"redirect_url": "/previous-versions/azure/defender-for-iot/organizations/legacy-central-management/install-software-on-premises-management-console",
81+
"redirect_document_id": false
82+
},
83+
{
84+
"source_path": "articles/defender-for-iot/organizations/legacy-central-management/activate-deploy-management.md",
85+
"redirect_url": "/previous-versions/azure/defender-for-iot/organizations/legacy-central-management/activate-deploy-management",
86+
"redirect_document_id": false
87+
},
88+
{
89+
"source_path": "articles/defender-for-iot/organizations/legacy-central-management/connect-sensors-to-management.md",
90+
"redirect_url": "/previous-versions/azure/defender-for-iot/organizations/legacy-central-management/connect-sensors-to-management",
91+
"redirect_document_id": false
92+
},
93+
{
94+
"source_path": "articles/defender-for-iot/organizations/legacy-central-management/sites-and-zones-on-premises.md",
95+
"redirect_url": "/previous-versions/azure/defender-for-iot/organizations/legacy-central-management/sites-and-zones-on-premises",
96+
"redirect_document_id": false
97+
},
98+
{
99+
"source_path": "articles/defender-for-iot/organizations/legacy-central-management/how-to-investigate-all-enterprise-sensor-detections-in-a-device-inventory.md",
100+
"redirect_url": "/previous-versions/azure/defender-for-iot/organizations/legacy-central-management/how-to-investigate-all-enterprise-sensor-detections-in-a-device-inventory",
101+
"redirect_document_id": false
102+
},
103+
{
104+
"source_path": "articles/defender-for-iot/organizations/legacy-central-management/how-to-work-with-alerts-on-premises-management-console.md",
105+
"redirect_url": "/previous-versions/azure/defender-for-iot/organizations/legacy-central-management/how-to-work-with-alerts-on-premises-management-console",
106+
"redirect_document_id": false
107+
},
3108
{
4109
"source_path": "articles/cdn/akamai-retirement-faq.md",
5110
"redirect_url": "/previous-versions/azure/cdn/akamai-retirement-faq",
@@ -88,6 +193,7 @@
88193
{
89194
"source_path": "articles/operator-5g-core/tutorial-configure-network-function.md",
90195
"redirect_url": "/previous-versions/azure/operator-5g-core/tutorial-configure-network-function",
196+
"redirect_document_id": false
91197
},
92198
{
93199
"source_path": "articles/operator-call-protection/deployment-overview.md",
@@ -112,6 +218,7 @@
112218
{
113219
"source_path": "articles/operator-call-protection/set-up-operator-call-protection.md",
114220
"redirect_url": "/previous-versions/azure/operator-call-protection/set-up-operator-call-protection",
221+
"redirect_document_id": false
115222
},
116223
{
117224
"source_path": "articles/private-multi-access-edge-compute-mec/overview.md",
@@ -121,6 +228,7 @@
121228
{
122229
"source_path": "articles/private-multi-access-edge-compute-mec/partner-programs.md",
123230
"redirect_url": "/previous-versions/azure/private-multi-access-edge-compute-mec/partner-programs",
231+
"redirect_document_id": false
124232
},
125233
{
126234
"source_path": "articles/time-series-insights/breaking-changes-long-data-type.md",
@@ -4627,6 +4735,36 @@
46274735
"redirect_url": "/azure/sentinel/data-connectors/threat-intelligence-upload-api",
46284736
"redirect_document_id": false
46294737
},
4738+
{
4739+
"source_path_from_root": "/articles/app-spaces/how-to-add-components.md",
4740+
"redirect_url": "/azure/container-apps/",
4741+
"redirect_document_id": false
4742+
},
4743+
{
4744+
"source_path_from_root": "/articles/app-spaces/how-to-manage-components.md",
4745+
"redirect_url": "/azure/container-apps/",
4746+
"redirect_document_id": false
4747+
},
4748+
{
4749+
"source_path_from_root": "/articles/app-spaces/index.yml",
4750+
"redirect_url": "/azure/container-apps/",
4751+
"redirect_document_id": false
4752+
},
4753+
{
4754+
"source_path_from_root": "/articles/app-spaces/overview.md",
4755+
"redirect_url": "/azure/container-apps/",
4756+
"redirect_document_id": false
4757+
},
4758+
{
4759+
"source_path_from_root": "/articles/app-spaces/quickstart-deploy-starter-app.md",
4760+
"redirect_url": "/azure/container-apps/",
4761+
"redirect_document_id": false
4762+
},
4763+
{
4764+
"source_path_from_root": "/articles/app-spaces/quickstart-deploy-your-app.md",
4765+
"redirect_url": "/azure/container-apps/",
4766+
"redirect_document_id": false
4767+
},
46304768
{
46314769
"source_path_from_root": "/articles/virtual-network/create-vm-accelerated-networking-cli.md",
46324770
"redirect_url": "/azure/virtual-network/create-virtual-machine-accelerated-networking",

articles/active-directory-b2c/add-password-reset-policy.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: garrodonnell
66
manager: CelesteDG
77
ms.service: azure-active-directory
88
ms.topic: how-to
9-
ms.date: 11/27/2023
9+
ms.date: 11/27/2024
1010
ms.author: godonnell
1111
ms.subservice: b2c
1212
zone_pivot_groups: b2c-policy-type

articles/active-directory-b2c/add-sign-up-and-sign-in-policy.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: garrodonnell
66
manager: CelesteDG
77
ms.service: azure-active-directory
88
ms.topic: how-to
9-
ms.date: 03/22/2024
9+
ms.date: 01/10/2025
1010
ms.author: godonnell
1111
ms.subservice: b2c
1212
ms.custom: "b2c-support"

articles/active-directory-b2c/api-connectors-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -244,7 +244,7 @@ If you reference a REST API technical profile directly from a user journey, the
244244

245245
## Development of your REST API
246246

247-
Your REST API can be developed on any platform and written in any programing language, as long as it's secure and can send and receive claims in JSON format.
247+
Your REST API can be developed on any platform and written in any programming language, as long as it's secure and can send and receive claims in JSON format.
248248

249249
The request to your REST API service comes from Azure AD B2C servers. The REST API service must be published to a publicly accessible HTTPS endpoint. The REST API call arrives from an Azure data center IP address.
250250

articles/active-directory-b2c/claimsschema.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -325,7 +325,7 @@ The **DateTimeDropdown** user input type is used to provide a set of drop-downs
325325

326326
The **RadioSingleSelect** user input type is used to provide a collection of radio buttons that allows the user to select one option.
327327

328-
![Using claim type with radiodsingleselect](./media/claimsschema/radiosingleselect.png)
328+
![Using claim type with radiosingleselect](./media/claimsschema/radiosingleselect.png)
329329

330330
```xml
331331
<ClaimType Id="color">

articles/active-directory-b2c/configure-authentication-sample-angular-spa-app.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -190,7 +190,7 @@ Your final configuration file should look like the following JSON:
190190
```json
191191
{
192192
"credentials": {
193-
"tenantName": "<your-tenant-namee>",
193+
"tenantName": "<your-tenant-name>",
194194
"clientID": "<your-webapi-application-ID>",
195195
"issuer": "https://<your-tenant-name>.b2clogin.com/<your-tenant-ID>/v2.0/"
196196
},

articles/active-directory-b2c/configure-user-input.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: garrodonnell
66
manager: CelesteDG
77
ms.service: azure-active-directory
88
ms.topic: how-to
9-
ms.date: 12/13/2023
9+
ms.date: 12/13/2024
1010
ms.author: godonnell
1111
ms.subservice: b2c
1212
zone_pivot_groups: b2c-policy-type

articles/active-directory-b2c/custom-policy-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ In the [Azure AD B2C samples GitHub repository](https://github.com/azure-ad-b2c/
4141

4242
### Claims
4343

44-
A claim provides temporary storage of data during an Azure AD B2C policy execution. Claims are more like variable in a programing language. It can store information about the user, such as first name, last name, or any other claim obtained from the user or other systems (claims exchanges). The [claims schema](claimsschema.md) is the place where you declare your claims.
44+
A claim provides temporary storage of data during an Azure AD B2C policy execution. Claims are more like variable in a programming language. It can store information about the user, such as first name, last name, or any other claim obtained from the user or other systems (claims exchanges). The [claims schema](claimsschema.md) is the place where you declare your claims.
4545

4646
When the policy runs, Azure AD B2C sends and receives claims to and from internal and external parties and then sends a subset of these claims to your relying party application as part of the token. Claims are used in these ways:
4747

articles/active-directory-b2c/custom-policy-reference-sso.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,7 @@ To use a session provider in your technical profile:
7171

7272
```xml
7373
<TechnicalProfile Id="SM-AAD">
74-
<DisplayName>Session Mananagement Provider</DisplayName>
74+
<DisplayName>Session Management Provider</DisplayName>
7575
<Protocol Name="Proprietary" Handler="Web.TPEngine.SSO.DefaultSSOSessionProvider, Web.TPEngine, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" />
7676
<PersistedClaims>
7777
<PersistedClaim ClaimTypeReferenceId="objectId" />

articles/active-directory-b2c/faq.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ metadata:
88
ms.service: azure-active-directory
99

1010
ms.topic: faq
11-
ms.date: 10/31/2023
11+
ms.date: 10/01/2024
1212
ms.author: godonnell
1313
ms.subservice: b2c
1414
ms.custom: b2c-support, has-azure-ad-ps-ref,azure-ad-ref-level-one-done
@@ -32,7 +32,7 @@ sections:
3232
- question: |
3333
Why can't I access the Azure AD B2C extension in the Azure portal?
3434
answer: |
35-
There are two common reasons for why the Microsoft Entra extension isn't working for you. Azure AD B2C requires your user role in the directory to be a global administrator. Contact your administrator if you think you should have access. If you have global administrator privileges, make sure that you are in an Azure AD B2C directory and not a Microsoft Entra directory. You can see instructions for [creating an Azure AD B2C tenant](tutorial-create-tenant.md).
35+
There are two common reasons for why the Microsoft Entra extension isn't working for you. Azure AD B2C requires your user role in the directory to be a Global administrator. Contact your administrator if you think you should have access. If you have Global administrator privileges, make sure that you are in an Azure AD B2C directory and not a Microsoft Entra directory. You can see instructions for [creating an Azure AD B2C tenant](tutorial-create-tenant.md).
3636
3737
- question: |
3838
Can I use Azure AD B2C features in my existing, employee-based Microsoft Entra tenant?
@@ -92,7 +92,7 @@ sections:
9292
- question: |
9393
Why am I unable to create an Azure AD B2C tenant?
9494
answer: |
95-
You might not have permission to create an Azure AD B2C tenant. Only users with **Global administrator** or **Tenant Creator** roles can create the tenant. You need to contact your **Global administrator**.
95+
You might not have permission to create an Azure AD B2C tenant. Only users with at least **Tenant Creator** roles can create the tenant.
9696
9797
- question: |
9898
How do I customize verification emails (the content and the "From:" field) sent by Azure AD B2C?

0 commit comments

Comments
 (0)