Update 1/20/2022: We have edited this post for clarity based on customer feedback.
Over the last few years, we have invested heavily in Microsoft Graph to enable developers to access the rich data ...
Updated Jan 20, 2022
Version 5.0
Blog Post
We are struggling with the conversion from Set-UserPhoto to the Graph equivalent. Our agency currently employs a PowerShell script to upload new employee photos. The photos are generated in our security badge system and exported to be used in Microsoft 365. Switching to a Graph version of the process necessitates the creation of an app, writing additional code and [possibly] editing the photos to fit one of the 9 designated sizes. There a concern that this will cause a significant increase in administration of what was originally a simple process.
In identifying which APIs to 'retire', it seems Microsoft used a metric that is not reflective of the viability of the API. It is fairly obvious that the Set-UserPhoto API would not be used very frequently but that negates the utility of the command. I feel it would be prudent to not deprecate the Set-UserPhoto cmdlet until an alternative procedure could be provided.
T