Anonymized engagement summary: Microsoft Intune configuration for three campuses managing their own Windows, iOS and Android devices at a public university (2023)
Anonymized engagement summaryPublic university · 2023
Opening answer. In 2023 EPC Group was engaged by a public university to complete its Microsoft Intune deployment. The goals were to control and secure its Windows 10, iOS and Android devices, enforce policy, and support remote deployment. The scope:
- configure Intune so that each of the university's three campuses can manage its own devices
- set up device auto-enrollment, Apple enrollment and forced enrollment of domain-joined workstations
- deploy device and app management, app-protection, compliance and conditional access policies
- provide on-the-job training so the in-house team can run Intune with little outside help
The work was scheduled for two to three weeks.
This is an anonymized engagement summary published under EPC Group's anonymized-engagement rule: the client is not named, no commercial terms are published, and every statement is EPC-reported. Named, documented engagements are in the Evidence Center.
Problem and scope
| Item | Scope |
|---|---|
| Organization | A public university |
| Situation | An existing Intune deployment to be completed and extended across Windows 10, iOS and Android devices |
| Multi-campus requirement | Intune configured for three campuses so that each campus manages its own devices |
| Planning | Requirements and business use cases; device platforms and requirements; the groups and users for rollout and the enrollment approach for each |
| Design | Device enrollment plans; PKI and iOS push-certificate options |
| Configuration | Device auto-enrollment; device policies for iOS and Windows; device and app management policies; app-protection and compliance policies; conditional access; device and resource profiles; Apple enrollment; forced automatic enrollment of domain-joined workstations; enrollment of Windows and iOS devices |
| Acceptance measures | A successful Autopilot reset with apps reinstalled; identified devices enrolled; policies, profiles and conditional access deployed automatically |
| Timeline | An estimated two to three weeks, with weekly status reports and meetings |
Not reported: device counts per campus, the go-live date and any measured result.
Approach and artifacts
Configure for three campuses. Intune is configured so that each of the three campuses can manage its own devices, and policies, profiles and conditional access are deployed automatically.
Define done in testable terms. The engagement names its success checks explicitly: an Autopilot reset that brings a device back with its apps reinstalled, enrollment of the identified devices, and automatic deployment of policies, profiles and conditional access.
Train while configuring. On-the-job training runs alongside the configuration work so the university's technical staff can keep running Intune afterwards.
What EPC Group delivered and what is not claimed
| Claim | Basis | Status |
|---|---|---|
| The university contracted EPC Group for a three-campus Intune configuration | EPC engagement record | Contracted (EPC-reported) |
| Devices enrolled, success checks passed, or measured results | Not reported | Not claimed |
Related services
Microsoft Entra ID and Intune · All case studies · Talk to a senior architect
Last updated by Errin O'Connor, Founder & Chief AI Architect, EPC Group
Related service: Microsoft Intune Consultants: MDM & Zero Trust
Author: Errin O'Connor, Founder & Chief AI Architect, EPC Group · Published October 25, 2026 · Project alias EPC-2023-ANON-EDU-INTUNE · Published under the anonymized-engagement rule.