Skip to content

Commit 792d72e

Browse files
committed
Merge branch 'v-jbasden-app-insights-nov-freshness2' of https://github.com/v-jbasden/azure-docs-pr into v-jbasden-app-insights-nov-freshness2
2 parents 1ff2a92 + a8cf790 commit 792d72e

File tree

2,214 files changed

+26337
-17800
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,214 files changed

+26337
-17800
lines changed

.acrolinx-config.edn

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,2 @@
11
{:allowed-branchname-matches ["main" "release-.*"]
2-
:allowed-filename-matches ["(?i)articles/(?:(?!active-directory/saas-apps/toc.yml|role-based-access-control/resource-provider-operations.md))" "includes/"]}
2+
:allowed-filename-matches ["(?i)articles/(?:(?!active-directory/saas-apps/toc.yml|role-based-access-control/resource-provider-operations.md|.*policy/samples/|.*resource-graph/samples/))" "(?i)includes/(?:(?!policy/reference/|policy/standards/))"]}

.openpublishing.redirection.defender-for-cloud.json

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -588,7 +588,7 @@
588588
{
589589
"source_path_from_root": "/articles/security-center/managing-and-responding-alerts.md",
590590
"redirect_url": "/azure/defender-for-cloud/managing-and-responding-alerts",
591-
"redirect_document_id": true
591+
"redirect_document_id": false
592592
},
593593
{
594594
"source_path_from_root": "/articles/security-center/os-coverage.md",
@@ -702,8 +702,8 @@
702702
},
703703
{
704704
"source_path_from_root": "/articles/security-center/tutorial-security-incident.md",
705-
"redirect_url": "/azure/defender-for-cloud/tutorial-security-incident",
706-
"redirect_document_id": true
705+
"redirect_url": "/azure/defender-for-cloud/managing-and-responding-alerts",
706+
"redirect_document_id": false
707707
},
708708
{
709709
"source_path_from_root": "/articles/security-center/tutorial-security-policy.md",
@@ -904,6 +904,11 @@
904904
"source_path_from_root": "/articles/defender-for-cloud/attack-path-reference.md",
905905
"redirect_url": "/azure/defender-for-cloud/how-to-manage-attack-path",
906906
"redirect_document_id": true
907+
},
908+
{
909+
"source_path_from_root": "/articles/defender-for-cloud/tutorial-security-incident.md",
910+
"redirect_url": "/azure/defender-for-cloud/managing-and-responding-alerts",
911+
"redirect_document_id": true
907912
}
908913
]
909914
}

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

Lines changed: 86 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,19 +1,98 @@
11
{
22
"redirections": [
3+
{
4+
"source_path_from_root": "/articles/defender-for-iot/organizations/resources-manage-proprietary-protocols.md",
5+
"redirect_url": "/azure/defender-for-iot/organizations/how-to-manage-individual-sensors#manage-custom-plugins-legacy",
6+
"redirect_document_id": false
7+
},
8+
{
9+
"source_path_from_root": "/articles/defender-for-iot/organizations/how-to-set-up-high-availability.md",
10+
"redirect_url": "/azure/defender-for-iot/organizations/legacy-central-management/how-to-set-up-high-availability",
11+
"redirect_document_id": false
12+
},
13+
{
14+
"source_path_from_root": "/articles/defender-for-iot/organizations/ot-deploy/sites-and-zones-on-premises.md",
15+
"redirect_url": "/azure/defender-for-iot/organizations/legacy-central-management/sites-and-zones-on-premises",
16+
"redirect_document_id": false
17+
},
18+
{
19+
"source_path_from_root": "/articles/defender-for-iot/organizations/ot-deploy/activate-deploy-management.md",
20+
"redirect_url": "/azure/defender-for-iot/organizations/legacy-central-management/activate-deploy-management",
21+
"redirect_document_id": false
22+
},
23+
{
24+
"source_path_from_root": "/articles/defender-for-iot/organizations/back-up-restore-management.md",
25+
"redirect_url": "/azure/defender-for-iot/organizations/legacy-central-management/back-up-restore-management",
26+
"redirect_document_id": false
27+
},
28+
{
29+
"source_path_from_root": "/articles/defender-for-iot/organizations/back-up-sensors-from-management.md",
30+
"redirect_url": "/azure/defender-for-iot/organizations/legacy-central-management/back-up-sensors-from-management",
31+
"redirect_document_id": false
32+
},
33+
{
34+
"source_path_from_root": "/articles/defender-for-iot/organizations/ot-deploy/connect-sensors-to-management.md",
35+
"redirect_url": "/azure/defender-for-iot/organizations/legacy-central-management/connect-sensors-to-management",
36+
"redirect_document_id": false
37+
},
38+
{
39+
"source_path_from_root": "/articles/defender-for-iot/organizations/how-to-investigate-all-enterprise-sensor-detections-in-a-device-inventory.md",
40+
"redirect_url": "/azure/defender-for-iot/organizations/legacy-central-management/how-to-investigate-all-enterprise-sensor-detections-in-a-device-inventory",
41+
"redirect_document_id": false
42+
},
43+
{
44+
"source_path_from_root": "/articles/defender-for-iot/organizations/how-to-manage-sensors-from-the-on-premises-management-console.md",
45+
"redirect_url": "/azure/defender-for-iot/organizations/legacy-central-management/how-to-manage-sensors-from-the-on-premises-management-console",
46+
"redirect_document_id": false
47+
},
48+
{
49+
"source_path_from_root": "/articles/defender-for-iot/organizations/how-to-manage-the-on-premises-management-console.md",
50+
"redirect_url": "/azure/defender-for-iot/organizations/legacy-central-management/how-to-manage-the-on-premises-management-console",
51+
"redirect_document_id": false
52+
},
53+
{
54+
"source_path_from_root": "/articles/defender-for-iot/organizations/how-to-troubleshoot-on-premises-management-console.md",
55+
"redirect_url": "/azure/defender-for-iot/organizations/legacy-central-management/how-to-troubleshoot-on-premises-management-console",
56+
"redirect_document_id": false
57+
},
58+
{
59+
"source_path_from_root": "/articles/defender-for-iot/organizations/how-to-work-with-alerts-on-premises-management-console.md",
60+
"redirect_url": "/azure/defender-for-iot/organizations/legacy-central-management/how-to-work-with-alerts-on-premises-management-console",
61+
"redirect_document_id": false
62+
},
63+
{
64+
"source_path_from_root": "/articles/defender-for-iot/organizations/ot-deploy/install-software-on-premises-management-console.md",
65+
"redirect_url": "/azure/defender-for-iot/organizations/legacy-central-management/install-software-on-premises-management-console",
66+
"redirect_document_id": false
67+
},
68+
{
69+
"source_path_from_root": "/articles/defender-for-iot/organizations/ot-deploy/legacy-air-gapped-deploy.md",
70+
"redirect_url": "/azure/defender-for-iot/organizations/legacy-central-management/legacy-air-gapped-deploy",
71+
"redirect_document_id": false
72+
},
73+
{
74+
"source_path_from_root": "/articles/defender-for-iot/organizations/manage-users-on-premises-management-console.md",
75+
"redirect_url": "/azure/defender-for-iot/organizations/legacy-central-management/manage-users-on-premises-management-console",
76+
"redirect_document_id": false
77+
},
78+
{
79+
"source_path_from_root": "/articles/defender-for-iot/organizations/ot-deploy/prepare-management-appliance.md",
80+
"redirect_url": "/azure/defender-for-iot/organizations/legacy-central-management/prepare-management-appliance",
81+
"redirect_document_id": false
82+
},
383
{
484
"source_path_from_root": "/articles/defender-for-iot/organizations/faqs-eiot.md",
585
"redirect_url": "/azure/defender-for-iot/organizations/concept-enterprise#frequently-asked-questions",
686
"redirect_document_id": false
787
},
8-
988
{
1089
"source_path_from_root": "/articles/defender-for-iot/organizations/best-practices/plan-network-monitoring.md",
1190
"redirect_url": "/azure/defender-for-iot/organizations/best-practices/plan-prepare-deploy",
1291
"redirect_document_id": false
1392
},
1493
{
1594
"source_path_from_root": "/articles/defender-for-iot/organizations/how-to-activate-and-set-up-your-on-premises-management-console.md",
16-
"redirect_url": "/azure/defender-for-iot/organizations/ot-deploy/activate-deploy-management",
95+
"redirect_url": "/azure/defender-for-iot/organizations/legacy-central-management/activate-deploy-management",
1796
"redirect_document_id": false
1897
},
1998
{
@@ -92,7 +171,7 @@
92171
},
93172
{
94173
"source_path_from_root": "/articles/defender-for-iot/organizations/how-to-define-global-user-access-control.md",
95-
"redirect_url": "/azure/defender-for-iot/organizations/manage-users-on-premises-management-console#define-global-access-permission-for-on-premises-users",
174+
"redirect_url": "/azure/defender-for-iot/organizations/legacy-central-management/manage-users-on-premises-management-console#define-global-access-permission-for-on-premises-users",
96175
"redirect_document_id": false
97176
},
98177
{
@@ -237,7 +316,7 @@
237316
},
238317
{
239318
"source_path_from_root": "/articles/defender-for-iot/how-to-manage-sensors-from-the-on-premises-management-console.md",
240-
"redirect_url": "/azure/defender-for-iot/organizations/how-to-manage-sensors-from-the-on-premises-management-console",
319+
"redirect_url": "/azure/defender-for-iot/organizations/legacy-central-management/how-to-manage-sensors-from-the-on-premises-management-console",
241320
"redirect_document_id": false
242321
},
243322
{
@@ -252,7 +331,7 @@
252331
},
253332
{
254333
"source_path_from_root": "/articles/defender-for-iot/how-to-manage-the-on-premises-management-console.md",
255-
"redirect_url": "/azure/defender-for-iot/organizations/how-to-manage-the-on-premises-management-console",
334+
"redirect_url": "/azure/defender-for-iot/organizations/legacy-central-management/how-to-manage-the-on-premises-management-console",
256335
"redirect_document_id": false
257336
},
258337
{
@@ -262,7 +341,7 @@
262341
},
263342
{
264343
"source_path_from_root": "/articles/defender-for-iot/how-to-investigate-all-enterprise-sensor-detections-in-a-device-inventory.md",
265-
"redirect_url": "/azure/defender-for-iot/organizations/how-to-investigate-all-enterprise-sensor-detections-in-a-device-inventory",
344+
"redirect_url": "/azure/defender-for-iot/organizations/legacy-central-management/how-to-investigate-all-enterprise-sensor-detections-in-a-device-inventory",
266345
"redirect_document_id": false
267346
},
268347
{
@@ -322,7 +401,7 @@
322401
},
323402
{
324403
"source_path_from_root": "/articles/defender-for-iot/how-to-work-with-alerts-on-premises-management-console.md",
325-
"redirect_url": "/azure/defender-for-iot/organizations/how-to-work-with-alerts-on-premises-management-console",
404+
"redirect_url": "/azure/defender-for-iot/organizations/legacy-central-management/how-to-work-with-alerts-on-premises-management-console",
326405
"redirect_document_id": false
327406
},
328407
{

.openpublishing.redirection.json

Lines changed: 41 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1060,6 +1060,26 @@
10601060
"redirect_url": "/azure/site-recovery/deploy-vmware-azure-replication-appliance-modernized",
10611061
"redirect_document_id": false
10621062
},
1063+
{
1064+
"source_path": "articles/site-recovery/hyper-v-vmm-powershell-resource-manager.md",
1065+
"redirect_url": "/azure/site-recovery/site-recovery-runbook-automation",
1066+
"redirect_document_id": false
1067+
},
1068+
{
1069+
"source_path": "articles/site-recovery/hyper-v-vmm-secondary-support-matrix.",
1070+
"redirect_url": "/azure/site-recovery/hyper-v-azure-support-matrix",
1071+
"redirect_document_id": false
1072+
},
1073+
{
1074+
"source_path": "articles/site-recovery/unregister-vmm-server-script.md",
1075+
"redirect_url": "/azure/site-recovery/azure-to-azure-autoupdate",
1076+
"redirect_document_id": false
1077+
},
1078+
{
1079+
"source_path": "articles/site-recovery/hyper-v-vmm-secondary-support-matrix.md",
1080+
"redirect_url": "/azure/site-recovery/azure-to-azure-autoupdate",
1081+
"redirect_document_id": false
1082+
},
10631083
{
10641084
"source_path": "articles/container-registry/container-registry-customer-managed-keys.md",
10651085
"redirect_url": "/azure/container-registry/tutorial-customer-managed-keys",
@@ -4550,7 +4570,12 @@
45504570
},
45514571
{
45524572
"source_path_from_root": "/articles/app-service/containers/configure-language-ruby.md",
4553-
"redirect_url": "/azure/app-service/configure-language-ruby",
4573+
"redirect_url": "https://github.com/Azure/app-service-linux-docs/blob/master/HowTo/use_ruby_with_container.md",
4574+
"redirect_document_id": false
4575+
},
4576+
{
4577+
"source_path_from_root": "/articles/app-service/configure-language-ruby.md",
4578+
"redirect_url": "https://github.com/Azure/app-service-linux-docs/blob/master/HowTo/use_ruby_with_container.md",
45544579
"redirect_document_id": false
45554580
},
45564581
{
@@ -5340,17 +5365,22 @@
53405365
},
53415366
{
53425367
"source_path_from_root": "/articles/app-service/containers/quickstart-ruby.md",
5343-
"redirect_url": "/azure/app-service/quickstart-ruby",
5368+
"redirect_url": "https://github.com/Azure/app-service-linux-docs/blob/master/HowTo/use_ruby_with_container.md",
5369+
"redirect_document_id": false
5370+
},
5371+
{
5372+
"source_path_from_root": "/articles/app-service/quickstart-ruby.md",
5373+
"redirect_url": "https://github.com/Azure/app-service-linux-docs/blob/master/HowTo/use_ruby_with_container.md",
53445374
"redirect_document_id": false
53455375
},
53465376
{
53475377
"source_path_from_root": "/articles/app-service-web/app-service-linux-ruby-get-started.md",
5348-
"redirect_url": "/azure/app-service/quickstart-ruby",
5378+
"redirect_url": "https://github.com/Azure/app-service-linux-docs/blob/master/HowTo/use_ruby_with_container.md",
53495379
"redirect_document_id": false
53505380
},
53515381
{
53525382
"source_path_from_root": "/articles/app-service-web/app-service-linux-using-ruby.md",
5353-
"redirect_url": "/azure/app-service/quickstart-ruby",
5383+
"redirect_url": "https://github.com/Azure/app-service-linux-docs/blob/master/HowTo/use_ruby_with_container.md",
53545384
"redirect_document_id": false
53555385
},
53565386
{
@@ -5975,12 +6005,17 @@
59756005
},
59766006
{
59776007
"source_path_from_root": "/articles/app-service/containers/tutorial-ruby-mysql-app.md",
5978-
"redirect_url": "/azure/app-service/tutorial-ruby-postgres-app",
6008+
"redirect_url": "https://github.com/Azure/app-service-linux-docs/blob/master/HowTo/use_ruby_with_container.md",
59796009
"redirect_document_id": false
59806010
},
59816011
{
59826012
"source_path_from_root": "/articles/app-service/containers/tutorial-ruby-postgres-app.md",
5983-
"redirect_url": "/azure/app-service/tutorial-ruby-postgres-app",
6013+
"redirect_url": "https://github.com/Azure/app-service-linux-docs/blob/master/HowTo/use_ruby_with_container.md",
6014+
"redirect_document_id": false
6015+
},
6016+
{
6017+
"source_path_from_root": "/articles/app-service/tutorial-ruby-postgres-app.md",
6018+
"redirect_url": "https://github.com/Azure/app-service-linux-docs/blob/master/HowTo/use_ruby_with_container.md",
59846019
"redirect_document_id": false
59856020
},
59866021
{

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -349,7 +349,7 @@ To stop collecting logs to your Log Analytics workspace, delete the diagnostic s
349349
1. Sign in to the [Azure portal](https://portal.azure.com).
350350
1. If you have access to multiple tenants, select the **Settings** icon in the top menu to switch to your Microsoft Entra ID tenant from the **Directories + subscriptions** menu.
351351
1. Choose the resource group that contains the Log Analytics workspace. This example uses a resource group named _azure-ad-b2c-monitor_ and a Log Analytics workspace named `AzureAdB2C`.
352-
1. [Delete the Logs Analytics workspace](../azure-monitor/logs/delete-workspace.md#azure-portal).
352+
1. [Delete the Logs Analytics workspace](../azure-monitor/logs/delete-workspace.md).
353353
1. Select the **Delete** button to delete the resource group.
354354
## Next steps
355355

articles/active-directory-b2c/technicalprofiles.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -249,7 +249,7 @@ The **InputClaim** element contains the following attributes:
249249
| --------- | -------- | ----------- |
250250
| ClaimTypeReferenceId | Yes | The identifier of a claim type. The claim is already defined in the claims schema section in the policy file or parent policy file. |
251251
| DefaultValue | No | A default value to use to create a claim if the claim indicated by ClaimTypeReferenceId doesn't exist so that the resulting claim can be used as an InputClaim element by the technical profile. |
252-
|AlwaysUseDefaultValue |No |Forces the use of the default value. |
252+
|AlwaysUseDefaultValue |Yes |Forces the use of the default value. |
253253
| PartnerClaimType | No | The identifier of the claim type of the external partner that the specified policy claim type maps to. If the PartnerClaimType attribute isn't specified, the specified policy claim type is mapped to the partner claim type of the same name. Use this property when your claim type name is different from the other party. An example is if the first claim name is *givenName*, while the partner uses a claim named *first_name*. |
254254

255255
## Display claims

0 commit comments

Comments
 (0)