4.4. Reflection Checkpoint

Key Takeaways

• Built-in Copilot features are embedded in M365 apps; agents are discrete, scoped, governable AI automations built in Copilot Studio
• Copilot has two billing models: flat monthly per-user license (for frequent users) and pay-as-you-go metered billing (for SharePoint Copilot and agents)
• Researcher = deep research + web; Analyst = data analysis + Python execution; Custom agents = organization-specific, built in Copilot Studio
• Agent lifecycle: Draft → Test → Submit → Approve → Publish → Monitor → Decommission
• Copilot Analytics tracks adoption; low usage after deployment is an adoption problem, not a technical problem
• Both M365 admin center and Power Platform admin center are needed for full agent administration

Connecting Forward

Phase 5 consolidates everything: exam strategy, key comparison tables, and mixed practice questions. Use it to stress-test your mental models before exam day.

Self-Check Questions

• A user wants to build an agent that HR staff can use to answer employee questions about benefits. The agent should only access documents in the HR SharePoint site. Walk through the lifecycle: where is it built, who approves it, where is it published, and what ongoing monitoring is needed?
• Your organization pays for 100 Microsoft 365 Copilot per-user licenses. A VP asks whether they also need to pay separately for Copilot in SharePoint sites. What is the answer, and why?