updates

Author: aahill

articles/ai-foundry/openai/how-to/spillover-traffic-management.md

@@ -5,7 +5,7 @@ author: aahill # GitHub alias
 ms.author: aahi
 ms.service: azure-ai-openai
 ms.topic: how-to
-ms.date: 05/20/2025
+ms.date: 08/27/2025
 ---
 
 # Manage traffic with spillover for provisioned deployments
@@ -16,14 +16,14 @@ Spillover manages traffic fluctuations on provisioned deployments by routing ove
 > Spillover is currently not available for the `/v1` [API endpoint](../reference-preview-latest.md).
 
 ## Prerequisites
-- Two separate deployments. The primary deployment can be any (standard, data zone) provisioned type. The spillover deployment can be a provisioned deployment of the same type as the primary deployment, or a pay-as-you-go deployment.
+- You need to have a provisioned managed deployment and a standard deployment.
 
 - The provisioned and standard deployments must be in the same Azure OpenAI resource to be eligible for spillover.
 
 - The data processing level of your standard deployment must match your provisioned deployment (for example, a global provisioned deployment must be used with a global standard spillover deployment).
 
 ## When to enable spillover on provisioned deployments
-To maximize the utilization of your provisioned deployment, you can enable spillover for all global and data zone provisioned deployments. With spillover, bursts or fluctuations in traffic can be automatically managed by the service. This capability reduces the risk of experiencing disruptions when a provisioned deployment is fully utilized. Alternatively, spillover is configurable per-request to provide flexibility across different scenarios and workloads.  
+To maximize the utilization of your provisioned deployment, you can enable spillover for all global and data zone provisioned deployments. With spillover, bursts or fluctuations in traffic can be automatically managed by the service. This capability reduces the risk of experiencing disruptions when a provisioned deployment is fully utilized. Alternatively, spillover is configurable per-request to provide flexibility across different scenarios and workloads. Spillover can be used for the [Azure AI Foundry Agent Service](../../agents/overview.md) and [responses API](./responses.md).  
 
 ## When does spillover come into effect?
 When spillover is enabled for a deployment or configured for a given inference request, spillover is initiated when a non-200 response code is received for a given inference request. When a request results in a non-200 response code, the Azure OpenAI automatically sends the request from your provisioned deployment to your standard deployment to be processed. Even if a subset of requests is routed to the standard deployment, the service prioritizes sending requests to the provisioned deployment before sending any overage requests to the standard deployment, which may incur additional latency.