Skip to content

Commit 18a650d

Browse files
committed
Learn Editor: Update workspaces-overview.md
1 parent e333a2f commit 18a650d

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

articles/api-management/workspaces-overview.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,8 +9,9 @@ ms.service: api-management
99
ms.topic: conceptual
1010
ms.date: 03/10/2023
1111
ms.author: danlep
12-
ms.custom:
12+
ms.custom:
1313
---
14+
1415
# Workspaces in Azure API Management
1516

1617
In API Management, *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).
@@ -137,6 +138,8 @@ Therefore, the following sample scenarios aren't currently supported in workspac
137138
* Using the authorizations feature
138139

139140
* Specifying API authorization server information (for example, for the developer portal)
141+
142+
All resources in an API Management service need to have unique names, even if they are located in different workspaces.
140143

141144
## Next steps
142145

0 commit comments

Comments
 (0)