Merge pull request #312981 from MicrosoftDocs/main

3/11/2026 11:30 AM IST Publish

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

articles/automation/index.yml

@@ -7,7 +7,7 @@ metadata:
 
   ms.service: azure-automation
   ms.topic: landing-page
-  ms.date: 11/14/2025
+  ms.date: 03/09/2025
   ms.author: v-rochak2
   author: RochakSingh-blr
 
@@ -100,4 +100,17 @@ landingContent:
       - linkListType: architecture
         links:
           - text: Recommendations to implement Automation
-            url: /azure/well-architected/operational-excellence/automate-tasks#evaluate-tasks-to-automate
+            url: /azure/well-architected/operational-excellence/automate-tasks#evaluate-tasks-to-automate
+
+  - title: Troubleshoot Azure Automation
+    linkLists:
+      - linkListType: how-to-guide
+        links:
+          - text: Troubleshoot Runbook Issues
+            url: troubleshoot/runbooks.md
+          - text: Troubleshoot Extension-based Hybrid Runbook Worker Issues
+            url: troubleshoot/extension-based-hybrid-runbook-worker.md
+          - text: Troubleshoot Managed Identity Issues
+            url: troubleshoot/managed-identity.md
+          - text: Data to Collect when Opening a Case for Azure Automation
+            url: troubleshoot/collect-data-microsoft-azure-automation-case.md

articles/azure-netapp-files/object-rest-api-introduction.md

@@ -21,6 +21,12 @@ This mapping is accomplished by presenting a specified NAS directory hierarchy a
 * Object REST API buckets are associated with volumes. Deleting the volume associated with a bucket permanently deletes the bucket. This action can't be undone. 
 * Buckets are supported with cool access-enabled volumes and with large volumes. 
 * You are responsible for maintaining the lifecycle of your bucket certificates. To check the expiration and renew certificates view the **Bucket** menu then check the **Certificate** status and **Certificate expiration date** fields. 
+* You must enable diagnostic logging on all Azure Key Vaults to ensure audit trails are available for security investigations.
+* You must configure network access control lists (ACLs) to restrict Key Vault access to only authorized networks (NetApp VNet and customer VNet).
+* It is recommended to implement separate Azure Key Vaults for certificates (read-only access) and S3 credentials (write access) to adhere to the principle of least privilege.
+* It is recommended to store Azure Key Vaults object references for certificates and credentials in separate buckets to maintain proper access control boundaries.
+* Buckets are not supported on Azure NetApp Files cache volumes.
+
 
 ## Supported actions
 

articles/backup/secure-by-default.md

@@ -30,7 +30,7 @@ Secure by default with soft delete is available in the following regions:
 
 | Vault type               | Availability type    | Regions                                      |
 |--------------------------|----------------------|---------------------------------------------|
-| Recovery Services vault  | General availability | West Central US                            |
+| Recovery Services vault  | General availability | West Central US, East Asia, Australia East |
 | Recovery Services vault  | Preview              | All remaining Azure public regions         |
 | Backup vault             | Preview              | Australia East, West Central US, East Asia |
 

articles/backup/threat-detection-overview.md

@@ -55,7 +55,7 @@ The following table describes the available summary statuses for source scans in
 
 ## Supported regions for threat detection for Azure VM backups
 
-Threat detection for Azure VM backups is available in preview in these regions: West Central US, Australia East, North Europe, Switzerland North, West Europe, Central US, East US, East US2, West US, UK South, UK West, Canada Central, Japan East, Japan West, India Central, India South, India West.
+Threat detection for Azure VM backups is available in preview in these regions: West Central US, Australia East, North Europe, Switzerland North, West Europe, Central US, East US, East US2, West US, UK South, UK West, Canada Central, Japan East, Japan West, India Central, India South, India West, Australia Central, Australia Southeast, Brazil South, Northcentral US, Canada East, East US3, Korea Central, Norway East, South Africa North, Sweden Central, Australia Central 2, France Central, Germany North, Jio India Central, Korea South, Poland Central, South Africa West, Switzerland West, Sweden South, Southeast Asia, UAE North, West US3, Brazil Southeast, South Central US, France South, Germany West Central, Jio India West, Malaysia South, Norway West, Southeast US, Taiwan North, New Zealand North, Malaysia West, Chile Central, Belgium Central, Austria East and Denmark East. 
 
 ## Limitations and known issues
 

articles/connectors/connectors-create-api-mq.md

@@ -1,17 +1,19 @@
 ---
-title: Connect to IBM MQ
-description: Connect to an MQ server on premises or in Azure from a workflow in Azure Logic Apps.
+title: Connect to IBM MQ from Workflows
+description: Connect to MQ servers on-premises or in Azure from workflows in Azure Logic Apps.
 services: logic-apps
 ms.suite: integration
-ms.reviewer: estfan, azla
+ms.reviewers: estfan, azla
 ms.topic: how-to
-ms.date: 01/08/2025
+ms.update-cycle: 365-days
+ms.date: 03/10/2026
 ms.custom:
   - engagement-fy23
   - sfi-image-nochange
+# Customer intent: As an integration developer who works with Azure Logic Apps, I want to connect my integration workflows to MQ servers either on-premises or in Azure.
 ---
 
-# Connect to an IBM MQ server from a workflow in Azure Logic Apps
+# Connect to IBM MQ servers from workflows in Azure Logic Apps
 
 [!INCLUDE [logic-apps-sku-consumption-standard](../../includes/logic-apps-sku-consumption-standard.md)]
 

articles/connectors/connectors-native-http-swagger.md

@@ -1,14 +1,16 @@
 ---
-title: Call REST API endpoints from workflows
-description: Call REST API endpoints from workflows in Azure Logic Apps.
+title: Call REST API Endpoints from Workflows
+description: Call the endpoint URL for a REST API from workflows in Azure Logic Apps.
 services: logic-apps
 ms.suite: integration
-ms.reviewer: estfan, azla
+ms.reviewers: estfan, azla
 ms.topic: how-to
-ms.date: 12/13/2024
+ms.update-cycle: 365-days
+ms.date: 03/10/2026
+# Customer intent: As an integration developer who works with Azure Logic Apps, I want to call a REST endpoint from my workflow.
 ---
 
-# Call REST API endpoints from workflows in Azure Logic Apps
+# Call endpoints for REST APIs from workflows in Azure Logic Apps
 
 [!INCLUDE [logic-apps-sku-consumption-standard](../../includes/logic-apps-sku-consumption-standard.md)]
 
@@ -20,7 +22,7 @@ The **HTTP + Swagger** built-in operations currently support only OpenAPI 2.0, n
 
 ## Prerequisites
 
-* An Azure account and subscription. If you don't have an Azure subscription, [sign up for a free Azure account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
+* An Azure account and subscription. [Get a free Azure account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
 
 * The URL for the Swagger file that describes the target REST API endpoint that you want to call
 

articles/energy-data-services/release-notes.md

@@ -20,9 +20,12 @@ Azure Data Manager for Energy is updated on an ongoing basis. To stay up to date
 - Plans for changes
 
 This page is updated with the details about the upcoming release approximately a week before the actual deployment.
-
 <hr width = 100%>
 
+## March 2026
+### Seismic DDMS Change Tier - Preview
+Azure Data Manager for Energy now supports changing the storage tier of seismic datasets as a preview feature. You can move datasets between **Hot**, **Cool**, and **Cold** storage tiers based on access frequency, helping you reduce storage costs for historical or infrequently accessed data while keeping active datasets performant. This feature is available on request. To enable it, raise a support request in the Azure portal. For more information, see [Tutorial: Change the storage tier of seismic datasets](tutorial-seismic-change-tier.md).
+
 ## February 2026
 ### OSDU&reg; Reservoir DMS - Generally Available
 OSDU&reg; Reservoir DMS is now generally available on Azure Data Manager for Energy.

articles/firewall/firewall-known-issues.md

@@ -73,6 +73,7 @@ Azure Firewall Standard has the following known issues:
 |Can’t deploy Firewall with Availability Zones with a newly created Public IP address|When you deploy a Firewall with Availability Zones, you can’t use a newly created Public IP address.|First create a new zone redundant Public IP address, then assign this previously created IP address during the Firewall deployment.|
 |Associating a Public IP address with Azure Firewall isn't supported in a cross-tenant scenario.|If you create a Public IP address in tenant A, you can't associate it with a firewall deployed in tenant B.|None.|
 |VMs behind Azure Firewall can't connect to DNAT rule destinations using the firewall's public IP|When VMs route traffic through Azure Firewall and attempt to connect to resources configured with DNAT rules by using the firewall's public IP address, the connection fails. The connection failure occurs because Azure Firewall doesn't support hair pinning traffic from internal VMs to the firewall's own public IP address for DNAT rule destinations.|A solution for this limitation is currently in development.|
+|Connectivity issues when routing OS‑native IPsec traffic from Azure VMs to on‑premises through Azure Firewall Standard |In some hybrid deployments, Azure virtual machines use OS‑native IPsec tunnels to connect to on‑premises networks. When this traffic is routed through Azure Firewall Standard- especially when a VPN Gateway or Global VNet Peering is involved, IPsec packets may fail to pass through the firewall, resulting in connectivity issues.|Avoid routing OS‑native IPsec traffic from Azure virtual machines through Azure Firewall Standard. A solution for this limitation is currently in development.
 
 ## Azure Firewall Premium known issues
 
@@ -91,6 +92,7 @@ Azure Firewall Premium has the following known issues:
 |Certificate Propagation|After a CA certificate is applied on the firewall, it might take between 5-10 minutes for the certificate to take effect.|A fix is being investigated.|
 |TLS 1.3 support|TLS 1.3 is partially supported. The TLS tunnel from client to the firewall is based on TLS 1.2, and from the firewall to the external Web server is based on TLS 1.3.|Updates are being investigated.|
 |TLSi intermediate CA certificate expiration|In some unique cases, the intermediate CA certificate can expire two months before the original expiration date.|Renew the intermediate CA certificate two months before the original expiration date. A fix is being investigated.|
+|Connectivity issues when routing OS‑native IPsec traffic from Azure VMs to on‑premises through Azure Firewall Premium |In some hybrid deployments, Azure virtual machines use OS‑native IPsec tunnels to connect to on‑premises networks. When this traffic is routed through Azure Firewall Standard- especially when a VPN Gateway or Global VNet Peering is involved, IPsec packets may fail to pass through the firewall, resulting in connectivity issues.|Avoid routing OS‑native IPsec traffic from Azure virtual machines through Azure Firewall Premium. A solution for this limitation is currently in development.
 
 ## Next steps
 

articles/logic-apps/deploy-single-tenant-logic-apps-private-storage-account.md

@@ -1,24 +1,25 @@
 ---
-title: Deploy Standard logic apps to private storage accounts
+title: Deploy Standard Workflows to Private Storage
 description: Deploy Standard logic app workflows to Azure storage accounts that use private endpoints and deny public access.
 services: logic-apps
 ms.suite: integration
-ms.reviewer: estfan, azla
+ms.reviewers: estfan, azla
 ms.topic: how-to
+ms.update-cycle: 365-days
+ms.date: 03/10/2026
 ms.custom: engagement-fy23, devx-track-arm-template
-ms.date: 02/24/2025
-# Customer intent: As a developer, I want to deploy Standard logic apps to Azure storage accounts that use private endpoints.
+# Customer intent: As an integration developer who works with Azure Logic Apps, I want to deploy Standard logic apps to Azure storage accounts that use private endpoints and deny public access.
 ---
 
-# Deploy single-tenant Standard logic apps to private storage accounts using private endpoints
+# Deploy Standard logic apps to Azure storage that use private endpoints
 
 [!INCLUDE [logic-apps-sku-standard](../../includes/logic-apps-sku-standard.md)]
 
 When you create a single-tenant Standard logic app resource, you're required to have a storage account for storing logic app artifacts. You can restrict access to this storage account so that only the resources inside a virtual network can connect to your logic app workflow. Azure Storage supports adding private endpoints to your storage account.
 
-This article describes the steps to follow for deploying such logic apps to protected private storage accounts.
+This guide shows how to deploy Standard logic apps to Azure storage accounts protected by private endpoints.
 
-For more information, review the following documentation:
+For more information, see:
 
 - [Secure traffic between Standard logic apps and Azure virtual networks using private endpoints](secure-single-tenant-workflow-virtual-network-private-endpoint.md)
 - [Use private endpoints for Azure Storage](../storage/common/storage-private-endpoints.md)
@@ -63,9 +64,9 @@ This deployment method requires temporary public access to your storage account.
 
    1. On the logic app resource menu, under **Settings**, select **Environment variables**.
 
-   1. On the **App settings** tab, add the **WEBSITE_CONTENTOVERVNET** app setting, if none exist, and set the value to **1**.
+   1. On the **App settings** tab, add the **WEBSITE_CONTENTOVERVNET** app setting, if none exists, and set the value to **1**.
 
-   1. If you use your own domain name server (DNS) with your virtual network, add the **WEBSITE_DNS_SERVER** app setting, if none exist, and set the value to the IP address for your DNS. If you have a secondary DNS, add another app setting named **WEBSITE_DNS_ALT_SERVER**, and set the value to the IP for your secondary DNS.
+   1. If you use your own domain name server (DNS) with your virtual network, add the **WEBSITE_DNS_SERVER** app setting, if none exists, and set the value to the IP address for your DNS. If you have a secondary DNS, add another app setting named **WEBSITE_DNS_ALT_SERVER**, and set the value to the IP for your secondary DNS.
 
 1. After you apply these app settings, you can remove public access from your storage account.
 

articles/logic-apps/logic-apps-enterprise-integration-overview.md

@@ -1,24 +1,26 @@
 ---
-title: B2B enterprise integration workflows
-description: Learn about building automated B2B workflows for enterprise integration by using Azure Logic Apps and Enterprise Integration Pack.
+title: B2B Enterprise Integration Workflows
+description: Learn about automated B2B workflows for enterprise integration in Azure Logic Apps.
 services: logic-apps
 ms.suite: integration
 author: divyaswarnkar
 ms.author: divswa
-ms.reviewer: estfan, azla
+ms.reviewers: estfan, azla
 ms.topic: overview
-ms.date: 02/19/2025
+ms.update-cycle: 365-days
+ms.date: 03/10/2026
+# Customer intent: As a B2B enterprise integration developer, I want to learn about building B2B workflows in Azure Logic Apps.
 ---
 
-# B2B enterprise integration workflows with Azure Logic Apps and Enterprise Integration Pack
+# B2B enterprise integration workflows with Azure Logic Apps
 
-For business-to-business (B2B) solutions and seamless communication between organizations, you can build automated, scalable, enterprise integration workflows by using Azure Logic Apps with the Enterprise Integration Pack (EIP).
+For business-to-business (B2B) solutions and seamless communication between organizations, you can build automated, scalable, enterprise integration workflows by using Azure Logic Apps, which includes the Enterprise Integration Pack (EIP).
 
 ## What is the Enterprise Integration Pack?
 
 If you're familiar with Microsoft BizTalk Server, the EIP follows similar concepts and makes B2B capabilities easy to use. However, one major difference is that the EIP is architecturally based on *integration accounts*. These accounts are cloud-based containers in Azure that simplify how you store, manage, and use B2B artifacts for B2B communication, including trading partners, agreements, maps, schemas, certificates, and so on.
 
-With these artifacts, you can build B2B workflows and integration solutions that include cloud services, such as Azure, Microsoft, and other software-as-service (SaaS) apps, on-premises systems, and custom apps by using Azure Logic Apps and choosing from [hundreds of connectors](/connectors/connector-reference/connector-reference-logicapps-connectors). For example, you can create and run custom code from your workflows using the built-in and Azure Functions connectors. You can also use [enterprise integration connectors](../connectors/managed.md#enterprise-connectors) that support the following industry standards:
+With these artifacts, you can build B2B workflows and integration solutions that include cloud services, such as Azure, Microsoft, and other software-as-service (SaaS) apps, on-premises systems, and custom apps by using Azure Logic Apps and choosing from [1,400+ connectors](/connectors/connector-reference/connector-reference-logicapps-connectors). For example, you can create and run custom code from your workflows using the built-in and Azure Functions connectors. You can also use [enterprise integration connectors](../connectors/managed.md#enterprise-connectors) that support the following industry standards:
 
 * Electronic Data Interchange (EDI)
 * Enterprise Application Integration (EAI)
@@ -27,13 +29,13 @@ Although organizations use different protocols and formats for B2B communication
 
 ## What do I need to get started?
 
-* An Azure account and subscription. If you don't have an Azure subscription, [sign up for a free Azure account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
+* An Azure account and subscription. [Get a free Azure account](https://azure.microsoft.com/pricing/purchase-options/azure-account?cid=msft_learn).
 
 * An [integration account](logic-apps-enterprise-integration-create-integration-account.md) to store the B2B artifacts that you define and want to use.
 
 * B2B artifacts, such as [trading partners](logic-apps-enterprise-integration-partners.md), [agreements](logic-apps-enterprise-integration-agreements.md), [maps](logic-apps-enterprise-integration-maps.md), [schemas](logic-apps-enterprise-integration-schemas.md), [certificates](logic-apps-enterprise-integration-certificates.md), and so on.
 
-* To create maps and schemas, you can use Visual Studio 2019 and the [Microsoft Azure Logic Apps Enterprise Integration Tools Extension](https://aka.ms/vsenterpriseintegrationtools). The extension is currently unavailable for Visual Studio 2022.
+* To create maps and schemas, you can use Visual Studio 2019 and the [Microsoft Azure Logic Apps Enterprise Integration Tools Extension](https://aka.ms/vsenterpriseintegrationtools). The extension is currently unavailable for Visual Studio 2022 and later.
 
    > [!NOTE]
    > Don't install this extension alongside the BizTalk Server extension. Having both extensions might 
@@ -74,7 +76,7 @@ The following diagram shows the high-level steps to start building B2B logic app
 
 To try this [sample](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.logic/logic-app-as2-send-receive), which deploys logic apps that send and receive AS2 messages through Azure, select **Deploy to Azure**. Before you run the sample, make sure that you manually update **FabrikamSales-AS2Send** logic app workflow so that the **HTTP** action's **URI** property uses the URI that's dynamically generated for the **Request** trigger in the **Contoso-AS2Receive** logic app.
 
-## Next steps
+## Related content
 
 * [Create trading partners](logic-apps-enterprise-integration-partners.md)
 * [Create agreements](logic-apps-enterprise-integration-agreements.md)