Anonymized engagement summary: Microsoft Intune configuration for three campuses managing their own Windows, iOS and Android devices at a public university (2023)
Contracted — countersigned (EPC-reported; documents private)First-pass editionA public university (client not named) · 2023 · Project ID EPC-2023-ANON-EDU-INTUNE
Last updated by Errin O'Connor, Founder & Chief AI Architect, EPC Group
Opening answer. In March 2023 a public university countersigned a statement of work with EPC Group 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.
Disclosure. This is an EPC-reported anonymized engagement summary. The client is not named. The countersigned statement of work is retained privately and is not published in the Evidence Center, so this account is outside the Evidence Center's documented-engagement counts. Every engagement fact below is taken from that document.
Verification class
Contracted — countersigned (EPC-reported; documents private). The university's systems operations manager signed the statement of work electronically in March 2023. No enrollment record, acceptance or outcome measurement is cited or claimed.
Buyer problem and scope
| Item | What the statement of work states |
|---|---|
| Buyer | A public university (client not named) |
| 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 |
Unknowns, not stated in the document cited: 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 statement of work 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.
Document (held privately):
| Document | Date |
|---|---|
| Statement of work, Microsoft Intune consulting and development (countersigned) | March 2023 |
Results and limitations
| Claim | Basis | Status |
|---|---|---|
| The university contracted EPC Group for a three-campus Intune configuration | Countersigned statement of work, March 2023 | Contracted (EPC-reported; documents private) |
| Devices enrolled, success checks passed, or measured results | No document cited | Not claimed |
Provenance
- Source: the countersigned statement of work (March 2023), held privately. Engagement ID: EPC-2023-ANON-EDU-INTUNE, an alias unrelated to the client's name.
- Anonymization: sector and organization type only, under EPC Group's anonymized-case rule; the university's name, location, campus names, staff names and commercial terms are not published.
- Not claimed: client endorsement, completion, or any measured result.
- Author: Errin O'Connor, Founder & Chief AI Architect, EPC Group, who signed the statement of work for EPC Group.
Revision history
- 2026-10-25: anonymized engagement summary published from the engagement's countersigned statement of work.
Related service
Microsoft Intune consulting · Talk to a senior architect
Author: Errin O'Connor, Founder & Chief AI Architect, EPC Group · Published: 2026-10-25.