Office 365 groups is a cool feature introduced by Microsoft , this is diffrent from traditional distribution groups. When it is created members get
- Shared Inbox
- Shared calendar
- Shared Doc Library
- Shared One note
- Shared Teamsite
I will not discuss it features as it has been documented well by Microsoft. Here we will discuss about the issues with Hybrid customers as they want interoperability.
One of our Customer is on Exchange 2010 & they want that on-premise users should be able to send email to office 365 groups. Now it becomes interesting as they need Group write-back feature which is part of Azure ad premium & they need to be at-least on exchange 2013.
Even if they are on Exchange 2013 they will still need to have Azure Ad premium.
- Purchased Azure Active Directory Premium licenses for your tenant. This is required to enable the groups writeback feature in Azure Active Directory Connect.
- On-premises Exchange integration with Office 365 Groups is available in CU1 and newer releases of Exchange 2016, and CU11 and newer releases of Exchange 2013. However, Exchange hybrid requires the latest Exchange 2013 or Exchange 2016 Cumulative Update (CU) to be installed on your on-premises Exchange servers. If you can’t install the latest CU, the update released immediately prior to the current CU can be used.
There is a workaround that we can do or a customized power-shell scripting solution (which I will write if customer asks). This concept has already been discussed with Microsoft & they said yes we can do that.
Create a OU in on-premise environment with Name “Office 365 Groups”, edit the AAD connect to not synchronize this OU with azure AD.
Now for every Unified Group , I mean office 365 group just create a mail contact on on-premise where external address(Target address) will be pointing to route email to o365 group.
If groups are small in number we can manage this manually but these will constantly increase in number so you know the options 🙂
- Azure Ad premium with Exchange 2013
- Powershell customized solution.
Definitely, OOB will be better option but not for all so for other customers We can build Powershell based automated solution, lets see how much our customers require it , if we are pushed a lot than just wait for it, I will write & share the solution.
Thanks for reading