Office 365 Group WriteBack - What is the use case?

%3CLINGO-SUB%20id%3D%22lingo-sub-210159%22%20slang%3D%22en-US%22%3EOffice%20365%20Group%20WriteBack%20-%20What%20is%20the%20use%20case%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-210159%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20been%20reading%20up%20on%20this%20to%20work%20out%20if%20I%20need%20it.%20From%20what%20I%20can%20tell%20it%20is%20purely%20so%20that%20Office%20365%20Groups%20show%20up%20in%20Outlook%20for%20those%20users%20whose%20mailbox%20is%20still%20on-premises.%20Is%20this%20correct%3F%20Are%20there%20any%20use%20cases%20which%20I%20am%20not%20getting%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20customer's%20initial%20implementation%20of%20Office%20365%20will%20be%20to%20use%20Teams%2FPlanner%20and%20leave%20all%20their%20mailboxes%20on%20prem%20until%20we%20can%20untangle%20that%20spaghetti.%20So%20give%20that%20all%20the%20groups%20will%20have%20Teams%20then%20users%20will%20interact%20with%20the%20through%20the%20Teams%20client%20and%20not%20Outlook.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-210159%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOffice%20365%20Groups%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-217814%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20Group%20WriteBack%20-%20What%20is%20the%20use%20case%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-217814%22%20slang%3D%22en-US%22%3E%3CP%3EThat's%20a%20question%20best%20addressed%20to%20Microsoft.%20I%20don't%20write%20their%20documentation.%20We%20do%20cover%20some%20issues%20in%20the%20chapter%20on%20hybrid%20recipients%20in%20the%20Office%20365%20for%20IT%20Pros%20ebook%2C%20but%20this%20is%20an%20evolving%20area%20and%20you%20should%20probably%20do%20your%20own%20testing%20with%20your%20own%20use%20cases%20to%20satisfy%20yourself%20as%20to%20the%20right%20choice%20for%20your%20organization.%20An%20example%20of%20recent%20evolution%20is%20the%20support%20for%20compliance%20records%20captured%20by%20Teams%20for%20hybrid%20recipients.%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwww.petri.com%2Fteams-compliance-records-hybrid-exchange%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.petri.com%2Fteams-compliance-records-hybrid-exchange%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-217751%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20Group%20WriteBack%20-%20What%20is%20the%20use%20case%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-217751%22%20slang%3D%22en-US%22%3EInferior%20is%20a%20subjective%20term.%20Do%20you%20have%20a%20link%20to%20any%20documentation%20which%20outlines%20the%20limitations%20of%20the%20following%20use%20cases%3A%3CBR%20%2F%3E1%3A%20End%20users%20have%20on-prem%20Exchange%20with%20no%20Hybird%3CBR%20%2F%3E2%3A%20End%20users%20have%20Hybrid%20Exchange%20with%20on-prem%20mailboxes%3CBR%20%2F%3E3%3A%20End%20users%20have%20O365%20mailboxes%20with%20Hybrid%3CBR%20%2F%3E4%3A%20Exchange%20is%20fully%20in%20cloud.%3CBR%20%2F%3E%3CBR%20%2F%3EThese%20vague%20assertions%20are%20a%20barrier%20to%20adoption.%20Customers%20want%20to%20know%20EXACTLY%20what%20their%20end%20user%20experience%20is%20going%20to%20be.%20Not%20just%20that%20it%20will%20be%20%22better%22%20if%20they%20migrate%20to%20the%20cloud.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-214160%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20Group%20WriteBack%20-%20What%20is%20the%20use%20case%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-214160%22%20slang%3D%22en-US%22%3EThere%20is%20actually%20another%20use%20case%2C%20at%20least%20for%20us.%3CBR%20%2F%3EWe're%20using%20SSCM%20and%20I%20can%20reuse%20those%20groups%20for%20app%20deployments%20%3A)%3C%2Fimg%3E%3CBR%20%2F%3EExample%3A%20a%20self%20managed%20group%20of%20users%20should%20have%20an%20app%20installed%20on%20their%20windows%20devices.%20Whenever%20the%20group%20owners%20adds%20somebody%2C%20the%20app%20gets%20deployed%20to%20their%20device.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-213720%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20Group%20WriteBack%20-%20What%20is%20the%20use%20case%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-213720%22%20slang%3D%22en-US%22%3E%3CP%3EVasil's%20point%20is%20well%20made.%20If%20you%20want%20to%20use%20the%20extended%20functionality%20of%20Office%20365%20(Teams%2C%20Groups%2C%20and%20Planner)%2C%20then%20move%20mailboxes%20to%20the%20cloud%20first.%20The%26nbsp%3Bexperience%20for%20on-premises%20mailboxes%20will%20always%20be%20inferior%20to%20that%20enjoyed%20by%20cloud%20users.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-210240%22%20slang%3D%22en-US%22%3ERe%3A%20Office%20365%20Group%20WriteBack%20-%20What%20is%20the%20use%20case%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-210240%22%20slang%3D%22en-US%22%3E%3CP%3EThat%20and%20mail%20flow.%20If%20your%20customers%20wants%20to%20leverage%20group-backed%20app%20such%20as%20Teams%20or%20Planner%2C%20he%20should%20really%20consider%20moving%20the%20mailboxes%20to%20the%20cloud.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

I've been reading up on this to work out if I need it. From what I can tell it is purely so that Office 365 Groups show up in Outlook for those users whose mailbox is still on-premises. Is this correct? Are there any use cases which I am not getting?

 

My customer's initial implementation of Office 365 will be to use Teams/Planner and leave all their mailboxes on prem until we can untangle that spaghetti. So give that all the groups will have Teams then users will interact with the through the Teams client and not Outlook.

5 Replies

That and mail flow. If your customers wants to leverage group-backed app such as Teams or Planner, he should really consider moving the mailboxes to the cloud.

Vasil's point is well made. If you want to use the extended functionality of Office 365 (Teams, Groups, and Planner), then move mailboxes to the cloud first. The experience for on-premises mailboxes will always be inferior to that enjoyed by cloud users.

There is actually another use case, at least for us.
We're using SSCM and I can reuse those groups for app deployments :)
Example: a self managed group of users should have an app installed on their windows devices. Whenever the group owners adds somebody, the app gets deployed to their device.
Inferior is a subjective term. Do you have a link to any documentation which outlines the limitations of the following use cases:
1: End users have on-prem Exchange with no Hybird
2: End users have Hybrid Exchange with on-prem mailboxes
3: End users have O365 mailboxes with Hybrid
4: Exchange is fully in cloud.

These vague assertions are a barrier to adoption. Customers want to know EXACTLY what their end user experience is going to be. Not just that it will be "better" if they migrate to the cloud.

That's a question best addressed to Microsoft. I don't write their documentation. We do cover some issues in the chapter on hybrid recipients in the Office 365 for IT Pros ebook, but this is an evolving area and you should probably do your own testing with your own use cases to satisfy yourself as to the right choice for your organization. An example of recent evolution is the support for compliance records captured by Teams for hybrid recipients. https://www.petri.com/teams-compliance-records-hybrid-exchange