format

Author: cherylmc

.openpublishing.redirection.json

@@ -1,5 +1,30 @@
 {
   "redirections": [
+    {
+      "source_path": "articles/partner-solutions/logzio/create.md",
+      "redirect_url": "/previous-versions/azure/partner-solutions/logzio/create",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/partner-solutions/logzio/manage.md",
+      "redirect_url": "/previous-versions/azure/partner-solutions/logzio/manage",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/partner-solutions/logzio/overview.md",
+      "redirect_url": "/previous-versions/azure/partner-solutions/logzio/overview",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/partner-solutions/logzio/setup-sso.md",
+      "redirect_url": "/previous-versions/azure/partner-solutions/logzio/setup-sso",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "articles/partner-solutions/logzio/troubleshoot.md",
+      "redirect_url": "/previous-versions/azure/partner-solutions/logzio/troubleshoot",
+       "redirect_document_id": false
+    },
     {
       "source_path": "articles/hdinsight-aks/cluster-storage.md",
       "redirect_url": "/previous-versions/azure/hdinsight-aks/cluster-storage",

articles/azure-maps/index.yml

@@ -45,8 +45,6 @@ landingContent:
             url: quick-demo-map-app.md
       - linkListType: concept
         links:
-          - text: Choose the right pricing tier for Maps account
-            url: choose-pricing-tier.md
           - text: Authentication with Azure Maps
             url: azure-maps-authentication.md
       - linkListType: how-to-guide

articles/azure-maps/toc.yml

@@ -46,8 +46,6 @@ items:
     href: authentication-best-practices.md
   - name: Azure Maps Event Grid integration
     href: azure-maps-event-grid-integration.md
-  - name: Choose the right pricing tier
-    href: choose-pricing-tier.md
   - name: Azure Maps geographic scope
     href: geographic-scope.md
   - name: Consent management

articles/databox-online/TOC.yml

@@ -511,7 +511,9 @@
         href: azure-stack-edge-contact-microsoft-support.md 
   - name: Shared release notes
     items:
-    - name: 2407 - Current
+    - name: 2501 - Current
+      href: azure-stack-edge-gpu-2501-release-notes.md
+    - name: 2407
       href: azure-stack-edge-gpu-2407-release-notes.md
     - name: 2403
       href: azure-stack-edge-gpu-2403-release-notes.md

articles/databox-online/azure-stack-edge-gpu-2501-release-notes.md

@@ -6,7 +6,7 @@ author: alkohli
 
 ms.service: azure-stack-edge
 ms.topic: how-to
-ms.date: 08/14/2024
+ms.date: 02/04/2025
 ms.author: alkohli
 ---
 # Update your Azure Stack Edge Pro GPU
@@ -22,59 +22,59 @@ Apply the software updates or hotfixes to keep your Azure Stack Edge Pro device
 
 ## About latest updates
 
-The current version is Update 2407. This update installs two updates, the device update followed by Kubernetes updates. 
+The current version is Update 2501. This update installs two updates, the device update followed by Kubernetes updates. 
 
 The associated versions for this update are:
 
-- Device software version: Azure Stack Edge 2407 (3.2.2754.1029).
-- Device Kubernetes version: Azure Stack Kubernetes Edge 2407 (3.2.2754.1029).
+- Device software version: Azure Stack Edge 2501 (3.3.2501.1176).
+- Device Kubernetes version: Azure Stack Kubernetes Edge 2501 (3.3.2501.1176).
 - Device Kubernetes workload profile: Other workloads.
-- Kubernetes server version: v1.28.5.
+- Kubernetes server version: v1.29.4.
 - IoT Edge version: 0.1.0-beta15.
-- Azure Arc version: 1.16.10.
-- GPU driver version: 535.161.08.
+- Azure Arc version: 1.19.2.
+- GPU driver version: 535.183.06.
 - CUDA version: 12.2.
 
-For information on what's new in this update, go to [Release notes](azure-stack-edge-gpu-2407-release-notes.md).
+For information on what's new in this update, go to [Release notes](azure-stack-edge-gpu-2501-release-notes.md).
 
-**To apply the 2407 update, your device must be running version 2403 or later.**
+**To apply the 2501 update, your device must be running version 2403 or later.**
 
 - If you aren't running the minimum required version, you see this error:
 
   *Update package can't be installed as its dependencies aren't met.*
 
-- You can update to 2403 from 2303 or later, and then install 2407.
+- You can update to 2403 from 2303 or later, and then install 2501.
 
 Supported update paths:
 
-| Current version of Azure Stack Edge software and Kubernetes | Upgrade to Azure Stack Edge software and Kubernetes | Desired update to 2407 |
+| Current version of Azure Stack Edge software and Kubernetes | Upgrade to Azure Stack Edge software and Kubernetes | Desired update to 2501 |
 |-------|----------|------------ |
-| 2303  | 2403  | 2407  |
-| 2309  | 2403  | 2407  |
-| 2312  | 2403  | 2407  |
-| 2403  | Directly to | 2407  |
+| 2303  | 2403  | 2501  |
+| 2309  | 2403  | 2501  |
+| 2312  | 2403  | 2501  |
+| 2403  | Directly to | 2501  |
 
 ### Update Azure Kubernetes service on Azure Stack Edge
 
 > [!IMPORTANT]
 > Use the following procedure only if you are an SAP or a PMEC customer.
 
-If you have Azure Kubernetes service deployed and your Azure Stack Edge device and Kubernetes versions are either 2207 or 2209, you must update in multiple steps to apply 2407.
+If you have Azure Kubernetes service deployed and your Azure Stack Edge device and Kubernetes versions are either 2207 or 2209, you must update in multiple steps to apply 2501.
 
 Use the following steps to update your Azure Stack Edge version and Kubernetes version to 2407:
 
 1. Update your device version to 2403.
 1. Update your Kubernetes version to 2210.
 1. Update your Kubernetes version to 2403.
-1. Update both device software and Kubernetes to 2407.
+1. Update both device software and Kubernetes to 2501.
 
-If you're running 2210 or 2301, you can update both your device version and Kubernetes version directly to 2403 and then to 2407.
+If you're running 2210 or 2301, you can update both your device version and Kubernetes version directly to 2403 and then to 2501.
 
-If you're running 2403, you can update both your device version and Kubernetes version directly to 2407.
+If you're running 2403, you can update both your device version and Kubernetes version directly to 2501.
 
-In Azure portal, the process requires two clicks, the first update gets your device version to 2403 and your Kubernetes version to 2210, and the second update gets your Kubernetes version upgraded to 2407.
+In Azure portal, the process requires two clicks, the first update gets your device version to 2403 and your Kubernetes version to 2210, and the second update gets your Kubernetes version upgraded to 2501.
 
-From the local UI, you'll have to run each update separately: update the device version to 2403, update Kubernetes version to 2210, update Kubernetes version to 2403, and then the third update gets both the device version and Kubernetes version to 2407.
+From the local UI, you'll have to run each update separately: update the device version to 2403, update Kubernetes version to 2210, update Kubernetes version to 2403, and then the third update gets both the device version and Kubernetes version to 2501.
 
 Each time you change the Kubernetes profile, you're prompted for the Kubernetes update. Go ahead and apply the update.
 
@@ -231,7 +231,7 @@ Do the following steps to download the update from the Microsoft Update Catalog.
 
 1. In the search box of the Microsoft Update Catalog, enter the Knowledge Base (KB) number of the hotfix or terms for the update you want to download. For example, enter **Azure Stack Edge**, and then select **Search**.
 
-    The update listing appears as **Azure Stack Edge Update 2403**.
+    The update listing appears as **Azure Stack Edge Update 2501**.
 
     > [!NOTE]
     > Make sure to verify which workload you are running on your device [via the local UI](./azure-stack-edge-gpu-deploy-configure-network-compute-web-proxy.md#configure-compute-ips-1) or [via the PowerShell](./azure-stack-edge-connect-powershell-interface.md) interface of the device. Depending on the workload that you are running, the update package will differ.
@@ -275,7 +275,7 @@ This procedure takes around 20 minutes to complete. Perform the following steps
 
 5. The update starts. After the device is successfully updated, it restarts. The local UI isn't accessible in this duration.
 
-6. After the restart is complete, you're taken to the **Sign in** page. To verify that the device software has been updated, in the local web UI, go to **Maintenance** > **Software update**. For the current release, the displayed software version should be **Azure Stack Edge 2403**. 
+6. After the restart is complete, you're taken to the **Sign in** page. To verify that the device software has been updated, in the local web UI, go to **Maintenance** > **Software update**. For the current release, the displayed software version should be **Azure Stack Edge 2501**. 
 
 
 7. You'll now update the Kubernetes software version. Select the remaining two Kubernetes files together (file with the *Kubernetes_Package.0.exe* and *Kubernetes_Package.1.exe* suffix) and repeat the above steps to apply update.   

articles/databox-online/azure-stack-edge-gpu-install-update.md

@@ -1,23 +1,18 @@
 ---
-title: Fallback to internet for Azure Private DNS zones (Preview)
+title: Fallback to internet for Azure Private DNS zones
 titleSuffix: Azure DNS
 description: Learn how to enable fallback to internet resolution for private DNS.
 services: dns
 author: greg-lindsay
 ms.service: azure-dns
-ms.date: 11/24/2024
+ms.date: 02/04/2025
 ms.author: greglin
 ms.topic: how-to
 ---
 
-# Fallback to internet for Azure Private DNS zones (Preview)
+# Fallback to internet for Azure Private DNS zones
 
-This article shows you how to set the [ResolutionPolicy](/java/api/com.azure.resourcemanager.privatedns.models.resolutionpolicy) property in Azure Private DNS to enable fallback to internet recursion when an authoritative NXDOMAIN response is received for a Private Link zone. On the DNS client side, there's no response to the DNS query.
-
-> [!NOTE]
-> Fallback to internet for Azure Private DNS is in PREVIEW.<br> 
-> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.<br><br>
-> This internet fallback policy preview is offered without a requirement to enroll in a pre-release feature preview.
+This article shows you how to set the [ResolutionPolicy](/java/api/com.azure.resourcemanager.privatedns.models.resolutionpolicy) property in Azure Private DNS to enable fallback to internet recursion when an authoritative NXDOMAIN response is received for a Private Link zone. NXDOMAIN is also known as a negative response. When a DNS resolver receives (or has cached) a negative response, it sends no DNS response to the DNS client and the query fails.
 
 ## Problem
 
@@ -101,7 +96,7 @@ This guide assumes you have provisioned the prerequisite resources before procee
 
     > [!NOTE]
     > Storage accounts that are in the same resource group have resource records in the same Private DNS zone.<br>
-    > Storage accounts that are in different resource groups have resource records in different (identically-named) Private DNS zones.
+    > Storage accounts that are in different resource groups have resource records in different (identically named) Private DNS zones.
 
 ## Demonstrate DNS resolution failure
 

articles/databox-online/media/azure-stack-edge-gpu-install-update/portal-update-17.png

@@ -1,14 +1,14 @@
 ---
-title: Use service principals to automate workflows in Firmware analysis
-description: Learn about how to use service principals to automate workflows for Firmware Analysis.
+title: Use service principals to automate workflows in firmware analysis
+description: Learn about how to use service principals to automate workflows for firmware analysis.
 author: karengu0
 ms.author: karenguo
 ms.topic: conceptual
 ms.date: 11/04/2024
 ms.service: azure
 ---
 
-# How to Use Service Principals to Automate Workflows in Firmware analysis
+# How to Use Service Principals to Automate Workflows in firmware analysis
 
 Many users of the firmware analysis service may need to automate their workflow. The command `az login` creates an interactive login experience with two-factor authentication that makes it difficult for users to fully automate their workflow. A [service principal](/entra/identity-platform/app-objects-and-service-principals) is a secure identity with proper permissions that authenticates to Azure in the command line without requiring two-factor authentication or an interactive log-in. This article explains how to create a service principal and use it to interact with the firmware analysis service. For more information on creating service principals, visit [Create Azure service principals using the Azure CLI](/cli/azure/azure-cli-sp-tutorial-1#create-a-service-principal). To authenticate securely, we recommend creating a service principal and authenticating using certificates. To learn more, visit [Create a service principal containing a certificate using Azure CLI](/cli/azure/azure-cli-sp-tutorial-3).
 
@@ -44,9 +44,12 @@ Many users of the firmware analysis service may need to automate their workflow.
     az login --service-principal --username <CLIENT_ID> --password <SECRET> --tenant <TENANT_ID>
     ```
 
-6.	Once logged in, refer to the following Quickstarts for scripts to interact with the Firmware analysis service via Azure PowerShell, Azure CLI, or Python:
+6.	Once logged in, refer to the following Quickstarts for scripts to interact with the firmware analysis service via Azure PowerShell, Azure CLI, or Python:
     - [Upload firmware using Azure CLI](quickstart-upload-firmware-using-azure-command-line-interface.md)
     - [Upload firmware using Azure PowerShell](quickstart-upload-firmware-using-powershell.md)
     - [Upload firmware using Python](quickstart-upload-firmware-using-python.md)
+ 
 
-
+#test
+test
+test