---
title: "Copilot Studio"
canonical: "https://kb.uconn.edu/space/AI/29080748086/Copilot+Studio"
format: markdown
---
# Microsoft Copilot Studio at UConn

**Microsoft Copilot Studio** is Microsoft's low-code platform for designing, testing, publishing, and managing custom AI agents. Unlike [Copilot Chat](https://uconn.atlassian.net/wiki/spaces/AI/pages/29080485930), which is a general-purpose conversational assistant, Copilot Studio is intended for building an agent around a defined purpose, approved knowledge sources, instructions, and—when appropriate—automated actions or integrations.

**Quick answer:** Copilot Studio is primarily a tool for UConn employees who need to create or maintain a custom agent for an institutional use case. Employees can request Copilot Studio Maker access through the ITS Service Desk. The access currently provided in some UConn requests is a **Microsoft Copilot Studio Viral Trial** license. This is a trial license, not a promise of permanently free service; Microsoft may introduce a billing structure in the future.

## What can Copilot Studio do?

Copilot Studio can help an approved builder create an agent that answers questions, guides users through a process, summarizes known content, or performs defined actions. Depending on the design and connected services, an agent may be made available in Microsoft 365, a website, Teams, or another supported channel.

Common capabilities include:

- Creating a focused conversational experience for a department, service, course, or process.
- Providing answers from selected knowledge sources rather than relying only on a user's individual prompt.
- Defining instructions, topics, guardrails, and escalation paths.
- Connecting an agent to approved Microsoft 365, Power Platform, Azure, or other services when the required permissions and licensing are in place.
- Testing agent behavior before publishing it to a broader audience.

Copilot Studio does not eliminate the need for a content owner, access controls, testing, human oversight, or a support plan. An agent can produce confident but incorrect answers, and an incorrectly configured connection can expose information to people who should not receive it.

## Who can use Copilot Studio?

- **Faculty and staff:** Eligible UConn employees may request Maker access through the ITS Service Desk to build or evaluate agents for an institutional purpose.
- **Student workers:** A student worker who is acting in an employee role may be considered for access when there is a documented university business need. Access is not automatic and may depend on the account, project, data, and approvals involved.
- **External users:** An agent may potentially be published for an audience that includes people outside UConn, but the builder must identify that audience and obtain the necessary review and approval before publication. External access does not grant access to UConn data.

Access depends on having a supported UConn Microsoft account and an approved use case. Sign in with your UConn credentials when using university-supported AI services.

## How much does it cost?

> ⚠️ **Important licensing notice:** Copilot Studio access provided to UConn users is currently being fulfilled in some cases through a **Microsoft Copilot Studio Viral Trial** license. A trial license should be treated as temporary evaluation access. It implies that Microsoft may add or change billing in the future. Do not commit UConn to a production deployment based on the assumption that Copilot Studio will remain free.

There is currently no single guaranteed price for every Copilot Studio scenario. Costs depend on the license, the agent's audience and usage, and the services connected to it.

| Component | What to expect |
| --- | --- |
| Copilot Studio Maker access | May be provisioned as a Viral Trial for initial evaluation. Availability, duration, and future pricing are subject to Microsoft and UConn licensing arrangements. |
| Microsoft 365 Copilot | An optional paid employee license may be needed for certain Microsoft 365 experiences or development scenarios. This is separate from standard Copilot Chat and from trial Maker access. |
| Azure or Microsoft Foundry resources | Connected cloud or advanced AI services may create consumption-based charges and require a KFS account. |
| Service accounts and other premium services | Dedicated accounts, premium connectors, Power Platform services, or other integrations may require additional licensing, approval, or support. |

If a project may use paid licensing, cloud resources, premium connectors, service accounts, or production deployment, include a **KFS account number** in the ITS request and ask for a current cost review before proceeding.

## How to request Copilot Studio access

Submit a ticket to ITS through the <u>[support portal](https://kb.uconn.edu/portal/1?autoLogin=true)</u> or by emailing <u>[techsupport@uconn.edu](mailto:techsupport@uconn.edu)</u> for a **Copilot Studio Maker license.** Include** **the following information:

- Describe your department, role, proposed agent, intended users, and whether you are evaluating, prototyping, or planning a production service.
- Identify the data sources and services the agent may use, including whether a service account or external access is needed.
- Provide the applicable KFS account number if paid licensing or cloud consumption may be involved.

## Security and privacy

For institutional work, use a UConn-supported AI service and remain signed in with your official UConn account. UConn's agreements with supported providers state that prompts and responses are not used to train vendor models when the service is used through the university account. This protection does not replace UConn policy, data classification, least-privilege access, or review by the data owner.

Before connecting data to an agent:

- Determine whether the information is public, internal, protected, or confidential.
- Confirm that the data owner approves the proposed use and audience.
- Grant only the permissions the agent needs.
- Test expected, ambiguous, adversarial, and out-of-scope questions.
- Provide a human escalation path and identify who owns the agent's content and maintenance.

**AI outputs should always be checked for accuracy and appropriateness.** Do not use an agent as the sole basis for high-impact academic, employment, financial, legal, health, security, or other consequential decisions.

## When does ITS recommend Copilot Studio?

ITS recommends evaluating Copilot Studio when there is a clearly defined institutional problem that benefits from a repeatable, conversational workflow or a purpose-built agent—and when someone is available to own, test, secure, and maintain it.

| Need | Recommendation |
| --- | --- |
| General questions, brainstorming, drafting, or summarizing user-provided information | **Use Copilot Chat first.** Copilot Studio is usually more than is needed for a self-contained task. |
| A narrow internal FAQ or procedure based on approved content | **Consider Copilot Studio.** Start with a small, low-risk knowledge set and a named content owner. |
| A guided workflow with repeatable steps, routing, or approved actions | **Consider Copilot Studio after review.** Confirm permissions, integrations, licensing, logging, and human escalation. |
| Questions that require a user's Microsoft 365 files, email, or Teams content | **Evaluate Microsoft 365 Copilot or another approved solution.** Standard Copilot Chat does not seamlessly connect to that content, and Copilot Studio may require additional configuration and licensing. |
| A public-facing or widely used production service | **Engage ITS before building or publishing.** Plan for security, accessibility, support, reliability, usage, ownership, and future billing. |
| A high-risk decision or authoritative system of record | **Do not rely on Copilot Studio alone.** Keep qualified human review and the appropriate university system or process in control. |

## Recommended starting approach

1. Define the business or academic problem and the intended audience.
2. Confirm that Copilot Chat or an existing supported service cannot meet the need more simply.
3. Begin with a narrow, low-risk use case and approved content.
4. Test with realistic and edge-case questions before expanding access.
5. Document ownership, support, data permissions, costs, and what happens if the trial ends or Microsoft changes its billing model.

## Frequently asked questions

### Is Copilot Studio the same as Copilot Chat?

No. Copilot Chat is a general-purpose assistant available to students, faculty, staff, and student workers. Copilot Studio is a builder platform for creating custom agents and is primarily intended for approved employee-led institutional use.

### Is Copilot Studio free?

Some UConn requests have been fulfilled with a Microsoft Copilot Studio Viral Trial license. That trial access should not be interpreted as permanently free service. Microsoft may introduce billing in the future, and connected Microsoft 365, Azure, Foundry, premium, or service-account components may already involve costs.

### Can I build an agent with institutional data?

Potentially, but only within a UConn-supported platform, while signed in with your UConn account, and after confirming that the data, permissions, audience, and proposed use meet UConn requirements. Consult the data owner or ITS when in doubt.

### Who pays for related services?

Projects involving paid licenses, Azure or Microsoft Foundry resources, premium services, or service accounts generally require an identified KFS account. Confirm the billing model with ITS before expanding beyond trial evaluation.