Update inferenceclassificationoverride

Change the classifyAs field of an override as specified.

You cannot use PATCH to change any other fields in an inferenceClassificationOverride instance.

If an override exists for a sender and the sender changes his/her display name, you can use POST to force an update to the name field in the existing override.

If an override exists for a sender and the sender changes his/her SMTP address, deleting the existing override and creating a new one with the new SMTP address is the only way to "update" the override for this sender.


One of the following permissions is required to call this API. To learn more, including how to choose permissions, see Permissions.

Permission type Permissions (from least to most privileged)
Delegated (work or school account) Mail.ReadWrite
Delegated (personal Microsoft account) Mail.ReadWrite
Application Mail.ReadWrite

HTTP request

PATCH /me/inferenceClassification/overrides/{id}
PATCH /users/{id}/inferenceClassification/overrides/{id}

Request headers

Name Type Description
Authorization string Bearer {token}. Required.
Content-Type string Nature of the data in the body of an entity. Required.

Request body

In the request body, supply the new value for classifyAs. For best performance you shouldn't include existing values that are not changing.

Property Type Description
classifyAs string Specifies how incoming messages from a specific sender should always be classified as. Possible values are: focused, other.


If successful, this method returns a 200 OK response code and updated inferenceClassificationOverride object in the response body.



The following example changes the override for the SMTP address randiw@adatum.onmicrosoft.com from other to focused.

PATCH https://graph.microsoft.com/v1.0/me/inferenceClassification/overrides/{id}
Content-type: application/json

  "classifyAs": "focused"

Here is an example of the response. Note: The response object shown here may be truncated for brevity. All of the properties will be returned from an actual call.

HTTP/1.1 200 OK
Content-type: application/json

  "classifyAs": "focused",
  "senderEmailAddress": {
    "name": "Randi Welch",
    "address": "randiw@adatum.onmicrosoft.com"
  "id": "98f5bdef-576a-404d-a2ea-07a3cf34af4r"