Copilot Playbook
Updated November 7, 2026
Managed App Handbook · Chapter 1 of 8

Status, availability and where to find it

What is generally available, in Frontier or preview, who pays, the dates to watch, and where each tool appears.

For makers, developers, admins and owners · 8-minute read · Facts as of 7 November 2026

Chapter 1 of 88-minute readParts 2–3Facts current as of 7 November 2026

Evidence tagsD DocumentedO ObservedC CommunityI Inference

Every claim in this handbook carries a tag, so you can tell documentation from observation from opinion.

  • DDocumented. Documented by Microsoft on Learn, Support, Message center, GitHub or an official blog, as of the dates in Appendix E
  • OObserved. Observed first-hand on 7 November 2026 in a live Copilot Code cloud session: its tools, its sandbox, an example tenant's policy verdicts, and the repository of a production partner-sales app
  • CCommunity. Reported by the community (MVP blogs, forums, videos, GitHub issues) and not confirmed by Microsoft
  • IInference. Inference or recommendation by the author; test it before you rely on it

Part 2

Status right now: Frontier, licenses and dates

  • What it isWhat is generally available, in Frontier or preview, or retiring; the licenses and admin switches each tool needs; who pays; and the key dates.
  • What you doCheck the status board against your tenant, set up spending policies before people start building, and put the dates in section 2.5 in your calendar.
  • Watch outSpending policies grant access as well as budget. App Builder and vibe.powerapps.com retire on 30 November 2026, and Ignite may change details.

Decide this in the setup Step 7: Access and licensing

Everything in this guide sits somewhere between early access and general availability, and the line moves weekly. This is the board as of Saturday 7 November 2026.

The status board on 7 November 2026

Units: release status and the date it took effectSource: section 2.1Evidence D

  • Copilot Cowork (work accounts) Generally availableGenerally available since 16 June 2026
  • Cowork App skill (/app) Frontier previewFrontier preview since mid-September 2026
  • Copilot Code, cloud sessions Frontier previewFrontier preview, rolling out since 21 October 2026
  • Copilot Code, local sessions Frontier previewFrontier preview, off by default
  • Copilot Managed Runtime Public previewPublic preview since 25 September 2026
  • Apps in Copilot Studio Public previewPublic preview, rolling out by region since October 2026
  • App Builder agent and vibe.powerapps.com RetiringRetiring 30 November 2026
Show the data
ItemAs statedUnitEvidencePartSource
Copilot Cowork (work accounts)Generally available since 16 June 2026statusD2 (2.1)Source
Cowork App skill (/app)Frontier preview since mid-September 2026statusD2 (2.1)In the part text
Copilot Code, cloud sessionsFrontier preview, rolling out since 21 October 2026statusD2 (2.1)Source
Copilot Code, local sessionsFrontier preview, off by defaultstatusD2 (2.1)In the part text
Copilot Managed RuntimePublic preview since 25 September 2026statusD2 (2.1)Source
Apps in Copilot StudioPublic preview, rolling out by region since October 2026statusD2 (2.1)Source
App Builder agent and vibe.powerapps.comRetiring 30 November 2026statusD2 (2.1)Source

Dates to watch, June 2026 to March 2027

Units: calendar dates; bars are date rangesSource: section 2.1, section 2.2, section 2.5Evidence D C

Today, 7 NovJun 2026JulAugSepOctNovDecJan 2027FebMarJanuary 2027: Targeted release retiresJan 2027Targeted release retiresJanuary to March 2027: CSP usage billingJan–Mar 2027CSP usage billing15 December 2026: Dev environments suspended15 DecDev environments suspended30 November 2026: App Builder retires30 NovApp Builder retires17 to 20 November 2026: Microsoft Ignite17–20 NovMicrosoft Ignite5 November 2026: SDK repository archived5 NovSDK repository archived4 November 2026: Migrate app opens4 NovMigrate app opens28 October: Frontier license post28 OctFrontier license post21 October 2026: Code rollout begins21 OctCode rollout beginssince October 2026: Studio Apps previewOctStudio Apps preview25 September 2026: Managed Runtime preview25 SepManaged Runtime previewmid-September 2026: App skill in Frontiermid-SepApp skill in Frontier16 June 2026: Cowork generally available16 JunCowork generally available
  1. 16 JunCowork generally available D
  2. mid-SepApp skill in Frontier D
  3. 25 SepManaged Runtime preview D
  4. OctStudio Apps preview D
  5. 21 OctCode rollout begins D
  6. 28 OctFrontier license post D
  7. 4 NovMigrate app opens D
  8. 5 NovSDK repository archived D
  9. Today, 7 NovYou are here
  10. 17–20 NovMicrosoft Ignite D
  11. 30 NovApp Builder retires D
  12. 15 DecDev environments suspended D
  13. Jan–Mar 2027CSP usage billing D
  14. Jan 2027Targeted release retires D

The today line is set when the page is built. Ignite sessions are listed in section 2.5.

Show the data
ItemAs statedUnitEvidencePartSource
Cowork generally available16 June 2026dateD2 (2.1)In the part text
App skill in Frontiermid-September 2026month (mid)D2 (2.1)In the part text
Managed Runtime preview25 September 2026dateD2 (2.1)Source
Studio Apps previewsince October 2026monthD2 (2.1)Source
Code rollout begins21 October 2026dateD2 (2.1)Source
Frontier license post28 OctoberdateD2 (2.2)In the part text
Migrate app opens4 November 2026dateD2 (2.5)Source
SDK repository archived5 November 2026dateD2 (2.5)In the part text
Microsoft Ignite17 to 20 November 2026date rangeD2 (2.5)Source
App Builder retires30 November 2026dateD2 (2.5)Source
Dev environments suspended15 December 2026dateD2 (2.5)In the part text
CSP usage billingJanuary to March 2027month rangeD2 (2.5)In the part text
Targeted release retiresJanuary 2027monthD2 (2.5)In the part text
2.1

The status board

Re-check after Ignite
ProductStatusWhat a builder needsAdmin switch
Copilot Cowork (work accounts)Generally available since 16 June 2026A Microsoft 365 Copilot license plus a spending policy that includes Cowork; usage is billed in Copilot credits, not included in the licenseMicrosoft 365 admin center, Copilot, Cost Management, Configuration, + Add spending policy, scope the users, select Cowork D
Cowork App skill (/app)Frontier preview since mid-September 2026Everything above, plus Frontier membership and a personal developer environmentFrontier enrollment; developer environment assignments in the Power Platform admin center D
Copilot Code, cloud sessionsFrontier preview, rolling out since 21 October 2026A Microsoft 365 Copilot license and a spending policy that includes CodeCopilot Code is gated by a Copilot spending policy that includes Code, plus Frontier membership and, on Windows, the Beta channel. There is no separate Code on/off switch, but your admin has to act; it is not automatic for everyone. D
Copilot Code, local sessionsFrontier preview, off by defaultAs cloud, on the Windows desktop appSet Code execution location to "Cloud and local" in the Microsoft 365 admin center D
Copilot Managed RuntimePublic preview since 25 September 2026Nothing to build; app users need Power Apps Premium or Copilot creditsOn automatically for eligible commercial tenants; creation paths under Apps, Overview, Set up app creation spaces D
Apps in Copilot StudioPublic preview, rolling out by region since October 2026Copilot Studio access; builds bill to the environmentOn by default; an admin can turn it off or scope it to groups with a tenant setting D
App Builder agent and vibe.powerapps.comRetiring 30 November 2026; no new apps since mid-OctoberNothing: migrateFrom 4 November, one-click Migrate app moves screens, navigation and logic into Apps in Copilot Studio only. Moving to Cowork, or anywhere else, is a manual rebuild from the downloaded source. D

2.2

Turning on Frontier

An admin opens the Microsoft 365 admin center, Copilot, Settings, View all, searches for "Frontier" and opens Copilot Frontier, then chooses No access (the default), All users or Specific users. AI administrators, Security administrators and Office Apps administrators can change it, and new features take up to three hours to appear. Users can't enroll themselves. D

  • A 28 October message-center post says a Microsoft 365 Copilot license is no longer needed to enroll users in Frontier, while the Learn page still says it is. It makes no difference for app building, because Cowork and Code still need the license. D
  • Frontier is also gaining previews of Teams, new Outlook for Windows, OneDrive and SharePoint from November, and Targeted release retires in January 2027. D

2.3

Billing is also access control

Re-check after Ignite

The spending policy that includes Cowork or Code is what grants access to it, not only a budget. Microsoft notes that a low credit limit doesn't block access, and that the old Cowork entry under Agents, All Agents no longer controls who can use it. Microsoft's guidance is at least 2,000 credits per user per month for Cowork users. D

ActivityWho paysHow to watch it
Building in CoworkThe builder's Copilot credits, under the Cowork spending policy/cost in the task D
Building in CodeThe builder's Copilot credits, under the Code spending policy, with per-user spend limitsCopilot cost management. A /cost command is not documented for Code I; builders report that it works there C
Building in Copilot StudioThe environment's Copilot Studio billing, from the first draft, set up in the Power Platform admin centerPower Platform admin center
Building with the CLINo license needed, except to run the app locallyNot applicable
Running a managed appEach user: Power Apps Premium, or 0.1 credit per API call (launches, connector reads and writes), plus a per-launch charge whose rate is not published, under a managed-apps spending policy DCopilot, Cost management
Work IQ calls from an appCopilot credits, billed separately even for Premium usersThe same spending policy, and admin billing reports
  • One partner recommends a separate spending policy only for Copilot Managed Runtime, scoped to app users, with "Auto-apply new services" off and a monthly cap with alerts, so a busy month of building can't lock people out of their apps. C
  • Whole-app builds have cost about 670 to 5,400 credits in public reports, far above Microsoft's per-task planning bands of 25 to 200-plus credits. Budget per app. C

2.4

Regions, clouds and languages

  • Cowork is limited to the regions its Anthropic models support; inside the EU Data Boundary only GPT models are offered. D
  • Copilot Managed Runtime is commercial cloud only, and the unified Copilot app isn't supported in special clouds. Community sources cite a roadmap item targeting GCC in November 2026; Microsoft hasn't confirmed it. DC
  • Learn pages disagree on whether Code works in all Copilot languages or only English at this release. Students aren't eligible for Cowork. D

2.5

Dates to watch

Re-check after Ignite
DateWhat happens
4 November 2026One-click Migrate app began moving App Builder apps into Apps in Copilot Studio; moving to Cowork is a manual rebuild D
5 November 2026The original microsoft/Managed-Apps repository was archived; packages are moving to @microsoft/cmr-* names D
17 to 20 November 2026Microsoft Ignite: the keynote (KEY01, 17 November), LAB652 hands-on Cowork, LAB668 Copilot Managed Runtime (runs in a browser, no local setup), BRK201 Home in the Copilot app, BRK267 What's new in Copilot Studio, BRK206 agentic productivity in Microsoft 365 apps, BRK355 Build like a startup, deploy like an enterprise, and a listed BRK203 Copilot Code session DC
30 November 2026App Builder apps stop opening; vibe.powerapps.com retires D
15 December 2026Unmanaged developer environments start being suspended D
January 2027Targeted release retires in favor of Frontier D
January to March 2027Default-on usage-based billing for new Copilot Business purchases through CSP partners D

Part 3

Where to find everything

  • What it isWhich surfaces carry Cowork, the App skill, Code and managed apps: web, Windows, Mac, Teams, Outlook, mobile, the portal and Copilot Studio.
  • What you doUse the table to tell people where to go, and send anyone who loses a link to managedapps.cloud.microsoft.
  • Watch outCode is not in Teams, Outlook or the mobile app, and Mac and mobile details are moving targets.

Decide this in the setup Step 3: People and devices

Both tools live in one app, Microsoft Copilot (formerly the Microsoft 365 Copilot app), but not on every surface that app appears on. The apps you build live somewhere else again.

Which tool is where, surface by tool

Units: availability per surface (yes, partly, not documented, no)Source: section 3.1Evidence D

Swipe the table sideways to see every tool.

SurfaceCoworkCowork App skillCode, cloudCode, localRun a managed app
copilot.cloud.microsoft in a browser Yes Yes Yes No PartlyThrough its link or the portal
m365.cloud.microsoft PartlyRedirects to copilot.cloud.microsoft PartlySame PartlySame No No
Microsoft Copilot desktop app, Windows Yes Yes YesOn the unified app YesWhen an admin enables it; secure local execution needs Windows 11 24H2 Not documented
Microsoft Copilot desktop app, Mac Yes Yes PartlyLearn says yes; the rollout notice lists Windows and web only Not yet Not documented
Teams and Outlook Yes Not documented No No PartlyPost the link; hosting isn't documented
Microsoft Copilot mobile app (iOS, Android) YesWithout the local browser Not listed NoNo mobile app at this release No Not documentedTest in a phone browser before promising it
managedapps.cloud.microsoft No No No No YesThe portal where users find and open apps shared with them
Copilot Studio No PartlyCowork apps can be opened and edited there No No No

Yes Partly or with conditions Not documented, not listed or not yet No

Show the data
SurfaceCoworkCowork App skillCode, cloudCode, localRun a managed app
copilot.cloud.microsoft in a browserYesYesYesNoThrough its link or the portal
m365.cloud.microsoftRedirects to copilot.cloud.microsoftSameSameNoNo
Microsoft Copilot desktop app, WindowsYesYesYes, on the unified appYes, when an admin enables it; secure local execution needs Windows 11 24H2Not documented
Microsoft Copilot desktop app, MacYesYesLearn says yes; the rollout notice lists Windows and web onlyNot yetNot documented
Teams and OutlookYesNot documentedNoNoPost the link; hosting isn't documented
Microsoft Copilot mobile app (iOS, Android)Yes, without the local browserNot listedNo mobile app at this releaseNoNot documented; test in a phone browser before promising it
managedapps.cloud.microsoftNoNoNoNoYes: the portal where users find and open apps shared with them
Copilot StudioNoCowork apps can be opened and edited thereNoNoNo
3.1

Which tool is where

SurfaceCoworkCowork App skillCode, cloudCode, localRun a managed app
copilot.cloud.microsoft in a browserYesYesYesNoThrough its link or the portal
m365.cloud.microsoftRedirects to copilot.cloud.microsoftSameSameNoNo
Microsoft Copilot desktop app, WindowsYesYesYes, on the unified appYes, when an admin enables it; secure local execution needs Windows 11 24H2Not documented
Microsoft Copilot desktop app, MacYesYesLearn says yes; the rollout notice lists Windows and web onlyNot yetNot documented
Teams and OutlookYesNot documentedNoNoPost the link; hosting isn't documented
Microsoft Copilot mobile app (iOS, Android)Yes, without the local browserNot listedNo mobile app at this releaseNoNot documented; test in a phone browser before promising it
managedapps.cloud.microsoftNoNoNoNoYes: the portal where users find and open apps shared with them
Copilot StudioNoCowork apps can be opened and edited thereNoNoNo

Sources: Microsoft Learn and message-center posts as of 7 November 2026. D Treat Mac and mobile details as moving targets.

3.2

Why Code may only appear at copilot.cloud.microsoft/code

This is the most common question from Frontier users, and there are four reasons.

  • Code has exactly one host. It is a tab in the Microsoft Copilot app, alongside Chat and Cowork; open the app and select Code in the tab switcher at the top. Teams, Outlook and the mobile app don't carry it. D
  • The Windows app needs admin preparation. Admins must opt the tenant in to the unified Copilot app rollout and set the app's update channel to Beta (an EdgeUpdate TargetChannel policy). Until both are done, the web is the only way in. D
  • An older desktop build won't show it. The Microsoft 365 Copilot app was renamed Microsoft Copilot; a non-unified build installed earlier has no Code tab. DI
  • Policy and discovery settings decide what you see. With discovery on but no spending policy, you get the Code welcome page but can't use it; with discovery off, the entry point is hidden. Local sessions are off until an admin sets the execution location to cloud and local. D

Going straight to copilot.cloud.microsoft/code works for many Frontier users, but the documented route is the tab switcher. D

3.3

The desktop app

  • Name and install: Microsoft Copilot, from Microsoft's download site or the Microsoft Store; admins can deploy an offline MSI (x64 or ARM64) or a macOS package through device management, or turn off automatic installation through Intune, Configuration Manager or Group Policy. D
  • Requirements: Windows 11 version 22H2 or later and a current EdgeUpdate; Code local sessions need Windows 11 24H2 for secure local execution, and Mac local protection is planned. D
  • First run: Code downloads its components once on first open. D
  • What local adds: Code works in folders on your device, the default location or one you choose, and you can edit generated files directly in code view. Cloud sessions keep the project in an isolated cloud workspace you can reach from any device, and code view is read-only there. D

3.4

Where managed apps open

  • The portal: managedapps.cloud.microsoft lists every app shared with a person, and is the place to send users who lose a link. D
  • The play link: each app runs at play.managedapps.cloud.microsoft/apps/<app-id>; organization links add a sharing id to the address. Links into a specific record or page aren't supported yet. DC
  • Teams: post the link in a channel. A Teams tab, the Microsoft 365 app launcher, pinning and an installable mobile app are not documented. D
  • Embedding: an admin can add a host origin to the frame-ancestors content security rule to embed an app in a custom site or SharePoint page; nothing else is documented. D