added separate include

Author: dlepow

articles/api-management/api-management-capacity.md

@@ -31,7 +31,7 @@ To follow the steps in this article, you must have:
 
 + An API Management instance. For more information, see [Create an Azure API Management instance](get-started-create-service-instance.md).
 
-[!INCLUDE [premium-dev-standard-basic.md](../../includes/api-management-availability-premium-dev-standard-basic.md)]
+[!INCLUDE [availability-capacity.md](../../includes/api-management-availability-capacity.md)]
 
 ## What is capacity
 
@@ -50,9 +50,6 @@ Although the **capacity metric** is designed to surface problems with your API M
 
 ## Capacity metric behavior
 
-> [!IMPORTANT]
-> The **Max** aggregation of the capacity metric is only supported in the Premium tier of API Management.
-
 Because of its construction, in real life **capacity** can be impacted by many variables, for example:
 
 + connection patterns (new connection on a request versus reusing the existing connection)

includes/api-management-availability-capacity.md

@@ -0,0 +1,14 @@
+---
+author: dlepow
+ms.service: api-management
+ms.topic: include
+ms.date: 11/16/2022
+ms.author: danlep
+---
+
+## Availability
+
+> [!IMPORTANT]
+> This feature is available in the **Premium**, **Standard**, **Basic**, and **Developer** tiers of API Management.
+>
+> The **Max** aggregation of the capacity metric is only supported in the **Premium** tier of API Management.