review comments

Author: dlepow

articles/api-management/breaking-changes/workspaces-breaking-changes-april-2024.md

@@ -11,7 +11,7 @@ ms.author: danlep
 
 # Workspaces - breaking changes (April 2024)
 
-On 30 April 2024 as part of our development of [workspaces](../workspaces-overview.md) (preview) in Azure API Management, we're introducing several breaking changes. 
+On 30 April 2024, as part of our development of [workspaces](../workspaces-overview.md) (preview) in Azure API Management, we're introducing several breaking changes. 
 
 These changes will have no effect on the availability of your API Management service. However, you may have to take action to continue using full workspaces functionality beyond 30 April 2024.
 
@@ -25,7 +25,7 @@ Review the following breaking changes to determine if you need to take action:
 
 ### Change to supported service tiers
 
-The following service tiers will no longer support workspaces: **Standard** and **Developer**. Workspaces will be available in the **Premium** tier.
+The following service tiers will no longer support workspaces: **Standard** and **Developer**. Workspaces will be available in the **Premium** tier. For availability in the v2 tiers, see [Azure API Management v2 tiers](../v2-service-tiers-overview.md).
 
 ### Changes to support for assigning service-level entities in workspaces
 
@@ -36,14 +36,6 @@ The following assignments of workspace entities to service-level entities will n
 * Assign workspace products to service-level tags
 
 
-### Changes to support for referencing service-level resources from workspace-level policies
-
-The following capabilities of workspace-level policies will no longer be supported:
-
-* Reference service-level backends
-* List service-level certificates with `context.Deployment.Certificates`. When used in a service-level policy, this method will return service-level certificates only.
-* Reference named values, policy fragments, loggers, cache, schemas, and related policy resources from the service level
-
 ### Changes to supported context objects
 
 The following `context` objects will no longer be supported in workspace policies or in the all-APIs policy on the service level:

articles/api-management/v2-service-tiers-overview.md

@@ -6,7 +6,7 @@ author: dlepow
 
 ms.service: api-management
 ms.topic: conceptual
-ms.date: 10/02/2023
+ms.date: 01/31/2024
 ms.author: danlep
 ms.custom: references_regions
 ---
@@ -85,7 +85,7 @@ Currently, the following API Management capabilities are unavailable in the v2 t
 * Built-in analytics
 * Inbound connection using a private endpoint
 * Upgrade to v2 tiers from v1 tiers 
-* Workspaces
+* Workspaces (*Standard v2*)
 
 **Developer portal**
 * Delegation of user registration and product subscription