review

Author: gitName

articles/api-management/api-management-key-concepts.md

@@ -181,7 +181,7 @@ When developers subscribe to a product, they're granted the primary and secondar
 
 ### Workspaces
 
-Workspaces allow decentralized API development teams to manage and productize their own APIs, while a central API platform team maintains the API Management infrastructure. Each workspace contains APIs, products, subscriptions, and related entities that are accessible only to the workspace collaborators. Access is controlled through Azure role-based access control (RBAC). Each workspace is associated with a workspace gateway that routes API traffic to its backend services.
+Workspaces allow decentralized API development teams to manage and productize their own APIs, while a central API platform team maintains the API Management infrastructure. Each workspace contains APIs, products, subscriptions, and related entities that are accessible only to the workspace collaborators. Access is controlled through Azure role-based access control (RBAC). Each workspace is associated with one or more workspace gateways that route API traffic to its backend services.
 
 **More information**:
 

articles/api-management/breaking-changes/workspaces-breaking-changes-march-2025.md

@@ -71,8 +71,8 @@ The following are abbreviated steps to add a workspace gateway to a workspace. F
 1. In the left menu, under **APIs**, select **Workspaces**.
 1. Select a workspace.
 1. In the left menu, under **Deployment + infrastructure**, select **Gateways** > **+ Add**.
-1. Complete the wizard to create a gateway. Currently, provisioning of the gateway can take from several minutes to up to 3 hours or longer.
-1. After your gateway is provisioned, go to the gateway's **Overview** page. Note the value of **Runtime hostname**. Use this value to update your client apps that call your workspace's APIs.
+1. Complete the wizard to create a new gateway or associate an existing gateway. Currently, provisioning a new gateway can take from several minutes to up to 3 hours or longer.
+1. After adding a gateway, go to the gateway's **Overview** page. Note the value of **Runtime hostname**. Use this value to update your client apps that call your workspace's APIs.
 1. Repeat the preceding steps for your remaining workspaces.
 
 ### Update client apps to use the new gateway hostname

articles/api-management/workspaces-overview.md

@@ -60,7 +60,7 @@ While workspaces are managed independently from the API Management service and o
 
 ## Workspace gateway
 
-Each workspace is associated with one or more workspace gateways to enable runtime of APIs managed within the workspace. A workspace gateway is a standalone Azure resource with the same core functionality as the gateway built into your API Management service. Workspace gateways are managed independently from the API Management service and from each other.  
+Each workspace is associated with one or more workspace gateways to enable runtime of APIs managed within the workspace. A workspace gateway is a standalone Azure resource (*workspace gateway premium*) with the same core functionality as the gateway built into your API Management service. Workspace gateways are managed independently from the API Management service and from each other.
 
 * For information on the cost of workspace gateways, see [API Management pricing](https://aka.ms/apimpricing).
 * For a detailed comparison of API Management gateways, see [API Management gateways overview](api-management-gateways-overview.md).
@@ -76,18 +76,21 @@ A workspace gateway can be either *dedicated* to a single workspace or *shared*
 
 * **Shared** - Shares gateway settings including scale, hostname, networking, and TLS configuration, and computing resources such as CPU and memory by multiple workspaces.
 
-<!--- Can a workspace be associated with both a dedicated g/w and a shared g/w?-->
-
 Consider reliability, security, and cost when choosing a deployment model for workspaces.
 
 * **Use dedicated gateways for mission-critical workloads** - To maximize API reliability and security, assign each mission-critical workspace to its own dedicated gateway, avoiding shared use with other workspaces.
 * **Balance reliability, security, and cost** - Associate multiple workspaces with a gateway to balance reliability, security, and cost for non-critical workloads. Distributing workspaces across at least two gateways helps prevent issues, such as resource exhaustion or configuration errors, from impacting all APIs within the organization.
 * **Use distinct gateways for different use cases** - Group workspaces on a gateway based on a use case or network requirements. For instance, separate internal and external APIs by assigning them to different gateways.
 **Prepare to quarantine troubled workspaces** - Use a proxy, such as Azure Application Gateway or Azure Front Door, in front of shared workspace gateways to simplify moving a workspace that's causing resource exhaustion to a different gateway, preventing impact on other workspaces sharing the gateway.
 
+> [!NOTE]
+> * A workspace gateway needs to be in the same region as the API Management instance's primary Azure region and in the same subscription
+> * All workspaces that share a workspace gateway must be in the same API Management instance
+> * A shared gateway can be associated with up to 30 workspaces (contact support to increase this limit)
+
 ### Gateway hostname
 
-Each workspace gateway provides a unique hostname for APIs managed in an associated workspace. Default hostnames follow the pattern `<gateway-name>-<hash>.gateway.<region>.azure-api.net`. Currently, custom hostnames aren't supported for workspace gateways.
+Each workspace gateway provides a unique hostname for APIs managed in an associated workspace. Default hostnames follow the pattern `<gateway-name>-<hash>.gateway.<region>.azure-api.net`. Currently, custom hostnames aren't supported for workspace gateways. Use the gateway hostname to route API requests to your workspace's APIs.
 
 
 ### Network isolation
@@ -109,9 +112,6 @@ For a current list of regions where workspace gateways are available, see [Avail
 ### Gateway constraints
 The following constraints currently apply to workspace gateways:
 
-* A workspace gateway needs to be in the same region as the API Management instance's primary Azure region and in the same subscription
-* All workspaces that share a workspace gateway must be in the same API Management instance
-* A shared gateway can be associated with up to 30 workspaces (contact support to increase this limit)
 * A workspace can't be associated with a self-hosted gateway
 * Workspace gateways don't support inbound private endpoints
 * APIs in workspace gateways can't be assigned custom hostnames
@@ -157,7 +157,7 @@ Workspaces are designed to be self-contained to maximize segregation of administ
 
 ## Migrate from preview workspaces
 
-If you created preview workspaces in Azure API Management and want to continue using them, migrate your workspaces to the generally available version by associating a workspace gateway with each workspace.
+If you created preview workspaces in Azure API Management and want to continue using them, migrate your workspaces to the generally available version by associating a dedicated or shared workspace gateway with each workspace.
 
 For details and to learn about other changes that could affect your preview workspaces, see [Workspaces breaking changes (March 2025)](breaking-changes/workspaces-breaking-changes-march-2025.md).
 

includes/api-management-service-limits.md

@@ -49,6 +49,8 @@ To request a limit increase, create a support request from the Azure portal. For
 | Maximum number of access policies per connection | 100 | 100 | 100 | 100 | 100 |
 | Maximum number of authorization requests per minute per connection | 250 | 250 | 250 | 250 | 250 |
 | Maximum number of [workspaces](../articles/api-management/workspaces-overview.md) per service instance | N/A | N/A | N/A | N/A | 100 |
+| Maximum number of APIs per [workspace](../articles/api-management/workspaces-overview.md#workspace-gateway) per service instance | N/A | N/A | N/A | N/A | 50 |
+| Maximum number of workspaces per [shared workspace gateway premium](../articles/api-management/workspaces-overview.md#workspace-gateway) per service instance | N/A | N/A | N/A | N/A | 30 |
 
 <sup>1</sup> Connections are pooled and reused unless explicitly closed by the backend.<br/>
 <sup>2</sup> Includes an up to 2048-bytes long query string.<br/>