Anonymized engagement summary: replacing an existing mobile device management platform with Microsoft Intune for an infrastructure operations services company (2023)
Contracted — client purchase order (EPC-reported; documents private)First-pass editionAn infrastructure operations services company (client not named) · 2023 · Project ID EPC-2023-ANON-INFRA-INTUNE
Last updated by Errin O'Connor, Founder & Chief AI Architect, EPC Group
Opening answer. In November 2023 an infrastructure operations services company issued a purchase order to EPC Group for Microsoft Intune consulting and deployment. The statement of work covers replacing the company's existing mobile device management (MDM) solution with cloud-based Intune:
- discovery of devices, directory and network
- an Intune design covering email configuration, enrollment, PKI and iOS push certificates, custom policies and monitoring
- deployment of security, app-management, certificate, app-protection and compliance policies, plus conditional access
- functional, admin and end-user testing
- go-live, then train-the-trainer knowledge transfer and operational documentation
Disclosure. This is an EPC-reported anonymized engagement summary. The client is not named. The statement of work and the client's purchase order are retained privately and are 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 those documents.
Verification class
Contracted — client purchase order (EPC-reported; documents private). The company issued a purchase order for the Intune engagement in November 2023, referencing the statement of work's consulting block. No go-live record, enrollment count or acceptance is cited or claimed.
Buyer problem and scope
| Item | What the statement of work states |
|---|---|
| Buyer | An infrastructure operations services company (client not named) |
| Situation | An existing MDM solution to be replaced by Microsoft Intune |
| Objective | Control and manage access to the company's data and IT resources efficiently, with security policies for existing devices and further configuration to close vulnerabilities |
| Discovery | Use cases with stakeholders; where sensitive data lives, who can reach it and what external access exists; inventory of devices, hardware, software and platforms; review of Active Directory, Group Policy, users and groups; network and VPN assessment |
| Planning | Licensing requirements and assignment; Azure and Intune portal capabilities; conceptual architecture; rollout groups and enrollment approach; success criteria and communication plan |
| Design | Intune design; email configuration policies; device enrollment plans; PKI and iOS push-certificate options; custom policies; alerts and monitoring |
| Deployment | Deploy Intune and enroll devices. Security policies for PCs and devices; device and app management policies; certificate profiles; app-protection and compliance policies; conditional access; Intune portals; proactive monitoring alerts and reports; integration with other Microsoft security tools as needed |
| Testing and go-live | Functional validation, IT-admin scenario and end-user scenario testing before production |
| After go-live | Best practices and knowledge transfer for in-house technical teams and super users ("train the trainer"); operational documentation and knowledge-base articles; as-built documentation; post-deployment support |
| Timeline | An estimated three to seven weeks |
Unknowns, not stated in the documents cited: the number of devices or users, the platform being replaced, the go-live date and any measured result.
Approach and artifacts
Know the data before you lock the devices. Before any policy is written, discovery establishes three things: what sensitive data the company holds, who can reach it, and what external access exists. Device and app policies are designed after that.
Design the hard parts explicitly. Certificate infrastructure and iOS push certificates are design items in their own right, alongside enrollment plans and email configuration.
Test as the people who will use it. Before production, testing runs three ways: functional validation, IT-admin scenarios and end-user scenarios. Train-the-trainer sessions and knowledge-base articles leave the in-house team able to run Intune with little outside help.
Documents (held privately):
| Document | Date |
|---|---|
| Statement of work, Microsoft Intune consulting and deployment (versions 1 and 2) | September–October 2023 |
| Client purchase order for the engagement | November 2023 |
Results and limitations
| Claim | Basis | Status |
|---|---|---|
| The company committed to an Intune consulting and deployment engagement with EPC Group | Client purchase order, November 2023 | Contracted (EPC-reported; documents private) |
| Intune deployed, devices enrolled, the old MDM retired, or measured results | No document cited | Not claimed |
Provenance
- Sources: the statement of work (2023) and the client's purchase order (November 2023), held privately. Engagement ID: EPC-2023-ANON-INFRA-INTUNE, an alias unrelated to the client's name.
- Anonymization: industry only, under EPC Group's anonymized-case rule; the company's name, the platform replaced, location, 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, named in the statement of work as leading the initiative.
Revision history
- 2026-10-25: anonymized engagement summary published from the engagement's statement of work and purchase order.
Related service
Microsoft Intune consulting · Talk to a senior architect
Author: Errin O'Connor, Founder & Chief AI Architect, EPC Group · Published: 2026-10-25.