The problems that bring people here
Most readers arrive from one of our Intune guides with a specific problem in hand. The engagement usually starts with one of these:
Macs are joining the fleet and nothing about them is zero-touch
Platform SSO, Automated Device Enrollment, Company Portal timing and Conditional Access for macOS each have their own prerequisites, and the documentation assumes you already have a working Apple Business Manager relationship. We set up macOS enrollment so a new Mac arrives at the desktop signed in to Entra ID, compliant and already visible to Conditional Access. Our Platform SSO setup guide is the public version of that work.
ConfigMgr still runs half the estate and nobody owns the exit plan
Task sequences, software update groups, collections and compliance baselines all need an Intune equivalent, and the mapping is not one to one. Co-management is a transition, not a destination. We sequence the workload moves, repackage the applications and write the exit plan so the ConfigMgr servers eventually get turned off.
Policies conflict and compliance dashboards are green for the wrong reasons
Profiles created by different admins at different times target the same devices with different settings. Intune does not merge them; it reports conflicts and the device gets neither. Baselines are permissive enough to show green while auditors ask for CIS alignment. We untangle the assignments and rebuild the baselines so the dashboard means something.
Autopilot promised zero-touch and delivered help-desk tickets
Hardware hash collection, OEM registration, Enrollment Status Page timeouts and app dependencies stop devices at the setup screen. We build and test the Autopilot profile against your apps, your policies and your network, then document the runbook your help desk needs.
Automation and AI governance landed in Intune faster than the team could absorb
Multi-admin approval now applies to Graph API automation, AI apps are appearing as protected apps and licensing bundles keep changing. We help teams automate safely, with multi-admin approval handled in their Graph scripts, and keep AI governance settings in step with the Microsoft 365 licensing they already pay for.
How an engagement runs
Every engagement is fixed-fee and remote by default, with on-site days available in Alberta and by arrangement across the United States and Canada. Hours cover Pacific, Mountain, Central and Eastern time. US clients are invoiced in USD and Canadian clients in CAD.
Two-week Intune health check
For organizations that have Intune deployed and are not confident it is configured well. We audit the tenant for policy conflicts, compliance gaps, assignment sprawl, enrollment failures and configuration drift.
You get: a written assessment, a policy conflict analysis, a prioritized remediation roadmap and a one-page executive summary. Most migrations and rebuilds start here, because the plan has to come from your tenant and not from a template.
ConfigMgr to Intune migration
Workload assessment, co-management configuration, phased migration with pilot rings, application repackaging and Autopilot deployment. Typical duration is 8 to 12 weeks for about 500 devices and 4 to 6 months for complex estates.
You get: a migration plan, a co-management exit roadmap, repackaged applications, Autopilot profiles, compliance baselines and an operational runbook.
macOS and mobile onboarding
Apple Business Manager, Automated Device Enrollment, Platform SSO, compliance and Conditional Access for Macs, plus app protection and minimum app version policies for iOS and Android.
You get: working enrollment for a pilot group, the settings catalog policies documented with their intent, and a rollout plan for the rest of the fleet.
Ongoing advisory
Monthly reviews, policy updates for new OS releases, application packaging and escalation support for teams that need Intune expertise without a full-time hire.
You get: monthly health reports, policy updates, packaging requests and architecture guidance.
What you get at the end
We do not hand over a recommendations deck and leave. Every engagement ends with working configuration and documentation your team can maintain:
- A clean tenant with documented policies. Configuration profiles, compliance policies and security baselines organized by purpose, free of conflicts and orphaned assignments. Every policy has a name that says what it does and a description that says why.
- Compliance baselines mapped to the controls your auditors ask about. CIS and Microsoft security benchmark alignment, with a gap analysis for anything Intune cannot enforce natively.
- Autopilot and ADE workflows tested with your apps and your network, not a lab demo.
- A runbook and knowledge transfer so your team can add policies, onboard apps, troubleshoot enrollment and read compliance reports without calling us.
Proof, without naming names
We do not publish customer names or logos. These outcomes come from engagements across energy, healthcare, retail, banking and telecom, including Fortune 500 and public-sector organizations:
- Reduced endpoint compliance gaps by 40% through an Intune policy redesign.
- Migrated more than 500 devices from ConfigMgr co-management to cloud-native Intune.
- Deployed Windows Autopilot zero-touch provisioning across three business units.
- Consolidated more than 120 conflicting GPOs and configuration profiles into 18 documented Intune policies.
Kevin Kaminski has worked on Microsoft endpoint management since SMS 2003 and has been a Microsoft MVP every year since 2008. He writes the Intune What’s New series on this site, so the advice you get reflects the service as it ships this month.
Microsoft Intune consulting FAQ
What does an Intune consulting engagement cost?
Engagements are fixed-fee and scoped to your environment. The two-week health check is the usual starting point; migrations and Autopilot rollouts are quoted after it, in USD for US clients and CAD for Canadian clients. Book a discovery call and we will scope it with you.
Do you work with organizations in the United States?
Yes. Most Intune work is remote, delivered across Pacific, Mountain, Central and Eastern time from Calgary, Alberta. We work with commercial, GCC and GCC High tenants.
How long does a ConfigMgr to Intune migration take?
About 8 to 12 weeks for a straightforward 500-device estate, and 4 to 6 months for complex environments with custom task sequences, large application catalogs or regulatory requirements.
Can we keep ConfigMgr during the migration?
Yes. Co-management runs both side by side while workloads move one at a time, with a documented exit plan so the transition actually ends.
Do you manage Macs, iOS and Android as well as Windows?
Yes. macOS Platform SSO with Automated Device Enrollment, Mac compliance and Conditional Access, and app protection and minimum app version policies for iOS and Android are all regular work.
What is the two-week Intune health check?
A fixed-scope tenant review covering policy conflicts, compliance gaps, assignment sprawl, enrollment failures and reporting blind spots, delivered as a written assessment, a prioritized plan and an executive summary.
Do you support GCC and GCC High?
Yes. We account for the feature availability differences and endpoint requirements of GCC High in architecture and migration planning.
How do you handle application repackaging?
We assess the portfolio, convert legacy installers to Win32 packages with detection and requirement rules, and test in a pilot ring before production.
Related services
Windows 365 and Azure Virtual Desktop consulting — Cloud PCs and session hosts managed through the same Intune tenant
Azure consulting — the identity and network foundation your endpoints depend on
Windows 365 and Intune training — hands-on Cloud PC deployment and Intune management