Skip to content

Commit 3ff79d7

Browse files
batamigbatamig
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into sap-redux
2 parents 388e0cb + 477a222 commit 3ff79d7

File tree

498 files changed

+3337
-2455
lines changed

Some content is hidden

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

498 files changed

+3337
-2455
lines changed

‎.openpublishing.redirection.json

Lines changed: 106 additions & 1198 deletions
Large diffs are not rendered by default.

‎articles/active-directory-b2c/secure-rest-api.md

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: kengaderdus
66
manager: CelesteDG
77
ms.service: azure-active-directory
88
ms.topic: how-to
9-
ms.date: 01/11/2024
9+
ms.date: 10/14/2024
1010
ms.author: kengaderdus
1111
ms.subservice: b2c
1212
zone_pivot_groups: b2c-policy-type
@@ -276,7 +276,10 @@ A claim provides temporary storage of data during an Azure AD B2C policy executi
276276

277277
### Acquiring an access token
278278

279-
You can obtain an access token in one of several ways, for the [from a federated identity provider](idp-pass-through-user-flow.md), by calling a REST API that returns an access token, by using an [ROPC flow](../active-directory/develop/v2-oauth-ropc.md), or by using the [client credentials flow](../active-directory/develop/v2-oauth2-client-creds-grant-flow.md). The client credentials flow is commonly used for server-to-server interactions that must run in the background, without immediate interaction with a user.
279+
You can obtain an access token in one of several ways, for the [from a federated identity provider](idp-pass-through-user-flow.md), by calling a REST API that returns an access token, by using an [ROPC flow](/entra/identity-platform/v2-oauth-ropc), or by using the [client credentials flow](../active-directory/develop/v2-oauth2-client-creds-grant-flow.md). The client credentials flow is commonly used for server-to-server interactions that must run in the background, without immediate interaction with a user.
280+
281+
> [!WARNING]
282+
> Microsoft recommends you do *not* use the ROPC flow. This flow requires a very high degree of trust in the application, and carries risks that are not present in other flows. You should only use this flow when other more secure flows aren't viable.
280283
281284
<a name='acquiring-an-azure-ad-access-token-'></a>
282285

@@ -577,12 +580,12 @@ The following XML snippet is an example of a RESTful technical profile configure
577580
```
578581
::: zone-end
579582

580-
## Next steps
583+
## Related content
581584

582585
::: zone pivot="b2c-user-flow"
583586
- Get started with our [samples](api-connector-samples.md#api-connector-rest-api-samples).
584587
::: zone-end
585588

586589
::: zone pivot="b2c-custom-policy"
587590
- Learn more about the [Restful technical profile](restful-technical-profile.md) element in the custom policy reference.
588-
::: zone-end
591+
::: zone-end

‎articles/application-gateway/.openpublishing.redirection.application-gateway.json

Lines changed: 42 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,6 @@
8080
"redirect_url": "/azure/application-gateway/tutorial-protect-application-gateway-ddos",
8181
"redirect_document_id": false
8282
},
83-
8483
{
8584
"source_path_from_root": "/articles/application-gateway/rewrite-http-headers.md",
8685
"redirect_url": "/azure/application-gateway/rewrite-http-headers-url",
@@ -305,6 +304,46 @@
305304
"source_path_from_root": "/articles/application-gateway/application-gateway-web-app-overview.md",
306305
"redirect_url": "/azure/application-gateway/configure-web-app",
307306
"redirect_document_id": false
308-
}
307+
},
308+
{
309+
"source_path_from_root": "/articles/application-gateway/powershell-samples.md",
310+
"redirect_url": "/previous-versions/azure/application-gateway/powershell-samples",
311+
"redirect_document_id": false
312+
},
313+
{
314+
"source_path_from_root": "/articles/application-gateway/cli-samples.md",
315+
"redirect_url": "/previous-versions/azure/application-gateway/cli-samples",
316+
"redirect_document_id": false
317+
},
318+
{
319+
"source_path_from_root": "/articles/application-gateway/resource-manager-template-samples.md",
320+
"redirect_url": "/previous-versions/azure/application-gateway/resource-manager-template-samples",
321+
"redirect_document_id": false
322+
},
323+
{
324+
"source_path_from_root": "/articles/application-gateway/scripts/create-vmss-cli.md",
325+
"redirect_url": "/previous-versions/azure/application-gateway/scripts/create-vmss-cli",
326+
"redirect_document_id": false
327+
},
328+
{
329+
"source_path_from_root": "/articles/application-gateway/scripts/create-vmss-powershell.md",
330+
"redirect_url": "/previous-versions/azure/application-gateway/scripts/create-vmss-powershell",
331+
"redirect_document_id": false
332+
},
333+
{
334+
"source_path_from_root": "/articles/application-gateway/scripts/create-vmss-waf-cli.md",
335+
"redirect_url": "/previous-versions/azure/application-gateway/scripts/create-vmss-waf-cli",
336+
"redirect_document_id": false
337+
},
338+
{
339+
"source_path_from_root": "/articles/application-gateway/scripts/create-vmss-waf-powershell.md",
340+
"redirect_url": "/previous-versions/azure/application-gateway/scripts/create-vmss-waf-powershell",
341+
"redirect_document_id": false
342+
},
343+
{
344+
"source_path_from_root": "/articles/application-gateway/scripts/waf-custom-rules-powershell.md",
345+
"redirect_url": "/previous-versions/azure/application-gateway/scripts/waf-custom-rules-powershell",
346+
"redirect_document_id": false
347+
},
309348
]
310-
}
349+
}

‎articles/azure-edge-hardware-center/index.yml

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,7 @@ summary: Use Azure Edge Hardware Center service to order from a variety of Azure
66
metadata:
77
title: Azure Edge Hardware Center documentation
88
description: Azure Edge Hardware Center Documentation.
9-
ms.service: databox
10-
ms.subservice: edge
9+
ms.service: azure-stack-edge
1110
ms.topic: landing-page
1211
author: alkohli
1312
ms.author: alkohli

‎articles/azure-maps/.openpublishing.redirection.azure-maps.json

Lines changed: 184 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,184 @@
1+
{
2+
"redirections": [
3+
{
4+
"source_path_from_root": "/articles/location-based-services/about-location-based-services.md",
5+
"redirect_url": "/azure/azure-maps/about-azure-maps",
6+
"redirect_document_id": true
7+
},
8+
{
9+
"source_path_from_root": "/articles/location-based-services/geocoding-coverage.md",
10+
"redirect_url": "/azure/azure-maps/geocoding-coverage",
11+
"redirect_document_id": true
12+
},
13+
{
14+
"source_path_from_root": "/articles/location-based-services/how-to-manage-account-keys.md",
15+
"redirect_url": "/azure/azure-maps/how-to-manage-account-keys",
16+
"redirect_document_id": true
17+
},
18+
{
19+
"source_path_from_root": "/articles/location-based-services/how-to-search-for-address.md",
20+
"redirect_url": "/azure/azure-maps/how-to-search-for-address",
21+
"redirect_document_id": true
22+
},
23+
{
24+
"source_path_from_root": "/articles/location-based-services/how-to-use-map-control.md",
25+
"redirect_url": "/azure/azure-maps/how-to-use-map-control",
26+
"redirect_document_id": true
27+
},
28+
{
29+
"source_path_from_root": "/articles/location-based-services/index.md",
30+
"redirect_url": "/azure/azure-maps/index",
31+
"redirect_document_id": false
32+
},
33+
{
34+
"source_path_from_root": "/articles/location-based-services/quick-demo-map-app.md",
35+
"redirect_url": "/azure/azure-maps/quick-demo-map-app",
36+
"redirect_document_id": true
37+
},
38+
{
39+
"source_path_from_root": "/articles/location-based-services/render-coverage.md",
40+
"redirect_url": "/azure/azure-maps/render-coverage",
41+
"redirect_document_id": true
42+
},
43+
{
44+
"source_path_from_root": "/articles/location-based-services/routing-coverage.md",
45+
"redirect_url": "/azure/azure-maps/routing-coverage",
46+
"redirect_document_id": true
47+
},
48+
{
49+
"source_path_from_root": "/articles/location-based-services/supported-languages.md",
50+
"redirect_url": "/azure/azure-maps/supported-languages",
51+
"redirect_document_id": true
52+
},
53+
{
54+
"source_path_from_root": "/articles/location-based-services/traffic-coverage.md",
55+
"redirect_url": "/azure/azure-maps/traffic-coverage",
56+
"redirect_document_id": true
57+
},
58+
{
59+
"source_path_from_root": "/articles/location-based-services/tutorial-prioritized-routes.md",
60+
"redirect_url": "/azure/azure-maps/tutorial-prioritized-routes",
61+
"redirect_document_id": true
62+
},
63+
{
64+
"source_path_from_root": "/articles/location-based-services/tutorial-route-location.md",
65+
"redirect_url": "/azure/azure-maps/tutorial-route-location",
66+
"redirect_document_id": true
67+
},
68+
{
69+
"source_path_from_root": "/articles/location-based-services/tutorial-search-location.md",
70+
"redirect_url": "/azure/azure-maps/tutorial-search-location",
71+
"redirect_document_id": true
72+
},
73+
{
74+
"source_path_from_root": "/articles/location-based-services/zoom-levels-and-tile-grid.md",
75+
"redirect_url": "/azure/azure-maps/zoom-levels-and-tile-grid",
76+
"redirect_document_id": true
77+
},
78+
{
79+
"source_path_from_root": "/articles/azure-maps/tutorial-iot-hub-maps.md",
80+
"redirect_url": "/azure/azure-maps",
81+
"redirect_document_id": false
82+
},
83+
{
84+
"source_path_from_root": "/articles/azure-maps/about-creator.md",
85+
"redirect_url": "/azure/azure-maps/creator-indoor-maps",
86+
"redirect_document_id": true
87+
},
88+
{
89+
"source_path_from_root": "/articles/azure-maps/choose-pricing-tier.md",
90+
"redirect_url": "/azure/azure-maps/how-to-manage-pricing-tier",
91+
"redirect_document_id": true
92+
},
93+
{
94+
"source_path_from_root": "/articles/azure-maps/how-to-creator-feature-stateset.md",
95+
"redirect_url": "/azure/azure-maps/about-creator",
96+
"redirect_document_id": false
97+
},
98+
{
99+
"source_path_from_root": "/articles/azure-maps/how-to-request-elevation-data.md",
100+
"redirect_url": "https://azure.microsoft.com/updates/azure-maps-elevation-apis-and-render-v2-dem-tiles-will-be-retired-on-5-may-2023",
101+
"redirect_document_id": false
102+
},
103+
{
104+
"source_path_from_root": "/articles/azure-maps/how-to-request-real-time-data.md",
105+
"redirect_url": "/azure/azure-maps",
106+
"redirect_document_id": false
107+
},
108+
{
109+
"source_path_from_root": "/articles/azure-maps/how-to-request-transit-data.md",
110+
"redirect_url": "/azure/azure-maps",
111+
"redirect_document_id": false
112+
},
113+
{
114+
"source_path_from_root": "/articles/azure-maps/indoor-map-dynamic-styling.md",
115+
"redirect_url": "/azure/azure-maps/about-creator",
116+
"redirect_document_id": false
117+
},
118+
{
119+
"source_path_from_root": "/articles/azure-maps/migrate-from-bing-maps-web-services.md",
120+
"redirect_url": "/azure/azure-maps/migrate-bing-maps-overview",
121+
"redirect_document_id": false
122+
},
123+
{
124+
"source_path_from_root": "/articles/azure-maps/migrate-from-bing-maps.md",
125+
"redirect_url": "/azure/azure-maps/migrate-bing-maps-overview",
126+
"redirect_document_id": false
127+
},
128+
{
129+
"source_path_from_root": "/articles/azure-maps/mobility-coverage.md ",
130+
"redirect_url": "/azure/azure-maps",
131+
"redirect_document_id": false
132+
},
133+
{
134+
"source_path_from_root": "/articles/azure-maps/mobility-service-data-structure.md",
135+
"redirect_url": "/azure/azure-maps",
136+
"redirect_document_id": false
137+
},
138+
{
139+
"source_path_from_root": "/articles/azure-maps/power-bi-visual-add-bar-chart-layer.md",
140+
"redirect_url": "/azure/azure-maps/power-bi-visual-add-3d-column-layer",
141+
"redirect_document_id": false
142+
},
143+
{
144+
"source_path_from_root": "/articles/azure-maps/power-bi-visual-getting-started.md",
145+
"redirect_url": "/azure/azure-maps/power-bi-visual-get-started",
146+
"redirect_document_id": false
147+
},
148+
{
149+
"source_path_from_root": "/articles/azure-maps/power-bi-visual-migrate-from-bing-maps.md",
150+
"redirect_url": "/azure/azure-maps/power-bi-visual-conversion",
151+
"redirect_document_id": false
152+
},
153+
{
154+
"source_path_from_root": "/articles/azure-maps/schema-stateset-stylesobject.md",
155+
"redirect_url": "/azure/azure-maps/about-creator",
156+
"redirect_document_id": false
157+
},
158+
{
159+
"source_path_from_root": "/articles/azure-maps/search-categories.md",
160+
"redirect_url": "/azure/azure-maps/supported-search-categories",
161+
"redirect_document_id": true
162+
},
163+
{
164+
"source_path_from_root": "/articles/azure-maps/tutorial-creator-feature-stateset.md",
165+
"redirect_url": "/azure/azure-maps/about-creator",
166+
"redirect_document_id": false
167+
},
168+
{
169+
"source_path_from_root": "/articles/azure-maps/tutorial-creator-indoor-maps.md",
170+
"redirect_url": "/azure/azure-maps/creator-indoor-maps",
171+
"redirect_document_id": false
172+
},
173+
{
174+
"source_path_from_root": "/articles/azure-maps/tutorial-creator-wfs.md",
175+
"redirect_url": "/azure/azure-maps/how-to-creator-wfs",
176+
"redirect_document_id": false
177+
},
178+
{
179+
"source_path_from_root": "/articles/azure-maps/tutorial-geofence.md",
180+
"redirect_url": "/azure/azure-maps/",
181+
"redirect_document_id": true
182+
}
183+
]
184+
}

‎articles/azure-resource-manager/bicep/linter-rule-no-unnecessary-dependson.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Linter rule - no unnecessary dependsOn entries
33
description: Linter rule - no unnecessary dependsOn entries
44
ms.topic: reference
55
ms.custom: devx-track-bicep
6-
ms.date: 07/11/2024
6+
ms.date: 10/11/2024
77
---
88

99
# Linter rule - no unnecessary dependsOn entries
@@ -18,7 +18,7 @@ Use the following value in the [Bicep configuration file](bicep-config-linter.md
1818

1919
## Solution
2020

21-
To reduce confusion in your template, delete any dependsOn entries that aren't necessary. Bicep automatically infers most resource dependencies as long as template expressions reference other resources via symbolic names rather than strings with hard-coded IDs or names.
21+
To reduce confusion in your template, delete any dependsOn entries that aren't necessary. Bicep automatically infers most resource dependencies as long as template expressions reference other resources via symbolic names rather than strings with hard-coded IDs or names.
2222

2323
The following example fails this test because the dependsOn entry `appServicePlan` is automatically inferred by Bicep implied by the expression `appServicePlan.id` (which references resource symbolic name `appServicePlan`) in the `serverFarmId` property's value.
2424

@@ -46,7 +46,7 @@ resource webApplication 'Microsoft.Web/sites@2023-12-01' = {
4646
}
4747
```
4848

49-
You can fix it by removing the unnecessary dependsOn entry.
49+
You can fix it by removing the unnecessary dependsOn entry:
5050

5151
```bicep
5252
param location string = resourceGroup().location
@@ -69,9 +69,9 @@ resource webApplication 'Microsoft.Web/sites@2023-12-01' = {
6969
}
7070
```
7171

72-
Use **Quick Fix** to remove the unnecessary dependsOn entry.
72+
Use **Quick Fix** to remove the unnecessary dependsOn entry:
7373

74-
:::image type="content" source="./media/linter-rule-no-unnecessary-dependson/linter-rule-no-unnecessary-dependson-quick-fix.png" alt-text="The screenshot of No unnecessary dependson linter rule with quick fix.":::
74+
:::image type="content" source="./media/linter-rule-no-unnecessary-dependson/linter-rule-no-unnecessary-dependson-quick-fix.png" alt-text="A screenshot of using Quick Fix for the no-unnecessary-dependson linter rule.":::
7575

7676
## Next steps
7777

‎articles/azure-resource-manager/bicep/media/linter-rule-no-unnecessary-dependson/linter-rule-no-unnecessary-dependson-quick-fix.png

42.6 KB
Loading

‎articles/backup/azure-backup-architecture-for-sap-hana-backup.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Azure Backup architecture for SAP HANA Backup
33
description: Learn about Azure Backup architecture for SAP HANA backup.
44
ms.topic: overview
5-
ms.date: 09/09/2024
5+
ms.date: 10/14/2024
66
ms.service: azure-backup
77
author: AbhishekMallick-MS
88
ms.author: v-abhmallick
@@ -76,7 +76,7 @@ This section provides you with an understanding about the backup process of an H
7676

7777
If you aren’t using firewall/NVA in your setup, then the backup stream is transferred over the Azure network to the Recovery Services vault / Azure Storage. Also, you can set up [Virtual Network Service Endpoint](../virtual-network/virtual-network-service-endpoints-overview.md) or [Private Endpoint](../private-link/private-endpoint-overview.md) to allow SAP HANA to send backup traffic directly to Recovery Services Vault / Azure Storage, skipping NVA/Azure Firewall. Additionally, when you use firewall/NVA, the traffic to Microsoft Entra ID and Azure Backup Service will pass through the firewall/NVA and it doesn’t affect the overall backup performance.
7878

79-
1. Azure Backup attempts to achieve speeds up to 420 MB/sec for non-log backups and up to 100 MB/sec for log backups. [Learn more](./tutorial-backup-sap-hana-db.md#understanding-backup-and-restore-throughput-performance) about backup and restore throughput performance.
79+
1. Azure Backup attempts to achieve speeds up to 420 MB/sec for non-log backups and up to 100 MB/sec for log backups. [Learn more](./tutorial-backup-sap-hana-db.md#understanding-the-backup-and-restore-throughput-performance) about backup and restore throughput performance.
8080

8181
1. Detailed logs are written to the *backup.log* and *backint.log* files on the SAP HANA instance.
8282

‎articles/backup/faq-backup-sql-server.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ metadata:
55
ms.reviewer: vijayts
66
ms.topic: faq
77
ms.service: azure-backup
8-
ms.date: 09/30/2024
8+
ms.date: 10/14/2024
99
author: AbhishekMallick-MS
1010
ms.author: v-abhmallick
1111

@@ -143,7 +143,7 @@ sections:
143143
- question: |
144144
Connecting the Azure environment to on-premises network using ExpressRoute and configured forced tunneling directs all the traffic to the on-premises network. How can I configure the settings so that Azure SQL Server workload backup traffic won't pass through the on-premises network and directly connects to Recovery Services vault?
145145
answer: |
146-
During the backup operation, the *backup job* connects to three Service Endpoints - `AzureBackup`, `AzureStorage`, and `Microsoft Entra ID. In this scenario, we recommend you to configure the Service Endpoint to `AzureStorage`, which helps to send the traffic from the Virtual Network to the Storage directly. For Azure Backup and Microsoft Entra ID, you can configure UDR over service tags so that the traffic travels to backbone network instead of on-premises.
146+
During the backup operation, the *backup job* connects to three Service Endpoints - `AzureBackup`, `AzureStorage`, and `Microsoft Entra ID`. In this scenario, we recommend you to configure the Service Endpoint to `AzureStorage`, which helps to send the traffic from the Virtual Network to the Storage directly. For Azure Backup and Microsoft Entra ID, you can configure UDR over service tags so that the traffic travels to backbone network instead of on-premises.
147147
148148
additionalContent: |
149149

0 commit comments

Comments
 (0)