Copilot adds Home and Code; Autopilot remains a preview

What changed

Keep private-preview functionality out of promises made to clients or colleagues.

Check Frontier or preview eligibility for each feature. Choose a task with inspectable inputs and outputs, and define who reviews the result before it affects customers or accounts. Keep the current process available during the test, especially for work whose completion depends on connected systems or access permissions.

The announcement describes Home and Code becoming available through the stated rollout, while Autopilot remains a preview with a separate access path. These should remain separate lines in a product-readiness review. An interface for organizing work, a coding capability and a system that can continue acting on a task create different operational and review requirements.

For a marketing team, an initial evaluation might compare preparation and review time on a recurring internal task, using approved data and a clear expected output. Keep any action affecting a customer, account or shared system behind the existing approval process. If access is not yet available, prepare the evaluation criteria without claiming the capability has been tested. A launch announcement can inform the shortlist of tools to evaluate, but it should not replace evidence from the team’s actual workflow.

Why it matters for advertisers

A new workspace and coding surface may change how a team organizes tasks, while an autonomous preview raises different questions about permissions and supervision. Those capabilities need separate evaluations rather than a single claim that work is now automated.