Merge pull request #303706 from MicrosoftDocs/main

Auto Publish – main to live - 2025-08-01 05:00 UTC

Author: learn-build-service-prod[bot]

articles/education-hub/faq.md

@@ -5,7 +5,7 @@ author: vinnieangel
 ms.author: vangellotti
 ms.service: azure-education
 ms.topic: tutorial
-ms.date: 7/11/2025
+ms.date: 7/31/2025
 ms.custom: template-tutorial
 ---
 
@@ -48,7 +48,6 @@ For more information, see the [terms and conditions for the Azure for Students o
       SQL Server Developer<br>
    :::column-end:::
    :::column span="":::
-      SQL Server Mobile Report Publisher<br>
       SQL Server Standard<br>
       System Center<br>
       Visio Professional<br>
@@ -152,7 +151,7 @@ If your institution has an active VL agreement but has not yet signed up for the
 
 ### How will my students get access to Azure Dev Tools for Teaching after August 15th, 2025? 
 
-If your institution is signed up for Azure Dev Tools for Teaching, your students will now be getting access to their software benefit through the Azure for Students offer. This provides them with the same software, in the same location they currently access. In addition, they will receive an Azure subscription with $100 free Azure credit to use on Azure services. No credit card is required to sign up, simply sign in with their institution ID as they do today. If they use the current redemption link for Azure Dev Tools for Teaching, they will be redirected to sign up for Azure for Students. To learn more about Azure for Students, click here.  
+If your institution is signed up for Azure Dev Tools for Teaching, your students will now be getting access to their software benefit through the Azure for Students offer. This provides them with the same software, in the same location they currently access. In addition, they will receive an Azure subscription with $100 free Azure credit to use on Azure services. No credit card is required to sign up, simply sign in with their institution ID as they do today. If they use the current redemption link for Azure Dev Tools for Teaching, they will be redirected to sign up for Azure for Students. To learn more about Azure for Students, [click here](https://azure.microsoft.com/free/students).  
 
 ### If I have additional questions about this change, who can I contact? 
 
@@ -181,7 +180,6 @@ If you're currently an Azure Dev Tools for Teaching customer without a Volume Li
       SQL Server Developer<br>
    :::column-end:::
    :::column span="":::
-      SQL Server Mobile Report Publisher<br>
       SQL Server Standard<br>
       System Center<br>
       Visio Professional<br>

articles/logic-apps/logic-apps-limits-and-config.md

@@ -5,7 +5,7 @@ services: logic-apps
 ms.suite: integration
 ms.reviewer: rohithah, laveeshb, rarayudu, azla
 ms.topic: reference
-ms.date: 07/18/2025
+ms.date: 07/31/2025
 ---
 
 # Limits and configuration reference for Azure Logic Apps
@@ -56,7 +56,7 @@ The following table lists the values for a single workflow run:
 
 | Name | Multitenant | Single-tenant | Notes |
 |------|-------------|---------------|-------|
-| Run history retention in storage | 90 days | 90 days <br>(Default) | The amount of time to keep a workflow's run history in storage after a run starts. <br><br>**Note**: If the workflow's run duration exceeds the retention limit, this run is removed from the run history in storage. If a run isn't immediately removed after reaching the retention limit, the run is removed within 7 days. <br><br>Whether a run completes or times out, run history retention is always calculated by using the run's start time and the current limit specified in the workflow setting, [**Run history retention in days**](#change-retention). No matter the previous limit, the current limit is always used for calculating retention. <br><br>For more information, review [Change duration and run history retention in storage](#change-retention). |
+| Run history retention in storage | 90 days | 90 days <br>(Default) | The amount of time to keep a workflow's run history in storage after a run starts. <br><br>**Note**: If the workflow's run duration exceeds the retention limit, this run is removed from the run history in storage. If a run isn't immediately removed after reaching the retention limit, the run is removed within 7 days. <br><br>Whether a run completes or times out, retention is always calculated by using the run's start time and the retention limit at the *time when the run started*, not the current limit. You can find the retention limit in the workflow setting, [**Run history retention in days**](#change-retention). <br><br>For more information, review [Change duration and run history retention in storage](#change-retention). |
 | Run duration | 90 days | - Stateful workflow: 90 days <br>(Default) <br><br>- Stateless workflow: 5 min <br>(Default) | The amount of time that a workflow can continue running before forcing a time-out. The run duration is calculated by using a run's start time and the limit that's specified in the workflow setting, [**Run history retention in days**](#change-duration) at that start time. <br><br>**Important**: Make sure the run duration value is always less than or equal to the run history retention in storage value. Otherwise, run histories might be deleted before the associated jobs are complete. <br><br>For more information, review [Change run duration and history retention in storage](#change-duration). |
 | Recurrence interval | - Min: 1 sec <br><br>- Max: 500 days | - Min: 1 sec <br><br>- Max: 500 days ||
 
@@ -73,7 +73,7 @@ For Consumption logic app workflows, the same setting controls the maximum numbe
 
 * In multitenant Azure Logic Apps, the 90-day default limit is the same as the maximum limit. You can only decrease this value.
 
-For example, suppose that you reduce the retention limit from 90 days to 30 days. A 60-day-old run is removed from the run history. If you increase the retention period from 30 days to 60 days, a 20-day-old run stays in the run history for another 40 days.
+* Run history retention is always calculated by using the run's start time and the retention limit at the time when the run started, not the current retention limit. 
 
 #### Portal
 
@@ -120,6 +120,8 @@ For Standard logic app workflows, you can decrease or increase the 90-day defaul
 
 By default, the app setting named **Workflows.RuntimeConfiguration.RetentionInDays** is set to keep 90 days of data. The host setting named **Runtime.FlowMaintenanceJob.RetentionCooldownInterval** is set to check every 7 days for old data to delete. If you leave these default values, you might see data *up to* 97 days old. For example, suppose Azure Logic Apps checks on Day X and deletes data older than Day X - 90 days, and then waits for 7 days before running again. This behavior results in data that ages up to 97 days before the job runs again. However, if you set the interval to 1 day, but leave the retention days at the default value, the maximum delay to delete old data is 90+1 days.
 
+Run history retention is always calculated by using the run's start time and the retention limit at the time when the run started, not the current retention limit. 
+
 #### Portal
 
 1. [Follow these steps to add the app setting named **Workflows.RuntimeConfiguration.RetentionInDays**](edit-app-settings-host-settings.md?tabs=azure-portal#manage-app-settings), and set the value to the number days that you want to keep your workflow run history.

articles/partner-solutions/index.yml

@@ -78,7 +78,7 @@ productDirectory:
       links:
         - url: ./new-relic/new-relic-overview.md
           text: Get end-to-end cloud observability to analyze and troubleshoot performance of applications, infrastructure, logs, real-user monitoring and more.
-    - title: MongoDB Atlas (preview)
+    - title: MongoDB Atlas
       imageSrc: ./media/index/mongo-db.svg
       links:
         - url: ./mongo-db/overview.md
@@ -93,7 +93,7 @@ productDirectory:
       links:
         - url: ./palo-alto/palo-alto-overview.md
           text: Protect your organization with a next generation firewall solution integrated with Azure.
-    - title: Pure Storage (preview)
+    - title: Pure Storage Preview
       imageSrc: ./media/index/pure-storage.svg
       links:
         - url: pure-storage/overview.md

articles/partner-solutions/palo-alto/.openpublishing.redirection.partner-solutions-palo-alto.json

@@ -24,6 +24,11 @@
             "source_path_from_root": "/articles/partner-solutions/palo-alto/palo-alto-troubleshoot.md",
             "redirect_url": "/azure/partner-solutions/palo-alto/troubleshoot",
             "redirect_document_id": true
-        }
+        },
+        {
+            "source_path_from_root": "/articles/partner-solutions/palo-alto/troubleshoot.md",
+            "redirect_url": "/troubleshoot/azure/partner-solutions/welcome-native-integrations",
+            "redirect_document_id": false
+        } 
     ]
 }

articles/partner-solutions/palo-alto/manage.md

@@ -40,8 +40,9 @@ To change the Cloud NGFW's billing plan, go to **Overview** and select **Change
 > [!NOTE]
 > The **Delete** button on the resource is activated only if all connected resources are already deleted. For more information, see [Azure Resource Manager resource group and resource deletion](/azure/azure-resource-manager/management/delete-resource-group).
 
-## Next step
+## Related content
 
-- For help with troubleshooting, see [Troubleshooting Palo Alto integration with Azure](troubleshoot.md).
+- [Azure Virtual Network FAQ](../../virtual-network/virtual-networks-faq.md)
+- [Virtual WAN FAQ](../../virtual-wan/virtual-wan-faq.md)
 
 

articles/partner-solutions/palo-alto/toc.yml

@@ -8,13 +8,13 @@ items:
 - name: Quickstarts
   expanded: true
   items:
-  - name: Create a Cloud NGFW by Palo Alto Networks resource
+  - name: Create a resource
     href: create.md
 - name: How to
   items:
-  - name: Manage your Cloud NGFW by Palo Alto Networks resource
+  - name: Manage your resource
     href: manage.md
-  - name: Troubleshoot Cloud NGFW by Palo Alto Networks 
-    href: troubleshoot.md
+  - name: Troubleshoot
+    href: /troubleshoot/azure/partner-solutions/welcome-native-integrations
   - name: Deploy Cloud NGFW by Palo Alto Networks with the Application Gateway
     href: application-gateway.md

articles/partner-solutions/palo-alto/troubleshoot.md

@@ -83,8 +83,8 @@ This section provides links to reliability guidance for many Azure services. Eac
 |Azure Health Data Services: De-identification service (preview)|[Reliability in Azure Health Data Services: De-identification service](reliability-health-data-services-deidentification.md)||
 |Azure Health Data Services: Workspace services (FHIR®, DICOM®, MedTech) | | [Business continuity and disaster recovery considerations](/azure/healthcare-apis/business-continuity-disaster-recovery?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json) |
 |Azure HDInsight| [Reliability in Azure HDInsight](reliability-hdinsight.md)||
-|Azure IoT Hub|| [Reliability in Azure IoT Hub](reliability-iot-hub.md) |
-|Azure Key Vault|| [Reliability in Azure Key Vault](./reliability-key-vault.md) |
+|Azure IoT Hub| [Reliability in Azure IoT Hub](reliability-iot-hub.md) ||
+|Azure Key Vault| [Reliability in Azure Key Vault](./reliability-key-vault.md) ||
 |Azure Kubernetes Service (AKS)| [Reliability in Azure Kubernetes Service (AKS)](reliability-aks.md)||
 |Azure Load Balancer| [Reliability in Azure Load Balancer](reliability-load-balancer.md )||
 |Azure Logic Apps|[Reliability in Azure Logic Apps](reliability-logic-apps.md) ||