- Joined
- Jul 10, 2017
- Messages
- 81
- Reaction score
- 26
When SSO wirh MS365 is activated and the email of an extension that was synced with MS365 is modified, the extension is never synced with MS365 again until it is deleted and created again.
In addition, if a user with an extension that uses SSO changes extension and the email is assigned to another extension, they will continue to access the first extension even if their email no longer corresponds. This creates a security breach. Right now the solution is to delete the extensions and recreate them.
This causes the deleted extensions to disappear from their queues and must be reassigned as an agent in each queue. if this happens on clients that handle more than 30 queues, each change like this is time consuming.
We suggest to improve the synchronization between MS365 and 3CX to avoid having to delete the extensions and to solve this problem and the security issue.
In addition, if a user with an extension that uses SSO changes extension and the email is assigned to another extension, they will continue to access the first extension even if their email no longer corresponds. This creates a security breach. Right now the solution is to delete the extensions and recreate them.
This causes the deleted extensions to disappear from their queues and must be reassigned as an agent in each queue. if this happens on clients that handle more than 30 queues, each change like this is time consuming.
We suggest to improve the synchronization between MS365 and 3CX to avoid having to delete the extensions and to solve this problem and the security issue.
Upvote
0
