Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Correct admin roles for profile photo edits. #9506

Merged
merged 8 commits into from
Jan 30, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion api-reference/beta/api/profilephoto-delete.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ The following tables show the least privileged permission or permissions require
|Application | ProfilePhoto.ReadWrite.All | Group.ReadWrite.All |

> [!NOTE]
> - Global and user admins can delete the photo of any user in the organization using delegated permissions. This operation also supports application permissions. Deleting the photo of any user in the organization requires *ProfilePhoto.ReadWrite.All* or *User.ReadWrite.All* permissions. Deleting the photo of the signed-in user only requires *User.ReadWrite* permissions.
> - Global admins, User admins, and People admins can delete the photo of any user in the organization using delegated permissions. This operation also supports application permissions. Deleting the photo of any user in the organization requires *ProfilePhoto.ReadWrite.All* or *User.ReadWrite.All* permissions. Deleting the photo of the signed-in user only requires *User.ReadWrite* permissions.

## HTTP request

Expand Down
2 changes: 1 addition & 1 deletion api-reference/beta/api/profilephoto-update.md
Original file line number Diff line number Diff line change
Expand Up @@ -61,7 +61,7 @@ You can use either PATCH or PUT for this operation.
> [!NOTE]
>
> - Permissions marked with * are supported only for backward compatibility. Please update your solutions to use an alternative permission and avoid using these permissions going forward.
> - Users with admin roles such as User admins can update the photo of any user in the organization by using delegated permissions. This operation is also supported with application permissions. Updating the photo of any user in the organization requires *ProfilePhoto.ReadWrite.All* or *User.ReadWrite.All* permission. Updating the photo of the signed-in user only requires *User.ReadWrite* permission.
> - Users with admin roles such as User admins, Global admins, or People admins can update the photo of any user in the organization by using delegated permissions. This operation is also supported with application permissions. Updating the photo of any user in the organization requires *ProfilePhoto.ReadWrite.All* or *User.ReadWrite.All* permission. Updating the photo of the signed-in user only requires *User.ReadWrite* permission.
> - Updating a user's photo using the Microsoft Graph API is currently not supported in Azure AD B2C tenants.

## HTTP request
Expand Down
2 changes: 1 addition & 1 deletion api-reference/v1.0/api/profilephoto-delete.md
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@ The following tables show the least privileged permission or permissions require
|Application | ProfilePhoto.ReadWrite.All | Group.ReadWrite.All |

> [!NOTE]
> - Global and user admins can delete the photo of any user in the organization using delegated permissions. This operation also supports application permissions. Deleting the photo of any user in the organization requires *ProfilePhoto.ReadWrite.All* or *User.ReadWrite.All* permissions. Deleting the photo of the signed-in user only requires *User.ReadWrite* permissions.
> - Global admins, User admins, and People admins can delete the photo of any user in the organization using delegated permissions. This operation also supports application permissions. Deleting the photo of any user in the organization requires *ProfilePhoto.ReadWrite.All* or *User.ReadWrite.All* permissions. Deleting the photo of the signed-in user only requires *User.ReadWrite* permissions.

## HTTP request

Expand Down
2 changes: 1 addition & 1 deletion api-reference/v1.0/api/profilephoto-update.md
Original file line number Diff line number Diff line change
Expand Up @@ -60,7 +60,7 @@ The following tables show the least privileged permission or permissions require

> [!NOTE]
>
> - Users with admin roles such as User admins can update the photo of any user in the organization by using delegated permissions. This operation is also supported with application permissions. Updating the photo of any user in the organization requires *ProfilePhoto.ReadWrite.All* or *User.ReadWrite.All* permission. Updating the photo of the signed-in user only requires *User.ReadWrite* permission.
> - Users with admin roles such as User admins, Global admins, or People admins can update the photo of any user in the organization by using delegated permissions. This operation is also supported with application permissions. Updating the photo of any user in the organization requires *ProfilePhoto.ReadWrite.All* or *User.ReadWrite.All* permission. Updating the photo of the signed-in user only requires *User.ReadWrite* permission.
> - Updating a user's photo using the Microsoft Graph API is currently not supported in Azure AD B2C tenants.

## HTTP request
Expand Down
6 changes: 3 additions & 3 deletions concepts/profilephoto-configure-settings.md
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@ Content-Type: application/json

{
    "source": "cloud",
    "allowedRoles": {}
    "allowedRoles": []
}
```

Expand Down Expand Up @@ -111,15 +111,15 @@ Content-Type: application/json
```
### Configure adminstrator support for profile photo updates

The following example shows how to configure the Global Administrator and User Administrator roles to change profile photo update settings in your organization.
The following example shows how to configure the Global Administrator, User Administrator, and People Administrator roles to change profile photo update settings in your organization.

```http
PATCH https://graph.microsoft.com/beta/admin/people/photoupdatesettings
Content-Type: application/json

{
    "source": "cloud",
    "allowedRoles": ["62e90394-69f5-4237-9190-012177145e10", "fe930be7-5e62-47db-91af-98c3a49a38b1"]
    "allowedRoles": ["62e90394-69f5-4237-9190-012177145e10", "fe930be7-5e62-47db-91af-98c3a49a38b1", "024906de-61e5-49c8-8572-40335f1e0e10"]
}
```

Expand Down
Loading