Availability first: Microsoft announced Home and Code for gradual rollout through the Frontier program, while Autopilot expanded to private preview. These are not features to describe as universally available. Treat this as a readiness and controlled-preview guide.
What Microsoft released
The September 25, 2026 Copilot announcement reorganized the work experience around Home, Code, and Autopilot. Home brings Chat and Cowork together and places Word, Excel, and PowerPoint inside Copilot. Code is a sandboxed, natural-language way to build solutions. Autopilot is a persistent agent that can continue work without a prompt. Microsoft also described Copilot Managed Runtime as preview infrastructure for running code inside the organization’s Microsoft 365 environment.
Prerequisites
- A Microsoft 365 tenant with the Copilot subscription and eligible users.
- A named administrator and a small pilot group; do not begin with every user.
- Clean Entra ID groups, least-privilege access, current SharePoint permissions, and an audit process.
- A documented spending and data-governance decision for agentic or usage-based capabilities.
How to prepare the tenant
Use a dedicated Entra security group containing IT, security, and representative business users. Record who is in the group and what data they can access.
In the Microsoft 365 admin center, check the tenant’s Copilot licensing and Message center. For preview-only features, verify that the tenant and users are eligible for the relevant Microsoft Frontier or private-preview program. Do not use a public URL as proof that a feature is enabled.
Audit overshared SharePoint sites, OneDrive links, Teams membership, and sensitive labels. Copilot respects user permissions; it can nevertheless make existing oversharing easier to discover.
Ask pilot users to summarize approved documents, create a draft, or locate information they already have permission to read. Record accuracy, citations, latency, and any unexpected data surfaced.
Require a separate development environment, code review, named owner, and test data. Treat generated scripts and connectors as untrusted until reviewed. Never connect a first experiment directly to production write operations.
Begin with approval-required actions such as drafting messages or proposing tasks. Defer sending email, changing records, deleting files, or contacting external parties until logging, ownership, rollback, and exception handling are proven.
How users access it
Users do not install a separate desktop package for the cloud Copilot experience. Access depends on the user’s license and the tenant’s rollout or preview eligibility. Tell users where the capability is actually visible in their Microsoft 365 or Copilot app, and provide a fallback workflow for users who are not in the rollout.
Governance checklist
- Assign an owner and backup owner to every agent or generated app.
- Require human approval for external communication and irreversible changes.
- Log prompts, outputs, approvals, connector calls, and failures according to your retention policy.
- Review plugins and connectors centrally; enable only approved business actions.
- Measure useful completion, correction rate, data incidents, and cost—not just usage.
Troubleshooting
If a user cannot see a feature, first check license assignment, preview eligibility, service health, rollout status, and browser/session state. If responses contain unexpected content, stop the pilot action, inspect the user’s underlying permissions and sharing links, and preserve the prompt/output for review. Do not broaden permissions to “fix” a Copilot result.
Sources and rollout notes
This guide reflects Microsoft documentation and release information checked on October 25, 2026. Rollouts can be tenant-, region-, license-, and service-dependent; confirm the feature in your tenant before promising availability.