Microsoft Copilot Studio (Charity) — Pricing, Plans & What's Included

Microsoft Copilot Studio (Charity) is a nonprofit-priced user-license SKU associated with the Microsoft Copilot Studio product family, because the source catalog lists it as “Power Virtual Agent User License (Non-Profit Pricing)” under Microsoft Copilot Studio. It is intended for eligible nonprofit organizations that need to evaluate or assign the licensed Copilot Studio / Power Virtual Agents capability to named users.

Yes, it is closely related, because Microsoft Copilot Studio is the current product family while the source SKU title still uses the legacy “Power Virtual Agent User License” wording. Buyers should expect some admin or catalog views to show Power Virtual Agents naming, but should confirm the exact current Copilot Studio entitlements before ordering.

The source confirms a Charity-available user-license SKU under Microsoft Copilot Studio / Power Virtual Agents, because it lists the product family, nonprofit SKU title, and term and billing options. It does not confirm detailed service rights such as authoring, runtime, capacity, connector, channel, or generative AI entitlements, so those should be validated with IT Partner against Microsoft’s current licensing terms before purchase.

Microsoft Copilot Studio (Charity) should not be assumed to include every connected service, because Microsoft 365, Dynamics 365, Power Platform, Azure, third-party systems, premium connectors, channels, or usage-based services may have separate licensing requirements. Professional services for design, integration, testing, content governance, and change management are also not described as included in the source SKU information.

No, Microsoft Copilot Studio (Charity) is not the same license as Microsoft 365 Copilot, because Copilot Studio / Power Virtual Agents is for building or managing conversational copilots while Microsoft 365 Copilot is for AI assistance inside Microsoft 365 productivity apps. A nonprofit should choose Microsoft 365 Copilot for employee productivity in Microsoft 365 apps and choose Copilot Studio only after confirming it covers the intended conversational copilot scenario.

Assign the Microsoft Copilot Studio Charity user license only to named users who require the licensed capability, because the source SKU is a per-user license. Before assigning broadly, confirm whether the SKU grants authoring-only rights, runtime rights, both, or other rights under the current Microsoft Copilot Studio licensing model.

Yes, nonprofit or charity eligibility must be approved, because the SKU is listed as nonprofit pricing for the Charity segment. If the organization relies on Microsoft grants, donated-license allocations, or sponsored-license programs, those implications should be confirmed with Microsoft or IT Partner before ordering.

The provided source does not state a seat limit, because it only confirms the Charity SKU, per-user unit of measure, and available term and billing options. Buyers should confirm any nonprofit program limits, tenant limits, grant allocation rules, or Microsoft policy restrictions with IT Partner before purchasing or expanding seats.

The source catalog does not list a trial for Microsoft Copilot Studio (Charity), because the Charity entries are non-trial subscription options. If a nonprofit wants to test the product, it should confirm available Microsoft evaluation paths, licensing rights, and any tenant-specific eligibility before starting a pilot.

The Charity catalog lists monthly commitment billed monthly, annual commitment billed annually, and annual commitment billed monthly, because those are the term and billing combinations shown for the nonprofit SKU. The live configurator should be used at checkout to confirm the current catalog option, commitment, and payment selection.

Cancellation and seat reduction are governed by Microsoft CSP terms in effect at the time of purchase, because CSP subscriptions follow Microsoft policy for cancellation windows, reductions, renewals, and changes. A nonprofit should confirm the applicable rules with IT Partner before ordering, especially when choosing an annual commitment.

Usually a CSP subscription can be adjusted according to Microsoft’s current seat-change rules, because this is a user-license SKU managed through Microsoft cloud subscription policies. The organization should confirm add, reduce, and renewal behavior before purchase, since available changes can depend on the commitment term, billing frequency, and Microsoft policy at the time.

Microsoft Teams or Microsoft 365 may be required depending on the scenario, because publishing, collaboration, identity, and user access can depend on the channels and services the copilot uses. The Copilot Studio Charity SKU should not be treated as automatically licensing Teams, Microsoft 365 apps, SharePoint, Exchange, or other connected Microsoft 365 services.

They should not be assumed to be included, because the source does not confirm connector, Dataverse, Dynamics 365, Azure, runtime, message, or capacity entitlements for this exact nonprofit SKU. Any flow, data connection, Dynamics access, Azure service, premium connector, or third-party integration should be licensed and validated separately before deployment.

A charity should govern Copilot Studio through least-privilege access, approved environments, data loss prevention policies, content review, and controlled connectors, because a copilot can expose or act on organizational data through connected services. Public-facing or sensitive-use cases should also include privacy review, human handoff, accessibility review, logging expectations, and escalation procedures before launch.

No, the Charity SKU does not by itself guarantee Government cloud residency, GCC, or GCC High suitability, because the source only confirms Charity availability and separately indicates that Government is another segment. Nonprofits with government contracts, regulated workloads, or residency requirements should validate the correct cloud environment, tenant type, service availability, and licensing path before buying.

Yes, it may fit those scenarios if the required Copilot Studio rights and connected-service licenses are validated, because the SKU is associated with conversational copilot capabilities for eligible nonprofit customers. Start with a narrow use case, controlled content, a defined audience, and a clear owner before expanding to public or high-risk interactions.

Start by inventorying existing Power Virtual Agents bots, owners, environments, connectors, channels, and data sources, because Microsoft Copilot Studio uses the current product family while legacy naming may still appear in the SKU and admin experience. IT Partner can help confirm whether the nonprofit user SKU maps correctly to current Copilot Studio behavior in the tenant before a production rollout.

A CSP transfer or partner-of-record change generally should not require reinstalling the Microsoft tenant or interrupting existing cloud data, because the subscription management relationship changes rather than the tenant identity itself. IT Partner should still review nonprofit eligibility, current subscriptions, renewal dates, and dependencies before transfer to avoid licensing gaps or poorly timed commitment changes.

No, the Charity SKU should be used only where the customer and tenant qualify for Microsoft Charity eligibility, because the source catalog separately lists Commercial, Education, and Government segments. Commercial affiliates should use standard business licensing, Education scenarios may require student or faculty/staff-appropriate offers where applicable, and Government or GCC High scenarios should be validated under the correct government licensing and cloud requirements.