directoryObject: validateProperties
Namespace: microsoft.graph
Validate that a Microsoft 365 group's display name or mail nickname complies with naming policies. Clients can use this API to determine whether a display name or mail nickname is valid before trying to create a Microsoft 365 group. To validate the properties of an existing group, use the group: validateProperties function.
The following policy validations are performed for the display name and mail nickname properties:
- Validate the prefix and suffix naming policy
- Validate the custom banned words policy
- Validate that the mail nickname is unique
Note
Invalid characters are not part of the policy validations. The following characters are invalid: @ () \ [] " ; : <> , SPACE.
This API only returns the first validation failure that is encountered. If the properties fail multiple validations, only the first validation failure is returned. However, you can validate both the mail nickname and the display name and receive a collection of validation errors if you are only validating the prefix and suffix naming policy. To learn more about configuring naming policies, see Configure naming policy.
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.Read.All | Directory.Read.All, Directory.ReadWrite.All |
Delegated (personal Microsoft account) | Not supported. | Not supported. |
Application | Group.Read.All | Directory.Read.All, Directory.ReadWrite.All, Group.ReadWrite.All |
HTTP request
POST /directoryObjects/validateProperties
Request headers
Name | Description |
---|---|
Authorization | Bearer {token}. Required. Learn more about authentication and authorization. |
Content-Type | application/json |
Request body
In the request body, provide a JSON object with the following parameters.
Parameter | Type | Description |
---|---|---|
entityType | String | Group is the only supported entity type. |
displayName | String | The display name of the group to validate. The property is not individually required. However, at least one property (displayName or mailNickname) is required. |
mailNickname | String | The mail nickname of the group to validate. The property is not individually required. However, at least one property (displayName or mailNickname) is required. |
onBehalfOfUserId | Guid | The ID of the user to impersonate when calling the API. The validation results are for the onBehalfOfUserId's attributes and roles. |
Response
If successful and there are no validation errors, the method returns 204 No Content
response code. It doesn't return anything in the response body.
If the request is invalid, the method returns 400 Bad Request
response code. An error message with details about the invalid request is returned in the response body.
If there is a validation error, the method returns 422 Unprocessable Entity
response code. An error message and a collection of error details is returned in the response body.
Examples
Example 1: Successful validation request
This is an example of a successful validation request.
Request
POST https://graph.microsoft.com/v1.0/directoryObjects/validateProperties
Content-type: application/json
{
"entityType": "Group",
"displayName": "Myprefix_test_mysuffix",
"mailNickname": "Myprefix_test_mysuffix",
"onBehalfOfUserId": "onBehalfOfUserId-value"
}
Response
HTTP/1.1 204 No Content
Example 2: Request with validation errors
This is an example of a request with validation errors.
Request
POST https://graph.microsoft.com/v1.0/directoryObjects/validateProperties
Content-type: application/json
{
"entityType": "Group",
"displayName": "test",
"mailNickname": "test",
"onBehalfOfUserId": "onBehalfOfUserId-value"
}
Response
HTTP/1.1 422
Content-Type: application/json
{
"error": {
"code": "Request_UnprocessableEntity",
"message": "The values provided contain one or more validation errors.",
"innerError": {
"request-id": "request-id-value",
"date": "date-value"
},
"details": [
{
"target": "displayName",
"code": "MissingPrefixSuffix",
"message": "Property mailNickname is missing a required prefix/suffix per your organization's Group naming requirements.",
"prefix": "Myprefix_",
"suffix": "_mysuffix"
},
{
"target": "mailNickname",
"code": "MissingPrefixSuffix",
"message": "Property mailNickname is missing a required prefix/suffix per your organization's Group naming requirements.",
"prefix": "Myprefix_",
"suffix": "_mysuffix"
}
]
}
}