Profile Photo size recommendations across Office 365 Manager attribute It is important if you are going to update these directly that you take account for the different sizes. There is also different size recommendations for each of the profile photo storage sources as outlined in the below table. The table below explains the source for each Office 365 Profile photo. These teams were brought together to deliver a single Office 365 offering, but with an on-premises standalone product AND a multi-tenant service, some inconsistencies are inevitable. One of the main reasons for this confusion, is because Office 365 is a combination of products run by different engineering teams at Microsoft. Unfortunately if you update your profile photo in Delve, it can take up to 72 hours to update the larger photo in the Delve profile, but immediately updates the one in the top right log in area. Office 365 has some synchronization technology between the sources where photos are stored. There are many places where your profile photo is displayed and unfortunately they do not come from the same source. It helps organizations with improving the culture and promote cross team collaboration and socialization. Having profile photos across your most used application, like Outlook and Skype for Business can be extremely useful when walking around the office, or even visiting other offices to have context of people and what their role is. Profile photos are extremely useful for employee engagement in organizations. These include: SharePoint, Outlook, Delve, Skype for Business, Microsoft Teams, Office client apps, Yammer and many more.
There are many experiences in Office 365 (and on-premises products) that show people information. Profiles information in Outlook, Skype for Business, and Microsoft Teams In this article I wanted to share a little more context on it. We have put together a knowledge base article on this in the past. At Hyperfish we’re often asked the where the people information comes from that is displayed across Office 365.
0 kommentar(er)
