Skip to content

Latest commit

 

History

History
130 lines (92 loc) · 4.12 KB

File metadata and controls

130 lines (92 loc) · 4.12 KB
title Create rejectedSender
description Add a new user or group to the rejectedSender list.
author yuhko-msft
ms.reviewer mbhargav, khotzteam, aadgroupssg
ms.localizationpriority medium
ms.subservice entra-groups
doc_type apiPageType
ms.date 04/05/2024

Create rejectedSender

Namespace: microsoft.graph

[!INCLUDE beta-disclaimer]

Add a new user or group to the rejectedSender list.

Specify the user or group in @odata.id in the request body. Users in the rejected senders list can't post to conversations of the group (identified in the POST request URL). Make sure you don't specify the same user or group in the rejected senders and accepted senders lists, otherwise you'll get an error.

[!INCLUDE national-cloud-support]

Permissions

Choose the permission or permissions marked as least privileged for this API. Use a higher privileged permission or permissions only if your app requires it. For details about delegated and application permissions, see Permission types. To learn more about these permissions, see the permissions reference.

[!INCLUDE permissions-table]

HTTP request

POST /groups/{id}/rejectedSenders/$ref

Request headers

Header Value
Authorization Bearer {token}. Required. Learn more about authentication and authorization.

Request body

In the request body, supply the id of a user or group object.

Response

This method returns 204 No Content response code and no response body.

Example

Request

The following example shows a request.

POST https://graph.microsoft.com/beta/groups/{id}/rejectedSenders/$ref
Content-type: application/json

{
  "@odata.id":"https://graph.microsoft.com/beta/users/alexd@contoso.com"
}

[!INCLUDE sample-code] [!INCLUDE sdk-documentation]

[!INCLUDE sample-code] [!INCLUDE sdk-documentation]

[!INCLUDE sample-code] [!INCLUDE sdk-documentation]

[!INCLUDE sample-code] [!INCLUDE sdk-documentation]

[!INCLUDE sample-code] [!INCLUDE sdk-documentation]

[!INCLUDE sample-code] [!INCLUDE sdk-documentation]

[!INCLUDE sample-code] [!INCLUDE sdk-documentation]


Response

The following example shows the response.

HTTP/1.1 204 No Content