Copilot Enablement Lead Engineer – Microsoft 365

Copilot Enablement Lead Engineer – Microsoft 365

Own end-to-end technical enablement of Microsoft 365 Copilot across pilot and wave deployments.

Configure Copilot scenarios, stage license assignments, validate Teams/Exchange readiness, and run cutover + hyper-care. Partner with Security/Compliance to ensure Copilot is deployed safely using least privilege (Entra PIM), audit/service health monitoring, and Purview labeling/DLP. Prepare the content estate using SharePoint Advanced Management to remediate oversharing, fix permissions/ownership, and enforce lifecycle controls.

This will be a 6/12 Month FTC

Responsibilities

• Configure and manage Copilot settings/scenarios in the Copilot admin experience; execute pilot + wave rollouts (cutover + hyper-care).

• Stage and manage Copilot license assignment by cohort; validate prerequisites across Teams and Exchange.

• Operate with least privilege using M365 admin roles + Entra PIM (JIT elevation, MFA/approval, time-bound access).

• Drive monitoring and operational readiness: audit logging, service health checks, incident triage during rollout.

• Prepare SharePoint/OneDrive for safe Copilot grounding: remediate permissions/ownership, reduce oversharing, enforce governance/lifecycle controls (SAM).

• Implement/validate Purview sensitivity labels + DLP controls to govern Copilot usage before broad enablement.

• Guide site owners through pre-flight checks; resolve last-mile access and readiness blockers.

Required Skills / Experience

• Strong hands-on M365 engineering: Teams, Exchange Online, SharePoint Online/OneDrive (enterprise scale).

• Experience delivering wave-based deployments and supporting cutover/hyper-care.

• Experience with Entra PIM / just-in-time privileged access and auditability.

• Experience with Microsoft Purview (sensitivity labels, DLP).

• Proven ability to drive content governance and permissions remediation (SharePoint).

Nice to Have

• Copilot program/rollout experience (readiness + governance).

• M&A / multi-entity environment experience.

• Runbook creation and repeatable “readiness gate” approach.

#LI-KS1