Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into mdb-mhn-additions

Author: RoseHJM

.openpublishing.redirection.json

@@ -6,7 +6,7 @@ author: kengaderdus
 manager: CelesteDG
 ms.service: azure-active-directory
 ms.topic: how-to
-ms.date: 01/11/2024
+ms.date: 10/14/2024
 ms.author: kengaderdus
 ms.subservice: b2c
 zone_pivot_groups: b2c-policy-type
@@ -276,7 +276,10 @@ A claim provides temporary storage of data during an Azure AD B2C policy executi
 
 ### Acquiring an access token 
 
-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.
+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.
+
+> [!WARNING]
+> 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.
 
 <a name='acquiring-an-azure-ad-access-token-'></a>
 
@@ -577,12 +580,12 @@ The following XML snippet is an example of a RESTful technical profile configure
 ```
 ::: zone-end
 
-## Next steps
+## Related content
 
 ::: zone pivot="b2c-user-flow"
 - Get started with our [samples](api-connector-samples.md#api-connector-rest-api-samples).
 ::: zone-end
 
 ::: zone pivot="b2c-custom-policy"
 - Learn more about the [Restful technical profile](restful-technical-profile.md) element in the custom policy reference.
-::: zone-end
+::: zone-end

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

@@ -80,7 +80,6 @@
             "redirect_url": "/azure/application-gateway/tutorial-protect-application-gateway-ddos",
             "redirect_document_id": false
         },
-        
         {
             "source_path_from_root": "/articles/application-gateway/rewrite-http-headers.md",
             "redirect_url": "/azure/application-gateway/rewrite-http-headers-url",
@@ -305,6 +304,46 @@
             "source_path_from_root": "/articles/application-gateway/application-gateway-web-app-overview.md",
             "redirect_url": "/azure/application-gateway/configure-web-app",
             "redirect_document_id": false
-        }
+        },
+        {
+            "source_path_from_root": "/articles/application-gateway/powershell-samples.md",
+            "redirect_url": "/previous-versions/azure/application-gateway/powershell-samples",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/application-gateway/cli-samples.md",
+            "redirect_url": "/previous-versions/azure/application-gateway/cli-samples",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/application-gateway/resource-manager-template-samples.md",
+            "redirect_url": "/previous-versions/azure/application-gateway/resource-manager-template-samples",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/application-gateway/scripts/create-vmss-cli.md",
+            "redirect_url": "/previous-versions/azure/application-gateway/scripts/create-vmss-cli",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/application-gateway/scripts/create-vmss-powershell.md",
+            "redirect_url": "/previous-versions/azure/application-gateway/scripts/create-vmss-powershell",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/application-gateway/scripts/create-vmss-waf-cli.md",
+            "redirect_url": "/previous-versions/azure/application-gateway/scripts/create-vmss-waf-cli",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/application-gateway/scripts/create-vmss-waf-powershell.md",
+            "redirect_url": "/previous-versions/azure/application-gateway/scripts/create-vmss-waf-powershell",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/application-gateway/scripts/waf-custom-rules-powershell.md",
+            "redirect_url": "/previous-versions/azure/application-gateway/scripts/waf-custom-rules-powershell",
+            "redirect_document_id": false
+        },
     ]
-}
+}

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

@@ -6,8 +6,7 @@ summary: Use Azure Edge Hardware Center service to order from a variety of Azure
 metadata:
   title: Azure Edge Hardware Center documentation
   description: Azure Edge Hardware Center Documentation.
-  ms.service: databox
-  ms.subservice: edge
+  ms.service: azure-stack-edge
   ms.topic: landing-page
   author: alkohli
   ms.author: alkohli

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

@@ -0,0 +1,184 @@
+{
+    "redirections": [
+        {
+            "source_path_from_root": "/articles/location-based-services/about-location-based-services.md",
+            "redirect_url": "/azure/azure-maps/about-azure-maps",
+            "redirect_document_id": true
+        },
+        {
+            "source_path_from_root": "/articles/location-based-services/geocoding-coverage.md",
+            "redirect_url": "/azure/azure-maps/geocoding-coverage",
+            "redirect_document_id": true
+        },
+        {
+            "source_path_from_root": "/articles/location-based-services/how-to-manage-account-keys.md",
+            "redirect_url": "/azure/azure-maps/how-to-manage-account-keys",
+            "redirect_document_id": true
+        },
+        {
+            "source_path_from_root": "/articles/location-based-services/how-to-search-for-address.md",
+            "redirect_url": "/azure/azure-maps/how-to-search-for-address",
+            "redirect_document_id": true
+        },
+        {
+            "source_path_from_root": "/articles/location-based-services/how-to-use-map-control.md",
+            "redirect_url": "/azure/azure-maps/how-to-use-map-control",
+            "redirect_document_id": true
+        },
+        {
+            "source_path_from_root": "/articles/location-based-services/index.md",
+            "redirect_url": "/azure/azure-maps/index",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/location-based-services/quick-demo-map-app.md",
+            "redirect_url": "/azure/azure-maps/quick-demo-map-app",
+            "redirect_document_id": true
+        },
+        {
+            "source_path_from_root": "/articles/location-based-services/render-coverage.md",
+            "redirect_url": "/azure/azure-maps/render-coverage",
+            "redirect_document_id": true
+        },
+        {
+            "source_path_from_root": "/articles/location-based-services/routing-coverage.md",
+            "redirect_url": "/azure/azure-maps/routing-coverage",
+            "redirect_document_id": true
+        },
+        {
+            "source_path_from_root": "/articles/location-based-services/supported-languages.md",
+            "redirect_url": "/azure/azure-maps/supported-languages",
+            "redirect_document_id": true
+        },
+        {
+            "source_path_from_root": "/articles/location-based-services/traffic-coverage.md",
+            "redirect_url": "/azure/azure-maps/traffic-coverage",
+            "redirect_document_id": true
+        },
+        {
+            "source_path_from_root": "/articles/location-based-services/tutorial-prioritized-routes.md",
+            "redirect_url": "/azure/azure-maps/tutorial-prioritized-routes",
+            "redirect_document_id": true
+        },
+        {
+            "source_path_from_root": "/articles/location-based-services/tutorial-route-location.md",
+            "redirect_url": "/azure/azure-maps/tutorial-route-location",
+            "redirect_document_id": true
+        },
+        {
+            "source_path_from_root": "/articles/location-based-services/tutorial-search-location.md",
+            "redirect_url": "/azure/azure-maps/tutorial-search-location",
+            "redirect_document_id": true
+        },
+        {
+            "source_path_from_root": "/articles/location-based-services/zoom-levels-and-tile-grid.md",
+            "redirect_url": "/azure/azure-maps/zoom-levels-and-tile-grid",
+            "redirect_document_id": true
+        },
+        {
+            "source_path_from_root": "/articles/azure-maps/tutorial-iot-hub-maps.md",
+            "redirect_url": "/azure/azure-maps",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-maps/about-creator.md",
+            "redirect_url": "/azure/azure-maps/creator-indoor-maps",
+            "redirect_document_id": true
+        },
+        {
+            "source_path_from_root": "/articles/azure-maps/choose-pricing-tier.md",
+            "redirect_url": "/azure/azure-maps/how-to-manage-pricing-tier",
+            "redirect_document_id": true
+        },
+        {
+            "source_path_from_root": "/articles/azure-maps/how-to-creator-feature-stateset.md",
+            "redirect_url": "/azure/azure-maps/about-creator",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-maps/how-to-request-elevation-data.md",
+            "redirect_url": "https://azure.microsoft.com/updates/azure-maps-elevation-apis-and-render-v2-dem-tiles-will-be-retired-on-5-may-2023",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-maps/how-to-request-real-time-data.md",
+            "redirect_url": "/azure/azure-maps",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-maps/how-to-request-transit-data.md",
+            "redirect_url": "/azure/azure-maps",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-maps/indoor-map-dynamic-styling.md",
+            "redirect_url": "/azure/azure-maps/about-creator",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-maps/migrate-from-bing-maps-web-services.md",
+            "redirect_url": "/azure/azure-maps/migrate-bing-maps-overview",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-maps/migrate-from-bing-maps.md",
+            "redirect_url": "/azure/azure-maps/migrate-bing-maps-overview",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-maps/mobility-coverage.md ",
+            "redirect_url": "/azure/azure-maps",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-maps/mobility-service-data-structure.md",
+            "redirect_url": "/azure/azure-maps",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-maps/power-bi-visual-add-bar-chart-layer.md",
+            "redirect_url": "/azure/azure-maps/power-bi-visual-add-3d-column-layer",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-maps/power-bi-visual-getting-started.md",
+            "redirect_url": "/azure/azure-maps/power-bi-visual-get-started",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-maps/power-bi-visual-migrate-from-bing-maps.md",
+            "redirect_url": "/azure/azure-maps/power-bi-visual-conversion",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-maps/schema-stateset-stylesobject.md",
+            "redirect_url": "/azure/azure-maps/about-creator",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-maps/search-categories.md",
+            "redirect_url": "/azure/azure-maps/supported-search-categories",
+            "redirect_document_id": true
+        },
+        {
+            "source_path_from_root": "/articles/azure-maps/tutorial-creator-feature-stateset.md",
+            "redirect_url": "/azure/azure-maps/about-creator",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-maps/tutorial-creator-indoor-maps.md",
+            "redirect_url": "/azure/azure-maps/creator-indoor-maps",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-maps/tutorial-creator-wfs.md",
+            "redirect_url": "/azure/azure-maps/how-to-creator-wfs",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/azure-maps/tutorial-geofence.md",
+            "redirect_url": "/azure/azure-maps/",
+            "redirect_document_id": true
+        }
+    ]
+}

articles/azure-fluid-relay/images/container-multiple-users.png

@@ -119,6 +119,7 @@ You can enable Azure NetApp Files storage with cool access during the creation o
 
     * **Enable Cool Access**: This option specifies whether the volume supports cool access.
     * **Coolness Period**: This option specifies the period (in days) after which infrequently accessed data blocks (cold data blocks) are moved to the Azure storage account. The default value is 31 days. The supported values are between 2 and 183 days.
+
     * **Cool Access Retrieval Policy**: This option specifies under which conditions data moves back to the hot tier. You can set this option to **Default**, **On-Read**, or **Never**.
 
         The following list describes the data retrieval behavior with the **Cool Access Retrieval Policy** settings:
@@ -148,6 +149,8 @@ In a capacity pool enabled for cool access, you can enable an existing volume to
 1. On the **Edit** window that appears, set the following options for the volume:
     * **Enable Cool Access**: This option specifies whether the volume supports cool access.
     * **Coolness Period**: This option specifies the period (in days) after which infrequently accessed data blocks (cold data blocks) are moved to the Azure storage account. The default value is 31 days. The supported values are between 2 and 183 days.
+    >[!NOTE]
+    > The coolness period is calculated from the time of volume creation. If any existing volumes are enabled with cool access, the coolness period is applied retroactively on those volumes. This means if certain data blocks on the volumes have been infrequently accessed for the number of days specified in the coolness period, those blocks move to the cool tier once the feature is enabled. 
     * **Cool Access Retrieval Policy**: This option specifies under which conditions data moves back to the hot tier. You can set this option to **Default**, **On-Read**, or **Never**.
 
         The following list describes the data retrieval behavior with the **Cool Access Retrieval Policy** settings:

articles/azure-fluid-relay/images/deployment-complete.png

@@ -3,7 +3,7 @@ title: Linter rule - no unnecessary dependsOn entries
 description: Linter rule - no unnecessary dependsOn entries
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 07/11/2024
+ms.date: 10/11/2024
 ---
 
 # Linter rule - no unnecessary dependsOn entries
@@ -18,7 +18,7 @@ Use the following value in the [Bicep configuration file](bicep-config-linter.md
 
 ## Solution
 
-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.
+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.
 
 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.
 
@@ -46,7 +46,7 @@ resource webApplication 'Microsoft.Web/sites@2023-12-01' = {
 }
 ```
 
-You can fix it by removing the unnecessary dependsOn entry.
+You can fix it by removing the unnecessary dependsOn entry:
 
 ```bicep
 param location string = resourceGroup().location
@@ -69,9 +69,9 @@ resource webApplication 'Microsoft.Web/sites@2023-12-01' = {
 }
 ```
 
-Use **Quick Fix** to remove the unnecessary dependsOn entry.
+Use **Quick Fix** to remove the unnecessary dependsOn entry:
 
-:::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.":::
+:::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.":::
 
 ## Next steps