Onsite: Boston, Massachusetts

Copilot Studio Adoption & Enablement Role

Role Purpose

Support the adoption and effective use of Microsoft Copilot Studio by helping business teams identify viable agent use cases, understand governance requirements, and scale value safely. This role also provides light support to broader M365 Copilot adoption efforts.

Primary Responsibilities – Copilot Studio (Approx. 70%)

- Partner with business teams to identify and shape Copilot Studio agent use cases aligned to approved business needs.

- Act as a front door for Copilot Studio adoption questions (what is allowed, what is a good candidate, next steps).

- Support Agent Makers by reinforcing training, attestation, and governance expectations.

- Help translate business ideas into governed, scalable Copilot Studio solutions in partnership with technical and governance teams.

- Reinforce required guardrails (no autonomous agents, human-in-the-loop controls, approved connectors, DEV→UAT→PROD lifecycle).

- Support development of simple, business-friendly enablement materials explaining Copilot Studio capabilities and limits.

Secondary Responsibilities – M365 Copilot Adoption (Approx. 30%)

- Support (but do not own) broader M365 Copilot adoption and enablement efforts.

- Help position Copilot Studio as a complement to M365 Copilot, not a replacement.

- Partner with Copilot Champions and advanced users to identify ideas appropriate for Copilot Studio.

- Collect and share feedback on adoption challenges, confusion points, and enablement gaps.

What This Role Is Not

- Not a Copilot Studio developer or engineer.

- Not the governance or security owner.

- Not the primary OCM or communications lead.

Ideal Profile

- Strong business translation and stakeholder engagement skills.

- Comfortable explaining AI governance and guardrails in plain language.

- Familiar with M365 Copilot and Copilot Studio concepts (hands-on development not required).

- Able to work across business, adoption, and platform teams.