Forum Discussion
O365 Groups and its related content (Plan, Files, etc.) when Group Owner leaves the organization?
It will be interesting to see how this is approached when Yammer + Office 365 groups work together.
The equivalent user experience in Yammer can allow a user to self-nominate themselves as admin if it becomes orphaned. That approach may work well for social-style Office 365 groups, but may not be so appropriate to others. However it keeps the administrative effort required to a minimum.
Another consideration for scripts to detect "orphaned" groups is that sometimes an account is disabled but not immediately removed. It's reasonably common practice for the account to be kept around for a short period of time before being removed from the tenant.
- what I understood from the architectural perspective if you connect Yammer group to Office 365 group you'll get the behaviour of the O365 group. http://fasttrack.microsoft.com/roadmap#I-72468
Yes, apart from the fact that the conversations are held in Yammer rather than in the Exchange group mailbox. This is actually an important point, because it means that conversations are then "hidden" from the point of compliance searches. Content searches are able to look through group mailboxes and document libraries, but they do not support Yammer. This is one good reason why any company working in a regulated industry will have a problem with Yammer Groups, even if they use Office 365 Groups to manage their membership.
There are some other differences too, but storage of conversations is the big one.
- I would highly recommend to study the Ignite session about the Yammer changes, Tony.
We can solve issues for Office 365 Groups because it supports PowerShell... Now Yammer... that's a completely different matter!
