Merge pull request #303583 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)

Author: Taojunshen

articles/azure-functions/durable/durable-functions-orchestration-versioning.md

@@ -9,7 +9,7 @@ ms.custom: fasttrack-edit
 #Customer intent: As a Durable Functions developer, I want to deploy breaking changes to my orchestrations without interrupting in-flight instances, so that I can maintain zero-downtime deployments.
 ---
 
-# Orchestration versioning in Durable Functions (Azure Functions)
+# Orchestration versioning in Durable Functions (Azure Functions) - public preview
 
 Orchestration versioning addresses [the core challenge](durable-functions-versioning.md) of deploying changes to orchestrator functions while maintaining the deterministic execution model that Durable Functions requires. Without this feature, breaking changes to orchestrator logic or activity function signatures would cause in-flight orchestration instances to fail during replay because they would break the [determinism requirement](durable-functions-code-constraints.md) that ensures reliable orchestration execution. This built-in feature provides automatic version isolation with minimal configuration. It's backend agnostic, so it can be used by apps leveraging any of the Durable Function's [storage providers](durable-functions-storage-providers.md), including the [Durable Task Scheduler](./durable-task-scheduler/durable-task-scheduler.md).
 

articles/firewall-manager/policy-overview.md

@@ -25,7 +25,7 @@ Policies can be associated with one or more firewalls deployed in either a Virtu
 
 ## Classic rules and policies
 
-Azure Firewall supports both Classic rules and policies, but policies is the recommended configuration. The following table compares policies and classic rules:
+Azure Firewall supports both Classic rules and policies, but policies are the recommended configuration. The following table compares policies and classic rules:
 
 
 | Subject | Policy  | Classic rules |
@@ -70,7 +70,7 @@ With inheritance, any changes to the parent policy are automatically applied dow
 ## Built-in high availability
 
 High availability is built in, so there's nothing you need to configure.
-You can create an Azure Firewall Policy object in any region and link it globally to multiple Azure Firewall instances under the same Azure AD tenant. If the region where you create the Policy goes down and has a paired region, the ARM(Azure Resource Manager) object metadata automatically fails over to the secondary region. During the failover, or if the single-region with no pair remains in a failed state, you can't modify the Azure Firewall Policy object. However, the Azure Firewall instances linked to the Firewall Policy continue to operate. For more information, see [Cross-region replication in Azure: Business continuity and disaster recovery](../reliability/cross-region-replication-azure.md#azure-paired-regions).
+You can create an Azure Firewall Policy object in any region and link it globally to multiple Azure Firewall instances under the same Entra ID tenant. If the region where you create the Policy goes down and has a paired region, the ARM(Azure Resource Manager) object metadata automatically fails over to the secondary region. During the failover, or if the single-region with no pair remains in a failed state, you can't modify the Azure Firewall Policy object. However, the Azure Firewall instances linked to the Firewall Policy continue to operate. For more information, see [Cross-region replication in Azure: Business continuity and disaster recovery](../reliability/cross-region-replication-azure.md#azure-paired-regions).
 
 ## Pricing
 

articles/network-watcher/traffic-analytics-faq.yml

@@ -70,6 +70,11 @@ sections:
         answer: |
           Yes.
 
+      - question: |
+          When viewing my Traffic Analytics workbooks, my data doesn't load due to 'low memory error'. How can I fix this to view my data in workbook? 
+        answer: |
+          Traffic Analytics workbooks are powered by Log Analytics queries. If the query exceeds limits for log analytics, the workbook could present low memory errors. To improve performance and reduce low memory errors, users can use Dedicated Log Analytics Clusters.
+
       - question: |
           Will I lose the data stored in Log Analytics workspace if I delete the storage account used for flow logging?
         answer: |

articles/playwright-testing/playwright-testing-reporting-with-sharding.md

@@ -79,7 +79,7 @@ Here's an example of how you can set it in your pipeline via GitHub Actions.
       runs-on: ubuntu-latest
       steps:
       - uses: actions/checkout@v3
-      - uses: actions/setup-node@v3
+      - uses: actions/setup-node@v4
         with:
           node-version: 18
         # This step is to sign-in to Azure to run tests from GitHub Action workflow.