Skip to content

Commit de3ab84

Browse files
authored
Merge pull request #28541 from microsoftgraph/users/lianshen/update-rbac
Update Places API with application permission details
2 parents a67363b + ea57ae1 commit de3ab84

5 files changed

Lines changed: 12 additions & 6 deletions

File tree

api-reference/beta/includes/rbac-for-apis/rbac-places-apis-update-known-issue.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,5 +5,6 @@ ms.topic: include
55

66
> [!IMPORTANT]
77
> In delegated scenarios with work or school accounts, the signed-in user must be assigned a supported [Microsoft Entra role](/entra/identity/role-based-access-control/permissions-reference?toc=%2Fgraph%2Ftoc.json) or a custom role with a supported role permission. *Exchange Administrator* is the least privileged role supported for this operation.
8+
> When using *application permissions*, you must configure the required `TenantPlacesManagement` role (to manage Places) and the `MailRecipient` role (to manage users and mailboxes). For more information on how to configure these roles, see [Role Based Access Control for Applications in Exchange Online](/exchange/permissions-exo/application-rbac).
89
9-
> **Known issue:** Update requests may still succeed without the role assignment but result in unexpected behaviors.
10+
> **Known issue:** Update requests may still succeed even when the required delegated Microsoft Entra role or application RBAC role assignments are missing, but can result in unexpected behaviors.

api-reference/beta/includes/rbac-for-apis/rbac-places-apis-write.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,4 +4,5 @@ ms.topic: include
44
---
55

66
> [!IMPORTANT]
7-
> In delegated scenarios with work or school accounts, the signed-in user must be assigned a supported [Microsoft Entra role](/entra/identity/role-based-access-control/permissions-reference?toc=%2Fgraph%2Ftoc.json) or a custom role with a supported role permission. *Exchange Administrator* is the least privileged role supported for this operation.
7+
> In delegated scenarios with work or school accounts, the signed-in user must be assigned a supported [Microsoft Entra role](/entra/identity/role-based-access-control/permissions-reference?toc=%2Fgraph%2Ftoc.json) or a custom role with a supported role permission. *Exchange Administrator* is the least privileged role supported for this operation.
8+
> When using *application permissions*, you must configure the required `TenantPlacesManagement` role (to manage Places) and the `MailRecipient` role (to manage users and mailboxes). For more information on how to configure these roles, see [Role Based Access Control for Applications in Exchange Online](/exchange/permissions-exo/application-rbac).

api-reference/v1.0/includes/rbac-for-apis/rbac-places-apis-update-known-issue.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,5 +5,6 @@ ms.topic: include
55

66
> [!IMPORTANT]
77
> In delegated scenarios with work or school accounts, the signed-in user must be assigned a supported [Microsoft Entra role](/entra/identity/role-based-access-control/permissions-reference?toc=%2Fgraph%2Ftoc.json) or a custom role with a supported role permission. *Exchange Administrator* is the least privileged role supported for this operation.
8+
> When using *application permissions*, you must configure the required `TenantPlacesManagement` role (to manage Places) and the `MailRecipient` role (to manage users and mailboxes). For more information on how to configure these roles, see [Role Based Access Control for Applications in Exchange Online](/exchange/permissions-exo/application-rbac).
89
9-
> **Known issue:** Update requests may still succeed without the role assignment but result in unexpected behaviors.
10+
> **Known issue:** Update requests may still succeed without either the delegated Microsoft Entra role assignment or the application RBAC role assignments but result in unexpected behaviors.

api-reference/v1.0/includes/rbac-for-apis/rbac-places-apis-write.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,4 +4,5 @@ ms.topic: include
44
---
55

66
> [!IMPORTANT]
7-
> In delegated scenarios with work or school accounts, the signed-in user must be assigned a supported [Microsoft Entra role](/entra/identity/role-based-access-control/permissions-reference?toc=%2Fgraph%2Ftoc.json) or a custom role with a supported role permission. *Exchange Administrator* is the least privileged role supported for this operation.
7+
> In delegated scenarios with work or school accounts, the signed-in user must be assigned a supported [Microsoft Entra role](/entra/identity/role-based-access-control/permissions-reference?toc=%2Fgraph%2Ftoc.json) or a custom role with a supported role permission. *Exchange Administrator* is the least privileged role supported for this operation.
8+
> When using *application permissions*, you must configure the required `TenantPlacesManagement` role (to manage Places) and the `MailRecipient` role (to manage users and mailboxes). For more information on how to configure these roles, see [Role Based Access Control for Applications in Exchange Online](/exchange/permissions-exo/application-rbac).

concepts/whats-new-overview.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,8 @@ Using the **signInAudience** property to limit where an [application](/graph/api
2626

2727
### Calendars | Places
2828

29-
Added a known issue of RBAC in [Places update API](/graph/api/place-update): update requests may still succeed without *Exchange Administrator* role but result in unexpected behaviors.
29+
- Added a known issue of RBAC in [Places update API](/graph/api/place-update): update requests may still succeed without *Exchange Administrator* role but result in unexpected behaviors.
30+
- When using *application permissions* with the [Create place](/graph/api/place-post), [Upsert places](/graph/api/place-patch-places), [Update place](/graph/api/place-update), and [Delete place](/graph/api/place-delete) APIs, you must configure the required `TenantPlacesManagement` role (to manage Places) and the `MailRecipient` role (to manage users and mailboxes). For more information on how to configure these roles, see [Role Based Access Control for Applications in Exchange Online](/exchange/permissions-exo/application-rbac).
3031

3132
### Device and app management | Cloud PC
3233

@@ -104,7 +105,8 @@ The new Tenant Configuration Management APIs in Microsoft Graph allow administra
104105

105106
### Calendars | Places
106107

107-
Added a known issue of RBAC in [Places update API](/graph/api/place-update?view=graph-rest-beta&preserve-view=true): update requests may still succeed without *Exchange Administrator* role but result in unexpected behaviors.
108+
- Added a known issue of RBAC in [Places update API](/graph/api/place-update?view=graph-rest-beta&preserve-view=true): update requests may still succeed without *Exchange Administrator* role but result in unexpected behaviors.
109+
- When using *application permissions* with the [Create place](/graph/api/place-post?view=graph-rest-beta&preserve-view=true), [Upsert places](/graph/api/place-patch-places?view=graph-rest-beta&preserve-view=true), [Update place](/graph/api/place-update?view=graph-rest-beta&preserve-view=true), and [Delete place](/graph/api/place-delete?view=graph-rest-beta&preserve-view=true) APIs, you must configure the required `TenantPlacesManagement` role (to manage Places) and the `MailRecipient` role (to manage users and mailboxes). For more information on how to configure these roles, see [Role Based Access Control for Applications in Exchange Online](/exchange/permissions-exo/application-rbac).
108110

109111
### Device and app management | Cloud PC
110112

0 commit comments

Comments
 (0)