A user account that you want to run SMTP matching on needs to have an Exchange Online email address (the Exchange Online license is not required).Unfortunately, there are some limitations highlighted by Microsoft related to SMTP matching: This means that you need to create a local AD object with SMTP address that matches primary SMTP address of a user object in Office 365. To solve the problem you need to run SMTP matching. Network problems are preventing connection to Microsoft Exchange How to solve this problem This means that the user will not be able to access local public folders (legacy public folders) and any attempt of connection will throw an error:Ĭannot expand the folder. However, it causes problems for an Office 365 user when he or she wants to access public folders being on the on-premises Exchange. It is worth mentioning that this scenario is correct and supported by Microsoft. In this scenario, a user account is created in Office 365 in a hybrid setup.
A user has an account in Office 365 but not in local Active Directory
In this article, I will show you how to manage these situations in an environment with hybrid configuration and Centralized Mail Transport enabled.
A user has an account in Office 365 with an Exchange Online license assigned as well as an account in local AD with an on-premises Exchange mailbox (a single user has two separate mailboxes). A user has an account in Office 365 and in local AD (this user had two accounts before the hybrid configuration was implemented to have access to services offered by Office 365). A user has an Office 365 account and no local AD account. But this can also happen the other way round when you run the synchronization from Office 365 to on-premises AD or in both directions. You can encounter these problems when you run the synchronization from on-premises AD to Office 365. In other words, perhaps an OU that contains a certain user object, group or computer was not selected in the AAD Connect configuration wizard. The improper scope of objects synchronized with Office 365. Lack of rights to Organizational Units (OU) or AD objects (users, groups or computers) for a service account used by Azure AD Connect (AAD Connect). If you hit the roadblock during the synchronization it is most probable that the problem will be related to user synchronization between local Active Directory and Azure AD. And if that is the case, you need to do some additional adjustments. After a quick verification whether the hybrid is set up correctly, you notice that some of the users are not synchronized properly. Once you have completed a hybrid configuration in your company, it turns out that the job is not done yet. : This post was updated on January 27, 2021.
0 kommentar(er)
