Copilot Studio: Introduction & Guide

Welcome to the Copilot Studio Pilot!

You're exploring Copilot Studio at the University of Miami, a powerful tool designed to extend the capabilities of Copilot for Microsoft 365. This platform offers advanced features beyond the standard license and is currently available through a limited pilot program.

If you already have access to Copilot Studio—or want to request access—please review the guidelines and responsibilities associated with participation, as this opportunity includes both enhanced functionality and important considerations for responsible use.

Why Copilot Studio?

Copilot Studio lets you design, build, and deploy advanced AI agents (chatbots) for scenarios that go beyond standard Copilot for Microsoft 365. Copilot Studio is a developer-focused platform designed for advanced users who want to build, customize, and deploy sophisticated AI-powered copilots. It provides granular control over logic, data integration, and user experience, making it ideal for technical teams and power users.

Cards

Key capabilities include:

  • Deploying agents to websites, Microsoft Teams, and other platforms
  • Integrating knowledge from internal documents and public sources
  • Customizing agent behavior, appearance, and authentication

Use Copilot Studio when:

  • You need to publish an agent to a website or multiple channels
  • Your use case requires advanced customization or system integration 

Alternatively, consider simpler options* when:

  • You only need basic Q&A or document summarization
  • No external integrations or complex workflows are required

*Examples of simpler options include Copilot for Microsoft 365 or FAQ bots.

Request Access to Copilot Studio

Ready to join the pilot program?

To request access to Copilot Studio, please submit a General Request form via ServiceNow. In the "Short description," include: Copilot Studio.

Request Access to Copilot Studio

Responsibilities & Risks

As a Copilot Studio pilot participant, you are expected to:
  • Adhere to all governance, security, and data compliance policies established by the organization.
  • Maintain and update agents at least every 180 days to ensure functionality and compliance.
  • Apply least-privilege access principles when configuring connectors and data sources.
  • Enable audit logging and retain version history for transparency and accountability.
  • Clearly disclose that chatbot responses are AI-generated in all user-facing interactions.
Risks to be aware of:
  • Sensitive data exposure if agents are misconfigured or improperly secured.
  • Compliance or security issues resulting from misuse or insufficient monitoring.
  • Limited support availability—Copilot Studio is a developer-focused tool. While the AI team can provide guidance, pilot users are expected to be proactive and self-sufficient.
Important: All pilot participants share a single environment and a monthly message allocation. As of November 2025, the allocation is 1 million messages per month. If one agent consumes a disproportionate number of messages, the entire environment may be impacted, and all agents could stop functioning until additional message credits are provisioned.

Integration Rules

  • Access to Copilot Studio does not grant permission to integrate with systems of record (e.g., Epic, Workday, etc.) without (a) additional support from IT, and (b) explicit approval from Operations.
  • All integrations must be reviewed for compliance, security, and operational impact.

Additional Guidelines

1. Act responsibly and professionally.
2. Practice ethical AI use (e.g., avoid harmful content, medical advice, or discriminatory outputs).
3. Limit exposure on public platforms—do not publish agents in uncontrolled environments.
4. Do not share sensitive or proprietary information through agents or connectors.
5. Publish agents only on approved channels (e.g., managed webpages, Microsoft Teams, Microsoft 365).

Best Practices

  • Plan Carefully: Define your agent's purpose, data types, and monitoring plan before building.
  • Test Thoroughly: Validate agent output and monitor for potential misuse.
  • Stay Compliant: Adhere to University of Miami data classification and governance policies.
  • Continuous Improvement: Participate in feedback loops and update your agents regularly.

Scenarios: When to Use Copilot Studio vs. Simpler Solutions

Scenario Do You Need Copilot Studio? Notes
Deploying agent to website Yes Requires advanced features
Simple Q&A or document summarization No Use standard M365 Copilot
Integration with Epic/Workday Only with approval Needs IT/Operations review and support
Handling sensitive data Yes, with oversight Must follow all compliance policies
Departmental and/or experimental use Maybe Check if simpler tools suffice

Additional Important Details

  • Documentation: Maintain clear documentation for each agent, including purpose, owner, and support contact.
  • Limited Support: The AI team will provide guidance, templates, and escalation support for strategic or sensitive use cases; however, keep in mind that day-to-day Copilot Studio troubleshooting and maintenance are your responsibility.
  • Coming Soon – Training & Enablement: Copilot Studio training materials, workshops, and Copilot for Microsoft 365 Champion Program for knowledge sharing are in development.

The University's Copilot Studio offering is evolving, and we are constantly updating our site's content. Please continue to regularly check this site for additional updates!

Top