SSO Only with M365 on v20

[gravasio]

Hello everyone,
As of now, we are operating on version 18 and have activated Microsoft 365 (M365) synchronization solely for the purpose of enabling Single Sign-On (SSO).

Recently, we attempted to upgrade to version 20. However, we encountered an issue where the ability to log in with Microsoft disappeared. It appears that in order to reactivate this feature, it’s necessary to also enable user synchronization and automatic extension creation; this erroneously created hundreds of inactive extensions and forced us to rollback to v18.

Can anyone confirm if this is correct? Has simple SSO support been discontinued? Are there any plans to restore this functionality?

Thanks
Giuseppe

 

[IliasL_3CX]

Please note that you will have to enable user sync at least once in order for the SSO to work, then after the users have been synced you can disable user sync and still use SSO

 

[lewiswil]

Please note that you will have to enable user sync at least once in order for the SSO to work, then after the users have been synced you can disable user sync and still use SSO

I've just tested this with my extension, once I remove myself from syncing I can no longer login with Microsoft.
We are happy to keep using user sync to allow SSO, but if we can stop this overwriting users names this would be preferred.

We have our users set up in the format "DEPT Name", to help identify the correct person when making calls, and having this change to just "Name" has caused us issues

 

[lwullschleger]

+1 for an option to block automatic 3cx users from O365 ! Need the same behaviour as V18 just to enable SSO for users that already exist and match with the email address !!

 

[lwullschleger]

And I can confirm that if the sync with M365 is not enabled, the users are not able to SSO. So you have to either select all users you want to sync manually or exclude all users you don't want to sync manually. This is really stupid ! Please 3CX Dev, reintroduce an option to sync only existing users with the email matching between 3CX and M365 ! This is a must ! We have around 100 users on M365 and need to sync only 50 of thems.. i can imagine bigger companies with numbers much higher !

 

[lwullschleger]

Please note that you will have to enable user sync at least once in order for the SSO to work, then after the users have been synced you can disable user sync and still use SSO

This is partially true, you need to disable sync completely. If you let for example only one user in the selection, all other users not synced won't be able to SSO

 

[lwullschleger]

I also noticed today that the M365 Sync override also the user details. In our example in M365 we have a cell phone number formatted like: +41 (79) 123 45 67 and 3CX copies it exactly like that. But in 3CX the mobile number need no spaces and no special characters... should be +41791234567. This means that you HAVE to adapt M365 to the 3CX requirements, which is absurd. We cannot change the format in M365 because this is the standard format in our company and we use it everywhere.... 3CX is entering soon in the lower left quadrant instead of beeing in the upper right !! Please wake up guys ! Yesterday I started looking into other PBX solutions, because too many thinks are not working with 3CX

 

[gravasio]

Any news?
Is this something you're going to fix or @lwullschleger solution will be our only option?
Thanks
Giuseppe

 

[NexusIT]

We are also looking into other phone systems. The fact that they haven't acknowledged this issue in nearly a year is a huge red flag for us. It seems like they have no plans to fix this anytime soon. We were just forced to upgrade to V20 due to the April 15th deadline.