Forum Discussion
Prevent users to change profil photo
- Set-OWAMailboxPolicy applies only for OWA and users can able to change their photos from other O365 services. Also this policy will take effect after 60 minutes,
Dean_Gross Standards. We have users that have been uploading goofy pictures, replacing their professional pictures.
Users perception vs Company perception of a professional photo to promote the company image is a good example.
Dear Dean,
This question is also opened in our case, and finally we let the Picture profile management to the Users himself but encouraging to respect some HR policy (not place picture of someone else like baby, not place to much holidays pictures, not place logo pictures, etc. ...).
Another case, i can see is to let only one place managing the user profile picture which could be the internal HRIS Application. This is the high level point in our company when the deployment application will be done globally (more than 120 countries and more than 80'000 concerned).
So anyway, i think it could be anyway better to educate the user to explain them what is acceptable and what is not, than block them.
Fab
Because companies dont want to see pictures or your dog, or your baby, or your favorite football team etc...
Hi Dean,
Good question.
One reason as I see is, to maintain a standard across the organization. The photo you're uploading to your social media profile page may not be the most appropriate for your work environment. So, to maintain a standard across the organization, the IT and HR departments can work collaboratively and upload a standardized photo, and then they can disable the ability change the photo by the user to avoid any conflicts.
Although it is true that software vendors create services with many features, specially cloud solutions such as Office 365, they do not make customized versions for individual customer. You may find features you like and features you don't like. But, that doesn't mean you have to use the product with all the features that comes right out of the box. Instead, creators have made it possible for the customer to disable features that they do not want. Also, if there's some feature missing, there's a way of providing your feedback and if there's a high demand, they will implement it. :)
Hope this helps you in some way. :)
Thank you,
Muditha Chathuranga
- Mmm...Dean, I agree with your comment when we are talking about an enterprise customer or event a government one...but for education (Harry's case) the scenario is a little bit different
- Juan, thanks again for providing your perspective. I don't have any Edu clients so I frequently forget about that unique set of use cases. I would expect that allowing kids to change their photos could create a lot of problems and preventing this type of personalization would be desirable.
This is just another example of why MS needs to include more admin controls when they initially deploy services. Providing minimum viable products to gather data could be very misleading because many customers will not even try it out if they can't control it.Another reason is to maintain professionalism. So you don't have a refrigerator, high school mascot, and potentially something NSFW in a Teams call/message, email, etc
These photos are only internal from my experience but if someone wants to put a picture of steak up, it could offend a vegan user. (Not my opinion, but you get the point.)
Easier to turn the option off and keep everything professional and congruent.
