![]() ![]() The synchronization to Office 365 is essentially “one-way” such that any change to a distribution group has to be made in Active Directory and then synced to Office 365. The basic source of the issue is that when you’re using Directory Synchronization, objects are authored in your on-premises Active Directory. It is also an issue where unfortunately there are not a lot of great options for resolution.īelow are some options that can help mitigate this issue in at least some scenarios. This limitation should hopefully not come as a surprise, it’s a topic I discuss with my clients during every Exchange Online engagement. If you have users that manage their own distribution groups via Outlook, you’ll find that this functionality does not work once the group manager has been moved to Exchange Online. One of these limitations is around distribution groups that have had managers assigned for administrative purposes. There are, however, a few limitations with Exchange Hybrid and Directory Synchronization. Users, for the most part, are unaware of whether their mailbox is in the cloud or on-premises. Exchange Hybrid and Directory Synchronization provide for the most full-featured integration experience with your on-premises messaging environment.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |