11.1 Establish an Adoption Team

11.1 Establish an Adoption Team

Quick Answer: The AI council sets strategy, risk appetite, and go/no-go decisions. The adoption team executes enablement: licenses, change management, communications, training, champion support, and measurement. Microsoft's public Copilot guidance names the council seats and the enablement loop; it does not require you to copy any internal Microsoft Digital program name.

Exam AB-731 asks a business decision-maker to plan for AI adoption across the organization. Under that heading, Microsoft lists Establish an adoption team as its own skill, separate from Establish an AI council for strategy, oversight, and cross-functional work. If you treat those two bullets as synonyms, you will miss the question. Governance is a decision table. Adoption is a weekly operating system.

This OpenExamPrep chapter teaches how a leader stands up that operating system for Microsoft 365 Copilot and related Microsoft AI apps and services. You are not expected to write code, click every Microsoft 365 admin-center blade, or recite unpublished Microsoft org charts.

Official Microsoft pages this section uses

Cite current public pages. Do not invent a Microsoft product or internal community name that those pages do not use.

• Microsoft 365 Copilot Adoption Playbook — twelve steps for business leaders, informed by the Microsoft 365 Copilot Early Access Program.
• Drive Microsoft 365 Copilot adoption throughout your organization — Microsoft Learn's summary of the same playbook, including council membership and the four adoption phases.
• The essential guide to Microsoft 365 Copilot adoption — Microsoft Adoption's simplified loop: Plan, Implement, Adopt, Manage.
• Microsoft Copilot adoption and onboarding guide for IT admins — readiness assessment, data, licenses, apps and network, setup, welcome email, and feedback.
• Implement Microsoft 365 Copilot — includes the learning objective Drive adoption by creating a Copilot Center of Excellence.

A Copilot Center of Excellence (CoE) in that Learn module is a standing enablement capability. Many organizations simply call the same group the Copilot adoption team. Use whichever label your culture will fund; do the work either way.

Council governs; adoption team executes

Microsoft's playbook Step 3 is Create an AI council. Learn's adoption unit lists four council seats that should appear in some form:

1. Executive sponsor — drives adoption and shows personal use so employees treat Copilot as encouraged, not optional theater.
2. IT enablement team — technical preparedness, rollout, onboarding support, feedback channels, and compliance plumbing.
3. Change management team — the bridge between the AI council and employees: monitor adoption, gather feedback, and make Copilot part of daily work.
4. Risk management expert — regulations, ethical standards, transparency, accountability, and trust.

That is a governing table. It decides which data classes may enter prompts, whether a Copilot Studio agent may go near customer records, and whether a pilot is allowed to scale. It is not, by itself, a training calendar, a champion network, or a communications drumbeat.

The adoption team is the group that runs enablement inside the constraints the council sets. Microsoft's essential guide is the team's weekly map:

Microsoft Learn's playbook summary groups the twelve steps into four phases that match that idea: Get ready (steps 1–4), Onboard and engage (steps 5–7), Deliver impact (steps 8–10), and Extend and optimize (steps 11–12). The adoption team lives in all four. The council is most visible in Get ready (create the council, set data and risk rules) and Deliver impact (meet regularly, decide what to celebrate and what to stop).

Who is on an AI / Copilot adoption team

Staff for enablement work, not for every policy debate. Seven seats cover the exam-style roster. In a small firm one person may wear two hats; in a global firm you may have a squad. Empty seats are the failure mode, not missing a trendy title.

Executive sponsor

Microsoft's playbook is blunt: a sponsor who is an active champion—showing how they use Copilot and talking about benefits—signals that generative AI in daily work is encouraged. For AB-731 scenarios, picture a chief operating officer (COO) or chief human resources officer (CHRO) who drafts a real staff note in Copilot in Word on stage, funds protected time for champions, and unblocks a stalled sensitivity-label project. A sponsor who only demands a return-on-investment (ROI) deck at day ninety, while still dictating emails by phone, is a barrier with a title.

The sponsor sits on both tables. On the council they vote on risk and spend. On the adoption team they open doors. They do not need to facilitate every office hour.

Change lead

Microsoft Learn's adoption unit describes change management as the bridge from council to employees. That sentence is the change lead's job description. They:

• Translate council decisions into a sequence people can live with (who gets seats first, what "good" looks like in a weekly team meeting).
• Measure attitudes. Microsoft's unit notes that 75 percent of knowledge workers use AI at work, but 46 percent of those people started in the last six months. Enthusiasm and skepticism will sit in the same staff meeting.
• Manage expectations: what Copilot can and cannot do, and when human expertise must stay in the loop. Microsoft's phrasing is that the user is in the driver's seat—the pilot—not a passenger handing judgment to the model.
• Keep the program from becoming an IT ticket queue with a fancy name.

IT enablement

IT makes Copilot safe enough to turn on and reliable enough to trust. Microsoft's playbook Step 1 is Review your security and data settings because Copilot inherits Microsoft 365 permissions. If a SharePoint library is overshared, Copilot can surface it. The admin onboarding guide tells IT to complete the Microsoft Copilot Optimization Assessment, get data ready (including SharePoint Advanced Management (SAM) where the organization has those licenses), confirm Microsoft 365 app and network requirements, assign licenses, send a welcome email, and enable feedback.

IT owns Data Loss Prevention (DLP), identity, tenant settings, and incident response. IT does not own the story of why the sales forecast meeting should change. When IT is the entire "adoption team," you get a technically correct tenant and empty usage charts.

Champions liaison, communications, training, and measurement

These four seats stop enablement from collapsing onto the service desk.

• The champions liaison recruits peer coaches, defends their time with managers, and carries patterns back to the council. Section 11.3 details the program; this seat is how the program has an owner.
• Communications writes the launch, the limitations message, and the public celebrations Microsoft's playbook Step 10 asks for. Silence creates rumor. Over-claiming ("Copilot never fabricates") creates betrayal.
• Training treats prompting as a skill. Microsoft's adoption unit states that employees often see immediate productivity gains, but it may take 6 to 12 months for a person to evolve how they use Copilot regularly. A kickoff webinar is a start, not a program. Publicize Copilot Lab, prompt guidance, Viva Learning catalogs, and role scenarios.
• Measurement uses the Microsoft Copilot Dashboard (Microsoft Learn notes it is powered by Microsoft Viva; a Viva subscription adds deeper reporting) plus qualitative stories. Dashboard counts without a business metric will not move a chief financial officer (CFO). Stories without usage data will not move a chief information officer (CIO).

Microsoft Adoption also publishes kits the comms and training seats should actually open: a downloadable Success Kit, a Launch Day kit, the Interactive Scenario Library, and instructor-led QuickStart sessions. Those are public Microsoft Adoption resources, not invented internal code names.

Intentional seats are an adoption-team decision

Playbook Step 2 belongs on the adoption team's first whiteboard: be intentional with license assignments. Microsoft recommends concentrating licenses in two or three key areas, defining a use case per team, and assigning Copilot to entire teams so people can learn from each other. Spreading one seat per department looks fair and produces no community. The Microsoft Copilot Dashboard Readiness tab is the playbook's suggested view for technical eligibility and Microsoft 365 user counts.

Microsoft's own published example started in Sales, Marketing, Customer Service, Human Resources, and Finance—meeting-heavy, writing-heavy, search-heavy work. An Early Access customer example started in Customer Service, Sales, and Customer Experience. There is no single official first-wave industry. There is an official method: pick a pain, name a metric, license the whole team, then expand.

First 90 days: what "established" looks like

Use this checklist when a scenario asks whether the organization actually has an adoption team or only a council slide.

• Days 1–30 (Plan / Get ready): Sponsor on the calendar. Council risk rules written in one page. Optimization Assessment or equivalent data review started. First-wave teams named with use cases. Change lead owns a stakeholder map.
• Days 31–60 (Implement / Onboard): Licenses on whole teams, not sprinkles. Welcome communication sent. Teams or Viva Engage community live. Training office hours on the calendar. Champions nominated, not just "whoever is enthusiastic."
• Days 61–90 (Adopt / Manage): Dashboard review with the council. Two success stories and one stop-the-bleeding issue. Decision to expand, remediate data, or pause. Champion load reviewed so the program is not a hidden second job.

Scenario: a council vote is not an adoption plan

A vice president of operations at a 4,000-person logistics company sits on the AI council. The council approves Microsoft 365 Copilot for planners and dispatchers and bans pasting customer manifests into consumer chatbots. Six weeks later, usage is flat. Dispatchers still keep private spreadsheets because a loosely permissioned SharePoint hub makes them afraid to search, no one redesigned the 7:00 a.m. stand-up, and the only "training" was a recorded demo.

The VP did not fail at governance. The VP failed to staff an adoption team. IT needed to fix oversharing. A change lead needed to put Copilot summaries into the stand-up script. Communications needed an in-policy story. Training needed prompts that cite the company's delay-code list. A champions liaison needed a dispatcher in each region. Measurement needed "minutes to replan a delayed lane," not "licenses assigned."

Once those seats exist, the council can keep governing: keep the consumer-bot ban, fund SAM, and later approve or reject a Copilot Studio agent for delay codes. The adoption team executes. That split is what AB-731 is testing when it asks you to establish an adoption team.