In the past, I already wrote two posts about managing Mozilla Firefox settings with Microsoft Intune. One long post describes the whole process of uploading the firefox.admx file, building up the OMA-URI, configuring the settings etc. And a second one which only handles managing Firefox bookmarks as that isn’t really straightforward.
But As I receive more and more comments on these posts and via other channels about managing Firefox proxy settings, which is also not really straightforward, I thought to write down in this post how I managed to configure the proxy settings with Microsoft Intune.
If you’re completely new in managing Firefox settings via Microsoft Intune, I suggest to read this post first. When you’re already familiar with this solution, move on to the fun stuff.
Collect required policy settings
As with the other Firefox settings, we first need to collect some information regarding the proxy setting we’d like to configure, which we find in the firefox.admx file. If we search for proxy in the ADMX file, we see this policy setting contains 12 elements (options, which you can recognize by the IDs).
ProxyLocked
ConnectionType
HTTPProxy
UseHTTPProxyForAllProtocols
SSLProxy
FTPProxy
SOCKSProxy
SOCKSVersion
AutoConfigURL
Passthrough
AutoLogin
UseProxyForDNS
Where we could leave such an element not configured (blank/ empty) when using Group Policies, this is not the case when using Intune. We need to use all the elements in our policy, even as some of the elements themselves can be left blank.
Configure a Custom configuration profile
I assume you have already created a Custom configuration profile for the ADMX ingestion (which is a pre-requisite) and configured some other settings. Let’s add this setting to that profile.
- On the settings tab click Add
- Give the Row a Name
- Fill in the OMA-URI:
./Device/Vendor/MSFT/Policy/Config/Firefox~Policy~firefox/Proxy - Data type: String
- Value:
<enabled/>
<data id="ProxyLocked" value="true"/>
<data id="ConnectionType" value="system"/>
<data id="HTTPProxy" value=""/>
<data id="UseHTTPProxyForAllProtocols" value="false"/>
<data id="SSLProxy" value=""/>
<data id="FTPProxy" value=""/>
<data id="SOCKSProxy" value=""/>
<data id="SOCKSVersion" value="4"/>
<data id="AutoConfigURL" value=""/>
<data id="Passthrough" value=""/>
<data id="AutoLogin" value="false"/>
<data id="UseProxyForDNS" value="false"/>Above is just an example, but it shows the 6 elements which you need to configure at a minimum to get this to work.
That should be it to configure the proxy settings.
The end-result
After syncing the profile to the device, you should be able to verify the proxy setting by entering about:policies in the address bar. This shows an overview of the configure settings.
That’s it for this short post. Thanks for reading!
