Skip to content

Commit 795e223

Browse files
authored
Merge pull request #159340 from dlepow/patch-53
Update api-management-role-based-access-control.md
2 parents 839b0ef + 50f6142 commit 795e223

File tree

1 file changed

+1
-5
lines changed

1 file changed

+1
-5
lines changed

articles/api-management/api-management-role-based-access-control.md

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ ms.service: api-management
1212
ms.workload: mobile
1313
ms.tgt_pltfrm: na
1414
ms.topic: article
15-
ms.date: 06/20/2018
15+
ms.date: 05/18/2021
1616
ms.author: apimpm
1717
ms.custom: devx-track-azurepowershell
1818

@@ -34,15 +34,11 @@ The following table provides brief descriptions of the built-in roles. You can a
3434
| API Management Service Contributor ||||| Super user. Has full CRUD access to API Management services and entities (for example, APIs and policies). Has access to the legacy publisher portal. |
3535
| API Management Service Reader || | || Has read-only access to API Management services and entities. |
3636
| API Management Service Operator || || | Can manage API Management services, but not entities.|
37-
| API Management Service Editor<sup>*</sup> ||| | | Can manage API Management entities, but not services.|
38-
| API Management Content Manager<sup>*</sup> || | || Can manage the developer portal. Read-only access to services and entities.|
3937

4038
<sup>[1] Read access to API Management services and entities (for example, APIs and policies).</sup>
4139

4240
<sup>[2] Write access to API Management services and entities except the following operations: instance creation, deletion, and scaling; VPN configuration; and custom domain setup.</sup>
4341

44-
<sup>\* The Service Editor role will be available after we migrate all the admin UI from the existing publisher portal to the Azure portal. The Content Manager role will be available after the publisher portal is refactored to only contain functionality related to managing the developer portal.</sup>
45-
4642
## Custom roles
4743

4844
If none of the built-in roles meet your specific needs, custom roles can be created to provide more granular access management for API Management entities. For example, you can create a custom role that has read-only access to an API Management service, but only has write access to one specific API. To learn more about custom roles, see [Custom roles in Azure RBAC](../role-based-access-control/custom-roles.md).

0 commit comments

Comments
 (0)