Building your team

Once you understand your customer use cases for your copilot, you can form a team and get them trained. Delivering a large copilot is a complex project with many different stakeholders within and beyond your organization. This section outlines the roles and responsibilities to align everyone in the project.

Internal team

Most customers treat a copilot implementation like any other project. It usually consists of the following roles:

External team

The Third party delivery partner is typically a System Integrator that leads various activities.

1. Project management-Sets up workstreams and reviews with the customer.

2. Copilot development–Developers and analysts who have experience with Copilot Studio, copilots, and related technologies.

3. Training

4. Administration/governance setup

5. Hackathons and other nurture events-Drives technology adoption and knowledge sharing.

Microsoft

Microsoft delivers the Copilot Studio service.

1. Account team - Account Executive, Account Technical Strategist, Technical Specialist, and Customer Success Manager

   1. Alignment on success and goals with the customer.

   2. Ultimate advocate for the customer within Microsoft.

   3. Leads business discussions and escalations.

   4. Attends all business calls until goals are met.

2. Product group

   1. Develops product features based on customer needs.

   2. Customer Advisory Team (CAT)–Engages with select customers, providing guidance on how to adopt and deploy the technology. Includes architecture reviews and monthly executive syncs.

3. Microsoft Support - Works with customers to solve issues with Microsoft software. Aims to solve issues directly but can also bring in engineering resources for challenging issues.

Training your team

For organizations that are new to building Copilot Studio copilots, training might be needed for the customer to become familiar with the technology. The following resources can assist customers with building Copilot Studio copilots, aka.ms/LearnPVA..

Training can be delivered through various channels. These channels include Technical Sales Professionals (TSPs), Microsoft Technology Center (MTC) architects, and Microsoft certified partners. In exceptional circumstances, engineering resources like Power CAT can facilitate these training sessions.

Copilot Studio in a Day

Copilot Studio in a Day is an instructor led, hands-on course that familiarizes copilot makers with Copilot Studio.

The course includes:

• Build your first copilot
• Topic suggestions
• Improve your copilot with entities, variables, and topic redirections
• Integrate with prebuilt Power Automate flows
• Build Power Automate flows for your copilot
• Authentication
• Export and import copilots, using solutions
• Create a copilot in Microsoft Teams
• Topic design
• Extend your copilot using Bot Framework skills (optional)
• Add a telephone number to your copilot using AudioCodes (optional)

Copilot Studio Architecture Series

The Copilot Studio Architecture Series can be consumed on demand. This course focuses on considerations that customers should account for when embarking on a copilot project.

The course includes:

• Planning your first copilot
• Building your first copilot
• Extending your Copilot Studio copilot with Power Platform
• Extending your Copilot Studio copilot with Bot Framework (to be announced)
• Advanced topics
• Security and governance

Project Planning