---
title: "Microsoft Copilot Studio (Microsoft)"
url: "https://ailawframework.com/software/copilot-studio"
type: "software_profile"
site: "AI Law Framework"
id: "copilot-studio"
vendor: "Microsoft"
category: "General-purpose"
segment: "General-purpose assistants"
confidence: "high"
last_reviewed: "2026-09-21"
---

# Microsoft Copilot Studio (Microsoft)

> Low-code platform to build and publish AI agents that can use Azure OpenAI, Bing, connectors and channels. Storage can be in Australia; generative inference and Bing may still leave the region unless admins block it.

Canonical page: https://ailawframework.com/software/copilot-studio  
Last reviewed: 2026-09-21

Site index for agents: https://ailawframework.com/llms.txt

Plan covered: Copilot Studio in a Power Platform environment: published agents, channels, connectors, knowledge sources and model settings. Assess each published agent separately. Licensed Microsoft 365 Copilot and consumer Copilot are out of scope.

## Capabilities

- Agentic workflows
- Knowledge search
- Document summarisation
- Intake and triage

## Key facts

| Fact | Value |
| --- | --- |
| Deployment | SaaS |
| Hosting regions | Australia, United States, European Union / EEA, United Kingdom, Multiple specified locations |
| Australian region | Yes |
| Model providers | Microsoft Azure OpenAI, Bing |
| Assurance | ISO 27001, GDPR |
| Training on customer content | No |
| Retention | Customer data can be stored in the chosen Power Platform geography (Australia East/Southeast listed). Microsoft may replicate within the same geography for durability. Prompts/outputs for generative features may be processed in another region (for Australia: in region or United States) if cross-region movement is allowed. Bing search data is stored and processed in the United States. |
| Integrations | Power Platform connectors, Azure OpenAI, Bing Search, Azure Key Vault, Azure Monitor, virtual networks |
| Legal content coverage | Agents ground on configured knowledge sources and connectors, not a licensed Australian case-law database. Each published agent must be assessed for its own sources. |
| Pricing | Microsoft list: tenant-wide Copilot Studio licence with Copilot Credit packs of 25,000 credits at USD 200/pack/month; unused credits do not carry over. Pay-as-you-go meter in Azure. Internal agents for Microsoft 365 Copilot-licensed users may consume no extra credits. Exceeding pack capacity can disable agents. |
| Australian presence | Yes. Power Platform can store Copilot Studio customer data in Australia East (NSW) and Australia Southeast (Victoria). Generative AI for Australia-hosted environments may still call Azure OpenAI in-region or in the United States, and Bing Search processing is in the United States. |
| Website | https://learn.microsoft.com/en-us/microsoft-copilot-studio/security-and-governance |

## What the research found

| Topic | Status | Finding | Open question | Sources |
| --- | --- | --- | --- | --- |
| Platform versus each published agent | Not confirmed | This profile is the Copilot Studio platform in a Power Platform environment. Licensing is tenant-wide capacity packs and/or Azure pay-as-you-go. Internal agents used by Microsoft 365 Copilot-licensed users may be included. Each published agent (channels, connectors, knowledge, authentication) needs its own assessment. Consumer Copilot and licensed Microsoft 365 Copilot are separate products. | Which environments, agents, channels and credit packs are in scope, and is PAYG overflow on? | [Copilot Studio security and governance](https://learn.microsoft.com/en-us/microsoft-copilot-studio/security-and-governance); [Microsoft Copilot Studio pricing](https://www.microsoft.com/en-us/microsoft-365-copilot/pricing/copilot-studio); [Secure your Copilot Studio projects](https://learn.microsoft.com/en-us/microsoft-copilot-studio/guidance/sec-gov-phase3) |
| AU storage; generative inference may leave AU | Public claim only | Customer data can be stored in Australia East/Southeast. Generative Copilot features for Australia-hosted environments process Azure OpenAI in-region or in the United States; Bing Search is stored and processed in the United States. Cross-region movement is on by default for GA generative features unless an admin does not consent. Regional storage does not prove regional inference. | Is our environment in Australia, is cross-region data movement off, and where does Azure OpenAI actually run? | [Data locations in Copilot Studio](https://learn.microsoft.com/en-us/microsoft-copilot-studio/data-location); [Move data across regions for Copilots and generative AI](https://learn.microsoft.com/en-us/power-platform/admin/geographical-availability-copilot); [Geographic data residency in Copilot Studio](https://learn.microsoft.com/en-us/microsoft-copilot-studio/geo-data-residency) |
| Agents, knowledge, actions, channels, GenAI | Public claim only | Makers build agents with knowledge sources, actions/connectors/skills, HTTP requests, publication to channels, Application Insights and triggers. Generative AI is powered by Azure OpenAI and Bing Search. Tenant admins can disable publishing of GenAI-powered agents. Environment admins can disable GenAI features that require data movement outside the region. | Which generative features, channels and connectors will be allowed in the production environment? | [Copilot Studio security and governance](https://learn.microsoft.com/en-us/microsoft-copilot-studio/security-and-governance); [Secure your Copilot Studio projects](https://learn.microsoft.com/en-us/microsoft-copilot-studio/guidance/sec-gov-phase3) |
| AU datacentres; US Bing; possible US OpenAI | Public claim only | Australia is a listed Power Platform geography. EU Data Boundary applies only if the tenant billing address is in the EU/EFTA and all environments are created inside the EUDB. An Australian billing address does not create an EU-style boundary. Bing Search processing for Australian environments is in the United States. | Name the Azure OpenAI and Bing countries for our AU environment with cross-region movement off versus on. | [Data locations in Copilot Studio](https://learn.microsoft.com/en-us/microsoft-copilot-studio/data-location); [Move data across regions for Copilots and generative AI](https://learn.microsoft.com/en-us/power-platform/admin/geographical-availability-copilot); [Geographic data residency in Copilot Studio](https://learn.microsoft.com/en-us/microsoft-copilot-studio/geo-data-residency) |
| USD 200 / 25,000 credits per month | Public claim only | Microsoft pricing page: Copilot Studio sold as a tenant-wide licence including Copilot Credit packs of 25,000 credits at USD 200/pack/month, plus a pay-as-you-go meter. Learn docs: unused Copilot Credits do not carry over; exceeding purchased capacity can disable agents. Packs are pooled across agents. | Quote packs versus PAYG, what happens at 100% and 125% of capacity, and which agents share the pool. | [Microsoft Copilot Studio pricing](https://www.microsoft.com/en-us/microsoft-365-copilot/pricing/copilot-studio); [Copilot Studio security and governance](https://learn.microsoft.com/en-us/microsoft-copilot-studio/security-and-governance) |
| Connectors, VNet, Key Vault, Entra | Public claim only | Agents use Power Platform connectors; maker remains responsible for destination data flow. Virtual Networks can keep connector traffic off the public internet. Secrets can sit in Azure Key Vault. Authentication, knowledge sources and HTTP requests are DLP-governed. Premium connector entitlement is included in agent licensing. | List every connector and channel on each production agent, with auth type and DLP policy. | [Copilot Studio security and governance](https://learn.microsoft.com/en-us/microsoft-copilot-studio/security-and-governance); [Secure your Copilot Studio projects](https://learn.microsoft.com/en-us/microsoft-copilot-studio/guidance/sec-gov-phase3) |
| Power Platform / Unified support | Not confirmed | Support follows the Microsoft customer agreement for Power Platform. Not inspected here. | What severity times apply if a production client-facing agent is disabled for credit exhaustion? | [Copilot Studio security and governance](https://learn.microsoft.com/en-us/microsoft-copilot-studio/security-and-governance) |
| No independent agent-quality study found | Not confirmed | Microsoft documents evaluation and rollback as implementation tasks. No published hallucination benchmark for Copilot Studio agents on Australian legal tasks was found. | Require an evaluation set and rollback plan before any agent is published to clients or staff. | [Secure your Copilot Studio projects](https://learn.microsoft.com/en-us/microsoft-copilot-studio/guidance/sec-gov-phase3) |
| Internal or client-facing agents; not a citator | Not confirmed | Fit for bounded workflows (intake triage, FAQ, retrieval over an approved knowledge source) with authentication and DLP. Unfit as unsupervised legal advice. Each agent’s knowledge source determines task fit. | Which tasks will a Studio agent perform, on which knowledge source, and who approves publication? | [Copilot Studio security and governance](https://learn.microsoft.com/en-us/microsoft-copilot-studio/security-and-governance); [Secure your Copilot Studio projects](https://learn.microsoft.com/en-us/microsoft-copilot-studio/guidance/sec-gov-phase3) |
| Published channels can talk to clients | Not confirmed | Agents can be published to channels, including unauthenticated web use unless blocked by data policy. That is a client-facing disclosure of whatever the agent retrieves. Unauthenticated agents and most channels can be blocked in a restrictive DLP policy. | Will any agent be client-facing or unauthenticated, and what will we tell clients it can see? | [Secure your Copilot Studio projects](https://learn.microsoft.com/en-us/microsoft-copilot-studio/guidance/sec-gov-phase3); [Copilot Studio security and governance](https://learn.microsoft.com/en-us/microsoft-copilot-studio/security-and-governance) |
| Azure OpenAI and Bing | Public claim only | Generative features are powered by Azure OpenAI Service and Bing Search. Microsoft states prompts/outputs are not used to train, retrain or improve Azure OpenAI foundation models. Other models can be configured; Anthropic in Microsoft Online Services is a separate admin path. | Which model endpoint and Bing setting does each production agent use? | [Move data across regions for Copilots and generative AI](https://learn.microsoft.com/en-us/power-platform/admin/geographical-availability-copilot); [Secure your Copilot Studio projects](https://learn.microsoft.com/en-us/microsoft-copilot-studio/guidance/sec-gov-phase3) |
| Azure OpenAI, Bing, connectors | Public claim only | Azure OpenAI and Bing Search are named for generative features. Connector destinations are additional processors chosen by the maker. Optional Anthropic/OpenAI Copilot subprocessors may apply if those routes are enabled at tenant level. Microsoft Online Services DPA covers the platform; Bing has separate handling when used as search. | List Azure OpenAI region, Bing on/off, and every connector destination for production agents. | [Move data across regions for Copilots and generative AI](https://learn.microsoft.com/en-us/power-platform/admin/geographical-availability-copilot); [Copilot Studio security and governance](https://learn.microsoft.com/en-us/microsoft-copilot-studio/security-and-governance) |
| No training of Azure OpenAI foundation models | Public claim only | When cross-region movement is allowed, Microsoft says it does not use the data to train, retrain or improve Azure OpenAI Service foundation models. Fine-tuning would be a separate Azure Foundry/OpenAI feature, not this Studio default. | Confirm no fine-tune or customer-data training is enabled on the Studio-linked Azure OpenAI resource. | [Move data across regions for Copilots and generative AI](https://learn.microsoft.com/en-us/power-platform/admin/geographical-availability-copilot) |
| Application Insights and maker telemetry | Not confirmed | Azure Monitor Application Insights can be enabled per agent and is DLP-governable. That can send conversation telemetry outside the agent. In-product user feedback was not specified on the pages reviewed. | Is Application Insights on for production agents, and what does it collect? | [Copilot Studio security and governance](https://learn.microsoft.com/en-us/microsoft-copilot-studio/security-and-governance) |
| Geography storage; Bing US; conversation logs unspecified | Not confirmed | Customer data storage follows the environment geography, with possible in-geo replication. Bing search data for generative features is stored in the United States. Default retention of agent transcripts was not numbered on the pages reviewed. | What is transcript/conversation retention in our environment, and can we set 30 days? | [Data locations in Copilot Studio](https://learn.microsoft.com/en-us/microsoft-copilot-studio/data-location); [Move data across regions for Copilots and generative AI](https://learn.microsoft.com/en-us/power-platform/admin/geographical-availability-copilot) |
| Environment offboarding via Power Platform / DPA | Not confirmed | Deletion follows Power Platform environment deletion and the Microsoft DPA. This review did not extract a Studio-specific certified-deletion period for transcripts, connector caches or Bing copies. | On agent or environment deletion, what is removed from Dataverse, Azure OpenAI, Insights and Bing, within how many days? | [Data locations in Copilot Studio](https://learn.microsoft.com/en-us/microsoft-copilot-studio/data-location) |
| Microsoft support plus maker access | Public claim only | Makers and admins with environment rights can see agent configuration and, depending on logging, conversations. Microsoft support follows Power Platform practices. Customer Lockbox eligibility should be confirmed. | Who in the firm can read production transcripts, and is Lockbox on? | [Secure your Copilot Studio projects](https://learn.microsoft.com/en-us/microsoft-copilot-studio/guidance/sec-gov-phase3); [Copilot Studio security and governance](https://learn.microsoft.com/en-us/microsoft-copilot-studio/security-and-governance) |
| DLP, environments, authentication | Public claim only | Data policies can restrict maker/user authentication, knowledge, actions, HTTP, channels, Insights and triggers, and can be applied to one environment, a group or the tenant. Unauthenticated web use can be blocked. Internal agents can be limited to groups. Connections should require strong authentication. | Show the production DLP policy, authentication requirement and who can publish. | [Copilot Studio security and governance](https://learn.microsoft.com/en-us/microsoft-copilot-studio/security-and-governance); [Secure your Copilot Studio projects](https://learn.microsoft.com/en-us/microsoft-copilot-studio/guidance/sec-gov-phase3) |
| Industry-standard encryption claimed | Public claim only | Geographic residency article: data encrypted at rest and in transit with industry-standard protocols. Customer-managed keys via Key Vault are documented for secrets, not clearly for all transcript stores. | Does CMK/Key Vault cover agent transcripts and knowledge indexes in the AU environment? | [Geographic data residency in Copilot Studio](https://learn.microsoft.com/en-us/microsoft-copilot-studio/geo-data-residency); [Secure your Copilot Studio projects](https://learn.microsoft.com/en-us/microsoft-copilot-studio/guidance/sec-gov-phase3) |
| GDPR, EUDB optional, multiple certifications cited | Public claim only | Copilot Studio documents GDPR DSR/DPIA support, EU Data Boundary when billing and environments are in the EU, and 'multiple standards certifications'. Reports were not downloaded. Power Platform is an Azure/Online Service under Microsoft compliance offerings. | Provide current SOC 2 / ISO 27001 scope for Copilot Studio and our AU geography. | [Geographic data residency in Copilot Studio](https://learn.microsoft.com/en-us/microsoft-copilot-studio/geo-data-residency) |
| Microsoft Product Terms and DPA; Bing terms if search on | Public claim only | Platform use is under the Microsoft Customer Agreement / EA, Product Terms and DPA. Cross-region generative features require admin consent to terms of use in the Power Platform admin centre. Bing Search, if enabled, has US processing. Liability follows the Microsoft agreement. | Confirm Copilot Studio is on our DPA and whether Bing consent is recorded for the AU environment. | [Geographic data residency in Copilot Studio](https://learn.microsoft.com/en-us/microsoft-copilot-studio/geo-data-residency); [Move data across regions for Copilots and generative AI](https://learn.microsoft.com/en-us/power-platform/admin/geographical-availability-copilot) |
| AU store; US Bing; OpenAI may be US | Public claim only | Table: Australia-hosted environments send Azure OpenAI traffic in-region or to the United States, and Bing Search data to the United States, when cross-region movement is allowed. Connector destinations add further countries. EUDB does not apply to a typical AU tenant. | With cross-region movement off, which generative features still work, and which countries remain? | [Move data across regions for Copilots and generative AI](https://learn.microsoft.com/en-us/power-platform/admin/geographical-availability-copilot); [Data locations in Copilot Studio](https://learn.microsoft.com/en-us/microsoft-copilot-studio/data-location) |
| Online Services / Power Platform process | Not confirmed | Incidents follow the Microsoft DPA for Online Services. No Studio-specific hour count was extracted. A credit-exhaustion outage of a client-facing agent is an availability incident as well as a security one. | Within how many hours are we notified of a Studio or connector incident affecting client data? | [Geographic data residency in Copilot Studio](https://learn.microsoft.com/en-us/microsoft-copilot-studio/geo-data-residency) |
| GA generative features on by default | Not confirmed | Generally available Copilots and generative AI features are turned on by default; cross-region movement may be required to use all of them. Makers can add connectors after go-live unless DLP blocks them. Capacity-pack enforcement can disable agents without a security change. | Who approves new connectors, channels or GenAI features, and what is the change window? | [Move data across regions for Copilots and generative AI](https://learn.microsoft.com/en-us/power-platform/admin/geographical-availability-copilot); [Secure your Copilot Studio projects](https://learn.microsoft.com/en-us/microsoft-copilot-studio/guidance/sec-gov-phase3) |
| Export the agent and environment data | Not confirmed | Implementation guidance includes lifecycle monitoring and rollback. No public bulk-export format or certified deletion of transcripts, knowledge indexes and Bing copies was found. | How do we export agent definitions, transcripts and knowledge on exit, and when are remaining copies deleted? | [Secure your Copilot Studio projects](https://learn.microsoft.com/en-us/microsoft-copilot-studio/guidance/sec-gov-phase3) |
| Maker-chosen destinations; DLP is the control | Not confirmed | The agent maker is responsible for destination data flow. Admins can review connector dependencies before deployment and restrict individual connectors in a data policy. HTTP requests and skills are separate controls. VNet support can keep some traffic private. | Which connectors are allowed in production, and how do we block new ones without a ticket? | [Copilot Studio security and governance](https://learn.microsoft.com/en-us/microsoft-copilot-studio/security-and-governance); [Secure your Copilot Studio projects](https://learn.microsoft.com/en-us/microsoft-copilot-studio/guidance/sec-gov-phase3) |
| Bing Search; US processing; admin consent | Public claim only | Bing Search is a named generative-AI dependency. For Australia-hosted environments, Bing data is stored and processed in the United States. Admins consent to Bing (with cross-region movement and Microsoft 365 services) in the Power Platform admin centre. Turning off Bing does not disable all Copilot features. | Is Bing Search on for the production environment, and can agents still meet the use case with it off? | [Move data across regions for Copilots and generative AI](https://learn.microsoft.com/en-us/power-platform/admin/geographical-availability-copilot) |
| Actions, HTTP, triggers, unauthenticated channels | Not confirmed | Agents can call actions, connectors, skills, HTTP and triggers. Unauthenticated web channels and most connectors can be blocked by DLP. Publishing of GenAI-powered agents can be disabled tenant-wide. There is no described global kill-switch beyond unpublishing, disabling GenAI, or exhausting/removing credits. | Which actions can run without a named approver, and how do we unpublish all production agents immediately? | [Copilot Studio security and governance](https://learn.microsoft.com/en-us/microsoft-copilot-studio/security-and-governance); [Secure your Copilot Studio projects](https://learn.microsoft.com/en-us/microsoft-copilot-studio/guidance/sec-gov-phase3) |
| Maker and user; not a legal sign-off product | Not confirmed | Guidance is to evaluate and roll back agents, require authentication, and limit internal agents to groups. No clause requires a qualified lawyer to approve each agent response. Client-facing agents need a human-review design of the firm's own making. | What human review sits in front of any client-visible or file-writing action? | [Secure your Copilot Studio projects](https://learn.microsoft.com/en-us/microsoft-copilot-studio/guidance/sec-gov-phase3) |

## Notes

AU environment storage is real (Australia East/Southeast). Generative inference for AU may still go to US Azure OpenAI, and Bing Search is US. Cross-region movement is the control. Assess each published agent, not only the platform. Credit exhaustion can take a client-facing agent offline.

## Sources

- [Geographic data residency in Copilot Studio](https://learn.microsoft.com/en-us/microsoft-copilot-studio/geo-data-residency) (checked 2026-09-21)
- [Copilot Studio security and governance](https://learn.microsoft.com/en-us/microsoft-copilot-studio/security-and-governance) (checked 2026-09-21)
- [Data locations in Copilot Studio](https://learn.microsoft.com/en-us/microsoft-copilot-studio/data-location) (checked 2026-09-21)
- [Move data across regions for Copilots and generative AI](https://learn.microsoft.com/en-us/power-platform/admin/geographical-availability-copilot) (checked 2026-09-21)
- [Secure your Copilot Studio projects](https://learn.microsoft.com/en-us/microsoft-copilot-studio/guidance/sec-gov-phase3) (checked 2026-09-21)
- [Microsoft Copilot Studio pricing](https://www.microsoft.com/en-us/microsoft-365-copilot/pricing/copilot-studio) (checked 2026-09-21)

A product profile is research to support questions. It does not approve a product for any firm. Public product information supports questions; it does not approve a product for your firm. Verify the exact plan, settings and signed terms.