Office 365 Contanct Integration

Status
Not open for further replies.

Simone Rota

Forum User
Joined
May 29, 2018
Messages
181
Reaction score
5
hi,
what kind of Office 365 users I need to have?
and
I'm going to sync to 3CX Personal Phonebooks and even in 3cx Global Phonebook?


Thanks
Simo
 
Office 365 supports at the moment the following 3 types of syncrhonizations:
* Users (You can select users from office 365 that will be created as extensions on your PBX)
* Contacts (The users that their personal contacts will be synced with the personal contacts on the Web Client are the ones that have Exchange License)
* Calendar (Synchronize extension change in WebClient based on calendar entries on O365. This requires the user to have Exchange License)

More information on: https://www.3cx.com/docs/office-365-integration/
 
Ok, just a question
Can I sync Contacts but not users? In this case, How to match Office 365 with Extension?
 
Yes you can sync the personal contacts of an Office 365 user. The match it is done based on User Name (O365) and email address (3CX PBX)
 
Done, but nothing Happend.... I Have to wait? Is there a Trigger?
 
As soon as you click OK on Management Console -> Office 365 Integration page it should trigger the synchronization.
Make sure also that the casing of the emails addresses on PBX is the same as the accounts on PBX. There is an issue that if they are not the same casing, then they will not be synced.
 
Yep but nothing happend...
Another weird thing... Adding Office 365 user (I want to sync just contact, no calendar and no user), I'm not seeing al my Office 365 users
 
Yep but nothing happend...
Another weird thing... Adding Office 365 user (I want to sync just contact, no calendar and no user), I'm not seeing al my Office 365 users

I'm not sure if you solved this but came across the same problem yesterday. In my case I found that 3CX would only show users that had the Azure AD property of UserType=Member, in our case we use Azure AD sync to synchronise users between our local AD and Azure AD and found that users created before 2014 didn't have this property set. Adding this property via PowerShell fixed the problem
 
Status
Not open for further replies.

Forum statistics

Threads
112,325
Messages
591,898
Members
165,479
Latest member
Senergia