Intune and Softphone Deployment

[Kevin Attard Compagno]

Hands-free automated installation for Windows Desktops.​

Attention System Administrators! Deploying the 3CX Softphone via Microsoft Intune allows IT admins to install the application on many devices simultaneously without manual intervention. We\'ve prepared a document to guide you through the steps.

From Manual to Au...​

Continue reading the Original Blog Post.​

 

[fabs]

Continue reading the Original Blog Post.

It would be a great benefit if the 3CX app Windows and iOs could be logged in via EntraID SSO.

 

[Kevin Attard Compagno]

Erm... I have M365 integration turned on, with SSO, and it does work on Windows. What are we missing here?

 

[fabs]

Erm... I have M365 integration turned on, with SSO, and it does work on Windows. What are we missing here?

Ah, I didn't know that the 3CX Windows app could be logged into directly via SAML, just like the web app.
Previously, I always had to provision the 3cx windows app via the web app.

 

[Evolute IT]

Erm... I have M365 integration turned on, with SSO, and it does work on Windows. What are we missing here?

We mean: instead of opening the softphone and putting the FQDN to then click SSO M365 and them go to browser > webclient > app again, it'd be cool if it could grab the config from Intune (via a Json/Plist/whatever) and autologon using the M365 windows credentials (when the PC is signed in via Entra.)

Kinda like Outlook which autoconnects when opening it for the first time on a domain-joined PC that has Exchange/M365 setup.

 

[Kevin Attard Compagno]

Well, Outlook has ONLY ONE URL to go to for that task. The 3CX Softphone, however, needs to first know WHICH PBX is integrated with M365.

The "extra step" is unavoidable.

Unless you want to run some script to pull an extension's configuration, and deploy that to the PC also?

 

[Evolute IT]

Well, Outlook has ONLY ONE URL to go to for that task. The 3CX Softphone, however, needs to first know WHICH PBX is integrated with M365.

The "extra step" is unavoidable.

Unless you want to run some script to pull an extension's configuration, and deploy that to the PC also?

Or just allow the app to grab config from a file that can be pushed via Intune/GPO. One that contains only the PBX FQDN and some basic config like CRM options and such. It would be a game changer to be able to provision settings in the app so that users can open it and click SSO and that's it. Even better if it can use the Windows logged-in user to do the SSO in the background and connect directly to the right extension.

Also, not entirely true. Outlook does not have ONE URL, it depends on the setup. If on-prem, the GPO is telling Outlook where to go for autodiscovery. If Cloud, it uses the domain/username of the person to do the same: autodiscover.<the domain>.

 

[SweetAction]

I would also recommend that either the Windows app allow a pre-deployed config file or use of a DNS record (similar to how Microsoft uses the autodiscover record) to reduce friction of the sign in.

 

[accentlogic]

Would it be possible to deploy the app with a parameter that passes the 3CX URL?