How to Sync Existing Extensions with M365 without Updating their Name Fields

[Univ. of North Florida]

Hi,

We are trying to sync a a few thousand existing extensions in 3CX with M365. It is critical that we do not update these extensions name fields since other system sync back to the 3CX database and use these name fields only if they are in the exact format we have been using. Each time an existing extensions syncs though, it updates their name fields to just be their First and Last names in M365. Is there a way to stop this that I am missing? We just need the extension to sync with M365 so we can do SSO and Calendar Sync. We don't need any other extension data to change.

Thank you,

Anthony Howell

 

[Evolute IT]

The name is part of the default set of properties that are synced. You cannot change that.

You will need to simply not enable the User Sync feature unfortunately.

 

[Univ. of North Florida]

Thank you for confirming that for us. If we don't check the user sync feature it looks like no one will sync at all either.

This means that SSO and Calendar won't work at all as well, unless the users are already synced in the system?

In which case they wont unsync unless we delete them later or remove them from the sync only list?

 

[Guillaume Bourgeois]

 

[Univ. of North Florida]

Hi,

Thank you for the confirmation. We will continue looking into this project and if we have any other questions we will post them here.

Thanks again,

Anthony Howell

 

[telecoms1]

I have had exactly the same issue, recently updated one of our largest systems to V20 and started getting issues with the M365 sync, the only way we could get SSO to continue working was to add the approx 500 users into the system manually using sync only (couldn't sync all users as that would have added over 2000 students)

This resulted in all of the staff names that were specially coded to designate their position and campus location being wiped out, all of their local Caller IDs being deleted and extensions being disabled when the academy disables a user from their M365 tenant.

I have raised this with 3CX support directly and have had the following response:

Please be advised that this is how the 365 sync is designed on v20. There is no way to change it.



As a company that is focused on a high level of customer service and support, I am not too sure how we are going to go back to our customers to say that this will no longer work properly.

It is rather a shame when a well-thought-out feature is rebuilt with some of these well-thought-out features missing.

 

[Univ. of North Florida]

I have had exactly the same issue, recently updated one of our largest systems to V20 and started getting issues with the M365 sync, the only way we could get SSO to continue working was to add the approx 500 users into the system manually using sync only (couldn't sync all users as that would have added over 2000 students)

This resulted in all of the staff names that were specially coded to designate their position and campus location being wiped out, all of their local Caller IDs being deleted and extensions being disabled when the academy disables a user from their M365 tenant.

I have raised this with 3CX support directly and have had the following response:

Please be advised that this is how the 365 sync is designed on v20. There is no way to change it.



As a company that is focused on a high level of customer service and support, I am not too sure how we are going to go back to our customers to say that this will no longer work properly.

It is rather a shame when a well-thought-out feature is rebuilt with some of these well-thought-out features missing.

Hi,

Thank you for your update. It really does sound like y'all are in the exact same boat as us down to the custom name formatting. I appreciate you including the response 3CX gave to you directly about this issue. This rules out us being able to change the way the integration is done in any way.

I also agree that it sucks that this integration can't be changed in any way to fit our needs. This is a project we really want to do, but it would unfortunately mess with multiple other systems that depend on 3CX name formatting. If I find a solution I'll try to remember to post it here but for now it sounds like we simply won't be able to do the integration in its current state.

Thanks again!

Anthony Howell