Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into us429364-seo-top25-vnet

Author: asudbring

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

@@ -11,7 +11,10 @@ ms.custom: fasttrack-edit
 
 # Orchestration versioning in Durable Functions (Azure Functions)
 
-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).
+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).
+
+> [!NOTE]
+> For Durable Task Scheduler users, if you're using the Durable Task SDKs instead of Durable functions, you should refer to the [Durable Task SDKs versioning article](./durable-task-scheduler/durable-task-scheduler-versioning.md). 
 
 ## Terminology
 

articles/event-grid/event-schema-service-bus.md

@@ -21,7 +21,9 @@ This article provides the properties and schema for Service Bus events. For an
 | [Azure Service Bus to Event Grid integration](../service-bus-messaging/service-bus-to-event-grid-integration-concept.md) | Overview of integrating Service Bus with Event Grid. |
 
 > [!NOTE]
-> When a failover occurs for a Service Bus namespace that's Geo-DR enabled, the secondary namespace doesn't emit events to Event Grid. You need to manually add the Event Grid subscription for the secondary namespace. 
+> When a failover occurs for a Service Bus namespace that's Geo-DR enabled, the secondary namespace doesn't emit events to Event Grid. You need to manually add the Event Grid subscription for the secondary namespace.
+>
+> Check the [Service Bus Geo-Replication documentation](/azure/service-bus-messaging/service-bus-geo-replication) to understand what happens for a Service Bus namespace that's Geo-Replication enabled.
 
 ## Next steps
 

articles/sre-agent/security-context.md

@@ -4,7 +4,7 @@ description: Learn how SRE Agent uses different security contexts to handle agen
 author: craigshoemaker
 ms.author: cshoe
 ms.topic: tutorial
-ms.date: 07/16/2025
+ms.date: 07/17/2025
 ms.service: azure
 ---
 
@@ -71,21 +71,21 @@ The following table details how the agent behaves when attempting to conduct a r
 
 | Agent has permission? | Execution mode | Agent behavior |
 |---|---|---|
-| Yes | Review | Reads required data and doesn't prompt for approval |
-| No | Review | Prompts for approval to take action |
-| Yes | Auto | Executes action without requiring approval |
-| No | Auto | Prompts for approval, and executes action based on approval status |
+| Yes | Review | Uses its permissions to perform the action. |
+| No | Review | Prompts for temporary access to perform the action [on behalf of the user](/entra/identity-platform/v2-oauth2-on-behalf-of-flow). |
+| Yes | Auto | Uses its permissions to perform the action |
+| No | Auto | Prompts for temporary access to perform the action [on behalf of the user](/entra/identity-platform/v2-oauth2-on-behalf-of-flow) |
 
 ### Write actions
 
 The following table details how the agent behaves when attempting to conduct a write operation.
 
 | Agent has permission? | Execution mode | Agent behavior |
 |---|---|---|
-| Yes | Review | Prompts for approval to take action |
-| No | Review | Prompts for approval to take action, if granted the agent temporarily inherits the required permissions from the user |
-| Yes | Auto | Executes action without requiring approval |
-| No | Auto | Prompts for approval, and executes action based on approval status |
+| Yes | Review | Prompts for approval to take action, then the agent uses its permissions to perform the action upon approval |
+| No | Review | First prompts for approval to take action, then prompts for temporary access to perform the action [on behalf of the user](/entra/identity-platform/v2-oauth2-on-behalf-of-flow) |
+| Yes | Auto | Uses its permissions to perform the action |
+| No | Auto | Prompts for temporary access to perform the action [on behalf of the user](/entra/identity-platform/v2-oauth2-on-behalf-of-flow) |
 
 ## Related content