Hi, I'm sorry if this has already been covered recently but I couldn't find anything specific at a glance...
M365 account sync and Windows app SSO would be a major improvement for us.
However, we run a single server (with SBCs) for multiple schools in our organisation, with a single M365 tenant. We have to have 'blocks' of extension numbers for each school for multiple reasons (not just vanity), most importantly because each school has it's own SIP trunk for billing purposes. Emergency services routing is critically required to be configured correctly, so each SIP trunk is set for each site as required. The extension range will route out across the correct SIP trunk (although users working in another school that call emergency services do have an issue, but this is the minority) to ensure billing and emergency service caller address and phone numbers are correct (regardless of the outbound caller ID, emergency services who need to return the call, will initially call back on the 'hidden' number as configured on the SIP trunk).
For this reason, I can't have 3CX auto-assigning extension numbers and further, with some system and manually created accounts, this could be an issue if were possible to set the required extension number in AD and then pull it in to 3CX in case of clashes. (Although, it's the lesser of two evils, if an admin doesn't check whether it's free first, then that's their fault).
Is there any way of improving this? We have 1000 staff across 8 sites that roam both internally on shared devices (as well as 1:1) and occasionally between schools, with a very small IT support team. I've scripted around this for domain joined Windows PCs with the legacy Windows client, but I need to have the least friction for the users without it becoming horrifically onerous for techs to assist them with configuring their client constantly.
Thanks
