Blocking Dialpad automatic updates in July 2026

In a previous post, I discussed the Dialpad app for macOS and how to block it from prompting non-admin users for admin credentials to complete a self-update.

Starting in Dialpad 2606.1.1, the environment variable method of blocking self-update has been obsoleted by a new configuration profile-based approach. This is a far more standard approach to managing Mac app settings.

To use this feature, create a profile in one’s MDM with the following custom plist for the com.electron.dialpad domain:

<dict>
	<key>DIALPAD_DISABLE_UPDATES</key>
	<true/>
</dict>

The managed preference can be created and deployed before or after a fleet is upgraded to Dialpad 2606.1.1, but that version is required for it to be effective.

A profile can also be built using tools such as iMazing Profile Editor.

Running Dialpad 2606.1.1 or later with the preference set will log the following in ~/Library/Application Support/Dialpad/logs

Managed preference DIALPAD_DISABLE_UPDATES is set: disabling updates.

Updated dmg download locations

Around this time, Dialpad updated the locations of their macOS app dmg downloads. In fact, downloading from the old URLs supplies an old version of the Dialpad client that doesn’t support the above managed preference. At the time of writing, Jamf App Installers and Installomator have been updated to the use to the new URLs. Autopkg support is in progress.

Old:
Apple silicon: https://storage.googleapis.com/dialpad_native/osx/arm64/Dialpad.dmg
Intel: https://storage.googleapis.com/dialpad_native/osx/x64/Dialpad.dmg

New:
Apple silicon: https://download.dialpad.com/osx/arm64/Dialpad.dmg
Intel: https://download.dialpad.com/osx/x64/Dialpad.dmg

Thanks to fellow Mac admin Allen Hancock who persistedworked with Dialpad to add this feature.

Leave a comment