Add owners
Namespace: microsoft.graph
Add a user or service principal to a Microsoft 365 or security group's owners. The owners are a set of users or service principals who are allowed to modify the group object.
Important: If you update the group owners and you created a team for the group, it can take up to 2 hours for the owners to be synchronized with Microsoft Teams. Also, if you want the owner to be able to make changes in a team - for example, by creating a Planner plan - the owner also needs to be added as a group/team member.
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 | Directory.ReadWrite.All |
Delegated (personal Microsoft account) | Not supported. | Not supported. |
Application | Group.ReadWrite.All | Directory.ReadWrite.All |
In delegated scenarios, the signed-in user must also be assigned a supported Microsoft Entra role or a custom role with the required role permission. The following least privileged roles are supported for this operation:
Microsoft Entra role | Limitations | Key role permission |
---|---|---|
Group owners | Can modify all types of group owners | microsoft.directory/groups/owners/update |
User Administrator | Can modify user owners only | microsoft.directory/groups/owners/update |
Directory Writers | Can modify user owners only | microsoft.directory/groups/owners/update |
Groups Administrator | Can modify all types of group owners | microsoft.directory/groups/owners/update |
Exchange Administrator | Can modify owners of Microsoft 365 groups only | microsoft.directory/groups.unified/owners/update |
SharePoint Administrator | Can modify owners of Microsoft 365 groups only | microsoft.directory/groups.unified/owners/update |
Teams Administrator | Can modify owners of Microsoft 365 groups only | microsoft.directory/groups.unified/owners/update |
Yammer Administrator | Can modify owners of Microsoft 365 groups only | microsoft.directory/groups.unified/owners/update |
Intune Administrator | Can modify owners of security groups only | microsoft.directory/groups.security/owners/update |
Knowledge Administrator | Can modify owners of security groups only | microsoft.directory/groups.security/owners/update |
Knowledge Manager | Can modify owners of security groups only | microsoft.directory/groups.security/owners/update |
Windows 365 Administrator | Can modify owners of security groups only | microsoft.directory/groups.security/owners/update |
HTTP request
POST /groups/{id}/owners/$ref
Request headers
Name | Description |
---|---|
Authorization | Bearer {token}. Required. Learn more about authentication and authorization. |
Content-Type | application/json. Required. |
Request body
In the request body, supply a JSON representation with the @odata.id of a user or servicePrincipal object to be added
Response
If successful, this method returns a 204 No Content
response code. It doesn't return anything in the response body. This method returns a 400 Bad Request
response code when the object is already a member of the group. This method returns a 404 Not Found
response code when the object being added doesn't exist.
Example
Request
The following example shows a request that adds a user as a group owner.
POST https://graph.microsoft.com/v1.0/groups/{id}/owners/$ref
Content-type: application/json
{
"@odata.id": "https://graph.microsoft.com/v1.0/users/{id}"
}
In the request body, supply a JSON representation with the @odata.id of a user or servicePrincipal object to be added.
Response
The following example shows the response.
Note: The response object shown here might be shortened for readability.
HTTP/1.1 204 No Content
Related content
피드백
https://aka.ms/ContentUserFeedback
출시 예정: 2024년 내내 콘텐츠에 대한 피드백 메커니즘으로 GitHub 문제를 단계적으로 폐지하고 이를 새로운 피드백 시스템으로 바꿀 예정입니다. 자세한 내용은 다음을 참조하세요.다음에 대한 사용자 의견 제출 및 보기