Problem
Many environments run Firefox and Zoom, but Intune’s Settings Catalog does not include built-in update policies for these apps.
For Firefox, I initially wrote a proactive remediation script that checked the local version against Mozilla’s latest and auto-installed updates. It worked, but it was extra complexity to maintain.
Then I discovered ADMX imports. Upload the vendor’s policy templates to Intune and you get the same settings you’d have in Group Policy. Much simpler.
Constraints
- Windows 11
- Intune
Decision
ADMX files are XML-based Group Policy templates. They define what settings are available. ADML files are the language files that provide the UI text.
You’ve probably used these in on-prem Group Policy. The same files work in Intune.
Implementation
Common sources:
| App | Download |
|---|---|
| Firefox | Mozilla GitHub or included in ESR installer |
| Zoom | Zoom Admin ADMX Templates |
| Chrome | Chrome Enterprise Bundle |
| Microsoft Edge | Download from Microsoft |
| Office/M365 | Office ADMX templates |
Outcome
1. Get Your ADMX and ADML Files
For Firefox:
- Download the Firefox ADMX templates from Mozilla
- Extract the ZIP
- You’ll find:
firefox.admx- The template fileen-US\firefox.adml- The English language file
2. Import into Intune
- Go to Intune admin center → Devices → Configuration
- Click the Import ADMX tab
- Click Import
- Upload the
.admxfile - Upload the matching
.admlfile (usually fromen-USfolder) - Click Next and complete the import
The import takes a few minutes. You’ll see the status change from “In progress” to “Available”.
3. Handle Dependencies
Some ADMX files depend on others. For example, many Microsoft templates need windows.admx as a base.
If you get a dependency error:
- Note which file it’s asking for
- Import that file first
- Then retry your original import
Common dependencies:
windows.admx- Base Windows definitionswindowscomponents.admx- Windows component definitions
4. Create a Policy Using Your ADMX
Once imported:
- Go to Devices → Configuration → Create → New policy
- Select Windows 10 and later
- Select Templates → Imported Administrative templates (Preview)
- Pick your imported template
- Configure the settings you need
- Assign to your groups
Trade-offs
After importing Firefox ADMX:
- Create new policy using the imported Firefox template
- Navigate to Mozilla → Firefox → Updates
- Enable Application Update settings:
AppAutoUpdate= EnabledBackgroundAppUpdate= Enabled
This tells Firefox to update automatically in the background - no scripts needed.
Example: Zoom Auto-Update Policy
After importing Zoom ADMX:
- Create new policy using the imported Zoom template
- Navigate to Zoom Meetings → General Settings
- Configure update settings as needed
Verify the Import
After importing, you can check:
- Go to Devices → Configuration → Import ADMX
- Your template should show status “Available”
- Click on it to see all the settings it contains
Trade-offs
- One ADML per import - You can only upload one language file. Pick
en-USunless you have a specific need. - Version conflicts - If you import an older version of an ADMX that’s already built into Intune, you might get conflicts. Check if the setting exists in Settings Catalog first.
- Preview feature - Imported Administrative Templates is still in preview. It works, but the UI might change.
- Processing time - Large ADMX files can take 5-10 minutes to process.
Why ADMX Over Scripts?
I used to run a proactive remediation script for Firefox updates. It worked, but:
- Scripts need maintenance when things change
- More moving parts = more things that can break
- ADMX policies are native and vendor-supported
If the vendor provides ADMX templates, use them. Save scripts for when there’s no other option.