Microsoft Copilot Field Guide
Unfiltered production reference for Microsoft Copilot Studio, M365 Copilot, GitHub Copilot, and absorbed Power Platform ALM as of November 19, 2026: Copilot Managed Runtime GA, Work IQ Action Policies, Copilotforce, Cost Management hard caps, ONLY verified pac copilot CLI commands, real Graph APIs, and GCC High sovereign endpoints.
01 / Verified Production Model Roster (November 19, 2026)
| Model | API ID | Context | Pricing (In / Out / Cached) | Status |
|---|---|---|---|---|
| Copilot Studio Apps & Managed Runtime Dedicated managed runtime hosting standalone Copilot Studio apps outside Teams/M365 chat. | managedapps.cloud.microsoft | Standalone Agent Apps | Copilot Credits / M365 | GA (Ignite Nov 2026) |
| Microsoft IQ & Work IQ Action Policies Fine-grained action guardrails governing what autonomous agents can read or write across Work IQ. | work-iq-action-policies | M365 Tenant Graph | M365 Copilot / Purview | Public Preview (Ignite Nov 2026) |
| Copilotforce (Salesforce Plugin) First-class Salesforce integration exposing 38+ ready-to-run CRM actions and object skills. | copilotforce-38-skills | CRM Integration | Enterprise Add-on | GA (Ignite Nov 2026) |
| Copilot Studio Cost Management Enforces hard monthly cutoff caps; reseller PAYG ships with a 4,000-credit default cap. | M365 Admin > Copilot > Cost Management | FinOps Controls | Hard Monthly Caps | GA (Ignite Nov 2026) |
| Microsoft Entra Agent ID & Purview DLP Dedicated identities for cloud agents plus Purview DLP extending to Copilot and local agents. | entra-agent-id | purview-dlp-copilot | Cross-Tenant IAM & DLP | Entra / Purview E5 | Entra GA · Local DLP Preview Jan 2027 |
| GitHub Copilot Multi-Model Suite Choose Claude Fable 5.2 / 5.5, GPT-6.2, Gemini 4 Neon, or Microsoft's MAI Code 2 per task. | claude-fable-5-2 | 5-5 | gpt-6.2 | gemini-4-neon | mai-code-2 | IDE + Coding Agent | Seat + Premium Requests | GA (Ignite Nov 2026) |
02 / Retirement & Breaking-Change Radar (No Vendor Sugar-Coating)
Legacy standalone AI Builder credit packs and old automation metering cut off on November 1.
The classic wave-based Power Platform Release Planner portal retired on November 15, 2026.
Legacy recent-file grounding calls to /v1.0/me/insights/used are being retired this month.
Frontier Prompt Caching Calculator
The ONLY 6 Real pac copilot Commands (Zero Fabricated Flags)
Standalone Power Platform administration and agent ALM have been absorbed directly into the Copilot Studio + Microsoft IQ + AI at Work operating model. If you automate agent deployments in CI/CD, ignore LLM-hallucinated subcommands like `pac copilot build` or `pac copilot validate` — they do not exist. The Power Platform CLI exposes exactly six verified `pac copilot` subcommands: `create`, `extract-template`, `extract-translation`, `list`, `publish`, and `status`.
- pac copilot list — Enumerate Copilot Studio agents in the active Dataverse environment.
- pac copilot status — Inspect publish/provisioning status for a target bot ID.
- pac copilot create — Scaffold a new agent from a template definition file.
- pac copilot extract-template / extract-translation — Export YAML/template specs and localization strings into Git.
- pac copilot publish — Publish an updated agent definition deterministically from CI/CD.
# 1. Target your environment (GCC High uses *.crm.microsoftdynamics.us)
pac auth create --environment https://contoso-prod.crm.microsoftdynamics.us
# 2. List agents and verify provisioning health
pac copilot list
pac copilot status --bot <BOT_GUID>
# 3. Export source-controlled template + localization bundles
pac copilot extract-template --bot <BOT_GUID> --templateFileName ./agent-template.yaml
pac copilot extract-translation --bot <BOT_GUID> --outputDirectory ./i18n
# 4. Publish cleanly after PR approval (combine with pac solution export/import for ALM)
pac copilot publish --bot <BOT_GUID>Verified Graph Retrieval, Adoption Telemetry & GCC High URLs
Enterprise telemetry and custom grounding break silently when engineers guess Graph paths or US Government cloud domains. Use the exact verified endpoints below — notably, Viva Engage analytics still use the legacy `Yammer` Graph function name, and GCC High Dataverse hosts live under `*.crm.microsoftdynamics.us`.
- Grounding replacement (Nov 2026): POST /v1.0/copilot/retrieval replaces retiring /v1.0/me/insights/used with native SharePoint/Purview ACL trimming.
- M365 Copilot usage telemetry: GET /v1.0/reports/getMicrosoft365CopilotUsageUserDetail(period='D30').
- Viva Engage activity telemetry: GET /v1.0/reports/getYammerActivityUserDetail(period='D30') (do not substitute VivaEngage in the path).
- Sovereign cloud Dataverse URLs: Commercial = *.crm.dynamics.com | GCC High = *.crm.microsoftdynamics.us | DoD = *.crm.appsplatform.us.
# Grounding API (replaces retiring /v1.0/me/insights/used)
POST https://graph.microsoft.com/v1.0/copilot/retrieval
Authorization: Bearer <ENTRA_TOKEN>
Content-Type: application/json
{
"queryString": "Q4 SOC2 vendor exception policy",
"dataSource": "sharePoint",
"maximumNumberOfResults": 5
}
# 30-day M365 Copilot & Viva Engage adoption reports
GET https://graph.microsoft.com/v1.0/reports/getMicrosoft365CopilotUsageUserDetail(period='D30')
GET https://graph.microsoft.com/v1.0/reports/getYammerActivityUserDetail(period='D30')Cost Management Caps, Key Vault Secret References & Entra Agent ID
Unbounded autonomous triggers in Copilot Studio are the #1 cause of surprise Azure invoices, while plaintext Environment Variables are the #1 security audit finding in Power Platform solutions. Lock down both before promoting any agent to production.
- Hard monthly billing caps (Ignite Nov 2026): Configure hard cutoff thresholds in M365 Admin Center → Copilot → Cost Management. Reseller PAYG plans now default to a 4,000-credit cap so runaway loops cannot drain budgets.
- Never store secrets in plaintext Environment Variables: Always configure Dataverse Environment Variables of type Secret pointing to Azure Key Vault secret references backed by Managed Identity / RBAC.
- Identity & DLP: Bind production agents to Microsoft Entra Agent ID (GA), enforce Work IQ Action Policies (Public Preview), and prepare for Purview DLP covering both Copilot and Local Agents (Public Preview Jan 2027).
Honest Trade-Offs: Copilot Studio vs Pro-Code Agents
Copilot Studio is genuinely fast for M365-centric business workflows, especially with Copilot Managed Runtime GA (managedapps.cloud.microsoft) and Copilotforce (38+ Salesforce skills). Know exactly when to stay low-code and when to eject to pro-code.
- Stay in Copilot Studio when: Users already live in Teams/M365/Salesforce, you need turnkey Entra Agent ID + Purview DLP + Work IQ grounding, and business analysts own prompt/topic iteration.
- Eject to Microsoft Foundry / AWS Bedrock / code-first MCP when: You need sub-second latency, custom multi-model routing across GPT-6.2/Claude Fable 5.2/Gemini 4, strict Git-native unit testing, or predictable per-token FinOps instead of stacked Copilot Credit meters.
Frequently Asked Engineering Questions
Why did `pac copilot build` or `pac copilot validate` fail in my pipeline?
Those commands do not exist—they are common AI hallucinations. The only six real pac copilot subcommands are create, extract-template, extract-translation, list, publish, and status. Use pac solution check for static solution validation.
How do I stop autonomous Copilot Studio agents from causing runaway PAYG bills?
Open Microsoft 365 Admin Center → Copilot → Cost Management and set hard monthly cutoff caps per billing policy. Note that reseller PAYG plans also enforce a 4,000-credit default cap unless explicitly raised.
What is the exact Dataverse URL format for GCC High?
GCC High uses *.crm.microsoftdynamics.us (commercial uses *.crm.dynamics.com; DoD uses *.crm.appsplatform.us). Always pair sovereign deployments with Azure Key Vault secret references—never plaintext Environment Variables.
How should teams track Microsoft Copilot & Power Platform roadmap changes now?
The old Power Platform Release Planner retired on November 15, 2026. Track continuous feature rollouts through the AI at Work roadmap or connect your engineering assistants to Microsoft's Release Communications MCP Server.