[APIM] Workspaces conceptual content

Author: gitName

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

@@ -6,7 +6,7 @@ author: dlepow
 
 ms.service: azure-api-management
 ms.topic: overview
-ms.date: 10/23/2024
+ms.date: 01/08/2025
 ms.author: danlep
 ms.custom: mvc
 ---
@@ -33,6 +33,7 @@ APIs enable digital experiences, simplify application integration, underpin new
 
 Azure API Management helps customers meet these challenges:
 
+* Provide an API platform for different stakeholders to produce, manage, and consume APIs 
 * Abstract backend architecture diversity and complexity from API consumers
 * Securely expose services hosted on and outside of Azure as APIs
 * Protect, accelerate, and observe APIs
@@ -100,6 +101,12 @@ Using the developer portal, developers can:
   * Download API definitions
   * Manage API keys
 
+## API platform deployment models
+
+Azure API Management supports three deployment models: centralized, siloed, and federated. Each model is suitable for different organizational structures and requirements.
+
+[!INCLUDE [api-management-platform-deployment-models](../../includes/api-management-platform-deployment-models.md)]
+
 ## API Management tiers
 
 API Management is offered in a variety of pricing tiers to meet the needs of different customers. Each tier offers a distinct combination of features, performance, capacity limits, scalability, SLA, and pricing for different scenarios. The tiers are grouped as follows:

includes/api-management-platform-deployment-models.md

@@ -0,0 +1,13 @@
+---
+author: dlepow
+ms.service: azure-api-management
+ms.topic: include
+ms.date: 08/08/2023
+ms.author: danlep
+---
+
+|Model|Description  |
+|---------|---------|
+|**Centralized**<br/><br/>:::image type="content" source="media/api-management-platform-deployment-models/centralized.png" alt-text="Diagram of the centralized model of Azure API Management." border="false" lightbox="media/api-management-platform-deployment-models/centralized.png":::      |**Pros**<br/>• Centralized API governance and observability<br/>• Unified developer portal for effective API discovery and onboarding<br/>• Cost-efficiency of the infrastructure<br/><br/>**Cons**<br/>• No segregation of administrative permissions between teams<br/>• API gateway is a single point of failure<br/>• Inability to attribute runtime issues to specific teams<br/>• Burden on platform team to facilitate collaboration may reduce API growth     |
+|**Siloed**<br/><br/>:::image type="content" source="media/api-management-platform-deployment-models/siloed.png"  alt-text="Diagram of the siloed model of Azure API Management." border="false" lightbox="media/api-management-platform-deployment-models/siloed.png":::       |**Pros**<br/>• Segregation of administrative permissions between teams increases productivity and security<br/>• Segregation of API runtime between teams increases API reliability, resiliency, and security<br/>• Runtime issues are contained and attributable to specific teams<br/><br/>**Cons**<br/>• Lack of centralized API governance and observability<br/>• Lack of unified developer portal<br/>• Increased cost and harder platform management​    | 
+|**Federated**<br/><br/>:::image type="content" source="media/api-management-platform-deployment-models/federated.png" alt-text="Diagram of the federated model of Azure API Management." border="false" lightbox="media/api-management-platform-deployment-models/federated.png":::       |**Pros**<br/>• Centralized API governance and observability<br/>• Unified developer portal for effective API discovery and onboarding<br/>• Segregation of administrative permissions between teams increases productivity and security<br/>• Segregation of API runtime between teams increases API reliability, resiliency, and security<br/>• Runtime issues are contained and attributable to specific teams<br/><br/>**Cons**<br/>• Platform cost and management difficulty greater than in the centralized model but lower than in the siloed model |