Almanac
Microsoft/copilotMicrosoft 365

Consultant KB for the whole Microsoft Copilot estate. Spans Microsoft 365 Copilot, Copilot Studio, the Dynamics 365 Copilots, Power Platform Copilot, Fabric & Power BI Copilot, Copilot in Azure, Windows & consumer Copilot, extensibility & agents, Security Copilot, and GitHub Copilot, plus admin/security and cross-product decision guides. Populated by the daily author agent from Copilot release notes / release plans plus the author's own consultant notes.

copilot/12-copilot-in-azure/feature-copilot-in-azure-overview.md
feature-copilot-in-azure-overview.mdv1 · history
CurrentApplies to AzureUpdated 2 months agoSource techcommunity.microsoft.com ↗

What it does

Copilot in Azure is an AI assistant built into the Azure portal, the Azure mobile app and the CLI. It helps you design, operate, troubleshoot and understand your Azure estate using natural language, grounded in your own resources and your own permissions.

Key facts

  • Went GA on 8 April 2025, after an ungated public preview that started May 2024.
  • Included at no extra cost. There's no separate licence or per-seat charge to turn it on.
  • Answers are scoped to what you can already see: it only touches resources you have access to and honours Azure RBAC, PIM, Azure Policy and resource locks.
  • GA added AI chat streaming, more entry points across the portal, and a cost management skill.
  • Microsoft quotes >99.9% uptime and a >30% response-time improvement over the preview year.
  • Available in 19 languages at GA; the Azure mobile app version is also GA.
  • Newer "Agents (preview)" and observability agent features sit on top of the core assistant and are still maturing.

When to use / skip

Use it when you're navigating an unfamiliar subscription, drafting Resource Graph queries or CLI, or trying to work out why something is broken without hunting through blades. It's a genuine time-saver for the "where is this and what does it do" class of question. Skip it as a system of record for cost or compliance figures, and don't treat its generated scripts as deploy-ready without reading them. It's an assistant, not an authority.

Configuration decisions

  • Decide whether to expose it at all: an org can block access to Copilot in Azure via the tenant setting if policy requires it.
  • Access follows existing RBAC, so there's no new permission model to design, but users still only get useful answers where they have read access.
  • Choose entry points: portal, mobile app and CLI all surface it; standardise on one for your runbooks.
  • If you want the agent/autonomous features, treat those as a separate preview decision, not part of the base rollout.

Gotchas

  • It only knows your tenant through your permissions, so two people asking the same question can get different answers.
  • Non-English support is partial; complex prompts in other languages degrade.
  • Preview features (agents, autonomous operations) carry preview terms and can change or vanish.
  • It doesn't replace reading the docs for exact limits and quotas, it just points you at them faster.

Consultant notes

  • Good first thing to switch on for a client's ops team; the "no extra cost" line makes the pitch easy.
  • Frame it as a query and troubleshooting aid, not an automation engine, so expectations stay sane.
  • Check the tenant's Copilot access setting during a governance review, some orgs disable it by default.
  • Pair it with proper RBAC hygiene, its usefulness is capped by how well access is scoped.

Check the GA feature list before quoting capabilities to a client, Microsoft ships to this one constantly.

Was this accurate?
Related
Copilot in Azure: Capabilities and Guardrails12-copilot-in-azureCustom engine agents04-extensibility-and-agentsAzure AI Foundry Agent Service12-copilot-in-azureCopilot in Dynamics 365 — overview03-dynamics-365-copilotDeclarative agents04-extensibility-and-agentsMicrosoft Security Copilot: Overview07-security-copilot