Share via

Design training programs and events

This article explains how to create maker enablement programs and plan events that drive Copilot Studio adoption and learning.

Maker enablement and training lifecycle

To turn curious employees into confident Copilot Studio makers, provide a structured learning journey that meets them at their skill level and guides them to proficiency. Integrate event-based training, such as workshops, into a broader continuous learning program.

Maker personas

Tailor training to different backgrounds. For example:

  • Citizen developer or business user: Typically starts with Agent Builder in Microsoft 365 Copilot and moves to Copilot Studio as needs grow. Proficient with Power Apps and Power Automate but new to AI. Needs an introduction to AI concepts, a clear explanation of how Copilot Studio builds on existing skills (natural language triggers, generative actions), and reassurance that they can use templates to create an agent without deep coding skills.
  • Data or AI specialist, power user: Primarily uses Copilot Studio for deeper configuration and integration scenarios. Comfortable with machine learning or analytics but unfamiliar with Power Platform's low-code environment. Needs an overview of Power Platform basics (environments, connectors, Dataverse) and an understanding of how AI expertise (for example, understanding of models or data) can be applied within Copilot Studio (such as by using Model Context Protocol or custom skills).
  • IT professional or developer: Core Copilot Studio persona (IT/power user) focused on enterprise integration, governance, and scale. Strong coding and system integration skills but new to a low-code approach. Needs clear guidance on Copilot Studio architecture (assurance that it aligns with security and compliance) and advanced guidance on integrating custom APIs, handling complex enterprise scenarios, and governance so they can partner with IT.

Phased training program

Implement training in stages. For example:

Phase 1: Onboarding (Awareness → Basic understanding):

  • Introduction to AI agents and Copilot Studio capabilities.
  • Basic platform navigation and first agent creation.
  • Understanding governance and security considerations.

Phase 2: Skill building (Understanding → Competence):

  • Advanced agent design patterns.
  • Integration with existing systems and data sources.
  • Troubleshooting and optimization techniques.

Phase 3: Advanced practice (Competence → Proficiency):

  • Complex scenario development.
  • Mentoring other makers.
  • Contributing to community knowledge base.

Reinforcement mechanisms

Learning isn't one and done. Use multiple channels to reinforce knowledge.

  • Learning resources

    • Maintain a Copilot Studio learning section on your intranet with links to Microsoft Learn training modules for self-paced learning on demand.
    • Set up a playlist for recorded trainings, demo sessions, and external videos and webinars relevant to Copilot Studio. Ensure new members know about this repository.
    • Develop skills by signing up for the Power Up program, an immersive training program designed to empower individuals and teams with the skills and knowledge needed to harness the full potential of agents and Copilot Studio.
    • Ask community members to attend Agent in a Day events. These events are hands-on workshops where participants learn to build solutions using agents in a single day. Guided by experts, attendees go through the entire development process from concept to deployment. These events are highly practical, providing participants with the skills and confidence to create their own solutions.
    • More advanced solution architects and implementation leads can attend the Copilot Studio Architecture Bootcamp, a fast-paced three-day intermediate-to-advanced experience focused on proven patterns, architecture decisions, and derisking complex Copilot Studio implementations.

  • Ongoing engagement

    • Implement a "Prompt of the week" or "Agent tip of the Week" campaign in your Viva Engage or Teams channel. For example, share a cool tip like how to use follow-up prompts to refine agent answers or a before-and-after example of a manual task turned into an agent. This approach keeps learning continuous and bite-sized.
    • Periodically update training content based on community feedback and evolving technology. If many members struggle with a specific concept, such as writing effective structured prompts, organize an ad-hoc session or create a tip sheet addressing it. Conversely, if members express interest in a new capability, like a recently released Copilot Studio feature, incorporate that capability into your training as soon as possible to keep the community at the cutting edge.

By providing a clear learning journey and multiple touchpoints for education, you ensure that employees at all skill levels have a path to grow. Coupling this training program with events makes it stronger: for instance, an introductory workshop can serve as Phase 1 onboarding, or a hackathon can be the capstone of Phase 2. This synergy of structured learning and events boosts both competence and confidence, which are key to driving adoption. Remember, "Change needs makers." Your goal is to transform interested individuals into capable makers who feel confident to create AI solutions and motivated to continue learning.

Event design and execution

Events are the catalysts that spark interest, learning, and community energy. A well-designed event can accelerate adoption by providing direct experience and a sense of momentum.

Every event should have a clear objective that aligns with the community purpose. Common objectives and matching event types include:

  • Awareness and inspiration

    • Meetups: Short sessions (1-2 hours) featuring demos, customer stories, or panel discussions on AI agent possibilities. Good for introducing what Copilot Studio is and showcasing early wins.
    • Success looks like: Attendees leave excited about the potential of Copilot, with ideas for how to apply it in their context.

  • Skill acquisition

    • Workshops or bootcamps: Half-day or multi-day training events focused on teaching how to build agents. Use the curriculum from the onboarding or skill-building phases as the agenda. Provide lab guides and ensure a low student-to-trainer ratio (or use features like Teams breakout rooms with champion facilitators) for hands-on support.

  • Solution creation and innovation

    • Hackathons ("Agent-thons"): 1–2-day events where teams build prototype agents addressing real problems. Hackathons reinforce skills in a collaborative, fun environment and often produce tangible solutions (which can turn into success stories). They also help identify emerging champions who shine and help others during the hackathon.

  • Community building

    • Showcase or conference: Larger gatherings (annual) where multiple teams and units come together to share what they built, attend advanced talks, and strengthen network ties. It could be internal (like a company AI Expo) or external (for example, participating in a public Microsoft AI Tour event). These events are great for celebrating progress and attracting new interest on a significant scale.

Standardized event templates

To ensure quality and reduce planning work, use the following templates and checklists:

  • Agenda templates: Use predefined agenda structures for common event types. For example, a hackathon template might include:

    • Pre-event: Idea briefing and team formation.
    • Day 1: Kickoff, training refreshers, building time, check-point syncs with mentors.
    • Day 2: Continued building, presentation prep, final demos, judging, awards, and closing.

  • Logistics checklists

    • Venue or virtual setup
    • Equipment (projectors, whiteboards, stable internet, everyone has access to a Copilot Studio environment)
    • Supplies (name tags, snacks if in person, or digital swag if virtual)
    • Feedback channels (post-event survey in Microsoft Forms, or a quick poll in Teams during a virtual event)

  • Speaker and mentor preparation: Identify speakers (internal leaders or external experts) and ensure they know the audience and goals. For mentors (especially in hackathons or labs), brief them on their role. For example, explain how to guide without taking over, handle common technical problems, and escalate when something doesn't work.

  • Content modules

    • Use hands-on labs or the Copilot Studio Agent Academy content to get started.
    • Always end events with a call-to-action. For example, join our community forum (with QR code invitation link), sign up for the next training, or start a free trial of Copilot Studio. This approach bridges the gap between one-time events and sustained community membership.

Persona-driven approach

When designing event content, recall the target personas and ensure the agenda has something for each group:

  • Business stakeholders: Include a segment on value and strategy, such as a short talk on "AI Agents value" or a live demo of a high-impact agent.
  • Makers: Ensure hands-on building time or technical deep dives.
  • IT and admin: Address governance, such as a breakout session on how to secure and manage agents.

Use a registration survey to gauge the mix of your audience in advance and adjust content allocation. For example, if 80% are first-time makers, spend more time on basics. If many are returning from prior events, introduce some advanced content or a new feature demo.

Event format decision

Use a decision tree based on factors such as audience size, time available, and goal:

  • If the goal is broad awareness and you have a mixed audience with limited time: Host a meetup or town hall style event.
  • If the goal is training and you have a focused group willing to spend a half or full day: Facilitate a workshop using structured labs.
  • If the goal is to produce tangible solutions and build camaraderie: Run a hackathon with support from IT for data access and such, as needed.
  • If the goal is to cement a community and showcase broad progress: Organize a summit or conference, which might feature elements of all the above (keynote, breakouts, hackathon, and expo booths).

Quality consistency

Treat internal events with the same professionalism as external ones:

  • Start events by framing them in context. For example, say, "This workshop is part of our Copilot Studio Community program to empower everyone to automate tasks with AI agents." Such messaging ties the event to the ongoing community initiative so participants know there's more beyond today.

  • Document events: Assign someone to capture photos or screenshots, key learnings, and notable quotes. Use these items for internal communications and success stories. If permissible, record sessions, especially for training, so people who couldn't attend can watch on-demand. These recordings become part of your community's knowledge repository.

Post-event transition

Immediately after events, funnel participants into the community:

  • If they're not already part of the community's Teams or Viva Engage, invite them or add them automatically, if appropriate.
  • Share a concise event recap post: Explain what happened, link to materials, and add next steps. Include a section like "Here's how to continue the journey" with upcoming community calls and places to get help applying what attendees learned.
  • For hackathons, even after awards are given, follow up on what teams need to move their prototypes forward. That follow-up might lead to a working group or a connection with IT for support. Successful hackathon projects can grow into flagship community projects and involve more people over time.

By meticulously designing and executing events with these best practices, you ensure that each event is a professional, valuable experience that accelerates adoption. You're not just running events in isolation. You're using them as engines to feed the community (new members, new champions, new success stories) and as accelerators toward the community's strategic goals.

Next steps

Once you establish your training programs and event capabilities:

  1. Develop your training curriculum: Create materials for each phase and persona.
  2. Plan your first events: Start with awareness and training events before moving to hackathons.
  3. Create event templates and checklists: Standardize processes for repeatable quality.
  4. Move to community operations: Establish ongoing engagement between events.

With your training and events in place, the next step is to establish the ongoing operations that keep your community engaged and growing between events.

Manage ongoing community operations

  • Last updated on