Block change picture
In Skype for Business we were able to prevent users from uploading pictures for their avatar. This was done from a PowerShell script that modified the OWA policy. We should have the same option with Teams. Hopefully in UI instead of PS.
This item is still in the works, no new details to share yet.
please add this feature in. I vote YES!
Tom Mauro commented
This request could certainly use an update. It was first shared as an idea almost two years ago and nothing since. Last update was over a year ago. Please provide some details on this.
Chen Gong commented
Please implement this feature asap. Thanks.
Chris Calgher commented
Could we get an update on this? It's been a year since the last update on this issue.
Jacob Clark commented
Please provide an eta on when we will be able to prevent users from changing their avatar photo within teams. We have locked down everything else and this allows our users to circumvent the restrictions.
Yes, Constantino, appreciate if you would share that script. Thanks
Jay Miller commented
Constantino, any chance you would share that script?
Constantino Tobio commented
This seems like a simple thing to fix, really. One little slider in the policies- prevent photo updates. My corporate overlords are getting pretty salty that employees are changing their photos to random avatars. Right now I have to have a script that runs through 10,000 employees twice a week to overwrite their photos from our employee database, and as you can imagine, it takes a couple of days to complete, when it doesn't bomb out.
Andrew Chandler commented
Bump for an update too. It's been years that Teams has been out, and it's been almost a year and a half since you guys were "working on it." We just deployed Teams and users can nuke their company-approved/taken photos with Spongebob for all we can help it... Unacceptable.
Uğurcan Öndüç commented
Our users Active Directory photos are synced to O365 and are used as the profile photos within the applications. These photos are set by our HR department. The ability to change these photos for all applications has been disabled using the OWA Mailbox Policy powershell setting. Apparently, Teams does not play ball here - and our users are updating their pictures to things not appropriate for a work environment. Until this is resolved, Teams will not have a place in our organization.
Any update Warren?
This is still a big problem and no answers. This is not good. You guys are enabling users so much, that you are basically causing breaches in HR and Security policies for all your clients. This is pretty unacceptable.
The only authority in a enterprise environment to update profile photos is HR, this basically impacts critically on corporate policies. Please prioritize MS.
Pissed of MS customer commented
Reported Oct 5, 2017, 'Working On it' comes 10 months later and now here we are, 2019 and still nothing from Microsoft. If I wasn't paying so much this product, I wouldn't mind but bloody hell it's super expensive and they're screwing with customers.
I think microsoft doesn't listen user's voice!
Shame on you! it's a security risk for most of the companies. (Think about someone posted illegal content/picture on company's active directory list. )
This should be solved ASAP!
Martin Smith commented
Why is this not at the top of the Devs list? It pulls in the Photos from 365 but open to abuse?
Come on Microsoft it's not even on the roadmap! Who is in charge of these lists?
please update! Thanks.
Scott Davies commented
This has been "In the works" for nealy a year now.
Can we please get an update on this or even better implemented. We need to be able to lock this down in our office.
It would be great to avoid Cats photos in Enterprise accounts... Thanks!
If Microsoft Teams is serious business tool, it needs to allow companies to maintain their professionalism, which includes professional user photos. I appreciate that some companies may be happy with the "free" approach to user photos, but surely that decision should be up to the company policies, if they wish to go that route or not?
The last Microsoft response was almost a year ago. Can we please have an update?