365 Integration with existing extensions

[dblum]

Can someone point me to the documentation or explain how to setup 365 integration if we had upgraded client from v16 to v18 and all the extensions already exist? Thank you

 

[NickD_3CX]

Can someone point me to the documentation or explain how to setup 365 integration if we had upgraded client from v16 to v18 and all the extensions already exist? Thank you

If on your V16 3CX, you have already configured Microsoft 365 integration and synced some extensions, there are no specific steps you need to do to upgrade to V18, all you need to do is following this guide:
https://www.3cx.com/docs/upgrading-pbx/

 

[dblum]

We had not integrated Microsoft 365 on v16 and do not want to create new extensions and want to map existing extensions to the proper user in AD. Please advise on how to do this?

 

[Evolute IT]

We had not integrated Microsoft 365 on v16 and do not want to create new extensions and want to map existing extensions to the proper user in AD. Please advise on how to do this?

Make sure the UPN on O365 is the same as their email in 3CX and it will sync to those users.

 

[MMi Solution]

want to map existing extensions to the proper user in AD.

You need to:
* put as email the login name of that user in their O365 account
* in O365 integration section of 3CX, choose that user for synchronization (you have to previously do the necessary steps to link with O365, as explaiend in the tutorial).

The only difference between an existing and not existing 3CX user is that:
* if there is an existing one (that is, one with email = O365 login), it will keep all 3CX specific things (like extension number, forwarding rules, hardphone configuration, etc)
* if there is not an existing one, then it will created, with a "next attributed" extension number

Note that for existing 3CX users, all fields common with O365 (name, surname, picture, outbound number, etc.) will be overwritten by whatever is defined in O365.

 

[Flo-R]

Thanks for the answers... they where quite helpful!
One little thing to add: The UPN in the local AD and in Azure AD must be exactly the same... including upper and lower case letters.

In my case the UPN & Mailadress was in small letters, in Azure AD the domain part of the mail address was in capital letters. In this case the sync with the existing user wont work.

I've changed the UPN in the local AD and the sync worked.