Intune and Jamf templates

EasyCC ships pre-built configuration templates for the two most common MDM tools. Download, fill in your values, paste into your MDM console.

Microsoft Intune (Settings Catalog)

File	Where
`intune-settings-catalog.json`	docs/enterprise/intune-settings-catalog.json

What's in it

A Settings Catalog import file with placeholder values for every supported policy field. After import, you edit the values to match your fleet.

Importing

Download

Grab the file from the link above.

Open Intune admin center

Navigate to Configuration profiles

Devices → Configuration → Create → New Policy.

Settings catalog

Field	Value
Platform	Windows 10 and later
Profile type	Settings catalog

Import

Click Import at the top of the editor and select the downloaded JSON. Intune populates the catalog.

Edit values

Walk through each field. Set values that match your fleet. Common picks:

release_channel: stable
force_update_after_hours: 168 (7 days)
safety_deep_check_enabled: false (default) or true (regulated)

Assign

Assign the profile to your pilot device group first; expand once stable.

Jamf Pro (Configuration Profile)

File	Where
`jamf-com.easycc.app.mobileconfig`	docs/enterprise/jamf-com.easycc.app.mobileconfig

What's in it

A .mobileconfig (Apple's Configuration Profile format) with placeholder values for every supported policy field.

Importing

Download

Grab the file from the link above.

Edit values before upload

Open the .mobileconfig in a text editor (it's XML). Find the placeholder values and update them to match your fleet.

For the syntax patterns, see PowerShell and plist snippets.

Open Jamf Pro

Navigate to Configuration Profiles

Computer Management → Configuration Profiles → New.

Set basics

Field	Value
General → Name	EasyCC Managed Config
General → Distribution Method	Install Automatically
General → Level	Computer Level

Upload

Application & Custom Settings → Upload your .mobileconfig.

Scope

Pilot Smart Group first; expand once stable.

Workspace ONE (uses the Jamf .mobileconfig)

The same .mobileconfig works for Workspace ONE on macOS. In Workspace ONE UEM Console:

Resources → Profiles → Add → macOS → Custom Settings
Upload the .mobileconfig

For Windows side of Workspace ONE, use the Intune Settings Catalog format (Workspace ONE accepts the same OMA-URI structure).

Kandji and Mosyle (use the Jamf .mobileconfig)

Same file works in:

Kandji → Library → Add → Custom Profile → Upload .mobileconfig
Mosyle → Profiles → New Profile → Custom Settings → Upload .mobileconfig

Both consume the standard Apple .mobileconfig format.

SCCM (no shipped template)

SCCM doesn't have a single template format we ship. For SCCM:

Use a Configuration Item with Registry settings — see SCCM
Or run a PowerShell script that writes the same registry values — see PowerShell and plist snippets

Active Directory Group Policy (use the ADMX/ADML)

For traditional GPO deploys, use the ADMX/ADML files instead:

See ADML and ADMX for installation.

Customizing the templates

The shipped templates have placeholder values. After import, edit them to fit:

Pin to your fleet's release channel
Set your update endpoint (if using a self-hosted mirror)
Set your safety scanner posture (regulated vs general office)
Adjust update deferral

There's no "wrong" set of values — pick what matches your org.

When templates need updating

When EasyCC adds new managed-policy fields, the templates are updated to include them. To take advantage:

Download the new template
Re-import into your MDM
Existing field values are preserved; new fields get defaults

The template format itself is stable — Intune Settings Catalog and Apple .mobileconfig formats don't change in incompatible ways.

Where to find these files

The canonical source is the EasyCC GitHub repo's docs/enterprise/ directory. The same files ship with EasyCC source releases.

If GitHub is blocked from your network, the files are also available in the EasyCC binary distribution under docs/enterprise/.

Intune and Jamf templates

On this page