Copilot Studio: persistent agents in private preview, Work IQ generally available

These distinctions matter when planning a project. A team should confirm the account’s eligibility and access conditions before making a preview feature essential to daily operations. A mention in a product recap does not by itself establish that the feature is available to every organization or suitable for its proposed launch schedule.

For a smaller business, an agent’s usefulness in customer follow-up depends on the work it can resume correctly. Consider a fictional quote request that arrives in the morning and is picked up by a colleague later that afternoon. The underlying record may have changed between the two interactions.

Before piloting CRM and ERP automation, establish which information is authoritative and who may update it. Staff should be able to identify actions already applied, proposals still pending and approvals given by a person. These are acceptance criteria to verify; no test results for the announced features are reported here.

Continuity also requires a clear handover rule. Decide where the agent stops if an instruction is ambiguous, the customer disputes information or a connector becomes unavailable. The responsible employee needs enough information to resume the case without interpreting an entire conversation or guessing whether a proposed change was actually applied.

A RAG knowledge base can supply information from internal documents. Work IQ’s general availability does not establish that every user may access every source in the business. Check the permissions planned for the project and inspect the information actually returned in the proposed workflow.

For a custom web application, maintain an inventory linking each selected feature to its exact release stage. Choose a fallback for any preview dependency. A limited pilot can use fictional records to check resumed work, denied access and handover to a person before the team decides whether to expand it.

The practical next step is to confirm access to the intended features and define the expected outcomes for one workflow. That preparation bases the project scope on the account’s actual conditions while keeping private-preview dependencies visible to the people responsible for launch.