Create rejectedSender

Namespace: microsoft.graph

Important

APIs under the /beta version in Microsoft Graph are subject to change. Use of these APIs in production applications is not supported. To determine whether an API is available in v1.0, use the Version selector.

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.

This API is available in the following national cloud deployments.

Global service US Government L4 US Government L5 (DOD) China operated by 21Vianet

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.

Permission type Least privileged permissions Higher privileged permissions
Delegated (work or school account) Group.ReadWrite.All Not available.
Delegated (personal Microsoft account) Not supported. Not supported.
Application Not supported. Not supported.

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"
}

Response

The following example shows the response.

HTTP/1.1 204 No Content