Business Central Unified Copilot Chat Refresh: Access, Permissions and Rollout Status

For administrators, the important distinction is that an automatically enabled interface does not override Chat permissions or existing Copilot governance controls. Microsoft’s configuration documentation still defines capability activation and user access separately.

Availability: launched metadata, historical preview dates​

Roadmap item 573362 lists the web platform, Worldwide Standard Multi-Tenant cloud, a Launched status, and October 2026 dates for both preview and general availability.

Microsoft Learn’s historical release-plan page, updated September 3, 2026, instead lists September 2026 public preview and no general-availability date. Microsoft also says those release plans became historical references when new disclosures moved to the AI at Work roadmap in September 2026.

The distinction matters: October is the roadmap’s stated availability month, not an established date when every tenant received the interface. Separately, Microsoft’s operational chat documentation still calls Chat a production-ready preview, subject to supplemental terms.

What the refresh means—and does not mean​

Microsoft positions consistency as the benefit: users should find it easier to get started and move between Business Central and other Microsoft applications. Those are intended outcomes, not published productivity measurements. The feature description does not establish a new AI model, licensing change, or autonomous agent capability.

Our assessment: familiar controls can make training easier, but a refreshed panel is not evidence of more accurate answers. Treat this as a usability update, not a new set of business permissions.

Administrator checklist: confirm Chat access​

For Business Central online, Microsoft documents these existing checks—not new requirements introduced by the interface refresh:

1. Search for and open Copilot & agent capabilities.
2. Confirm Chat is Active. If inactive, select it and choose Activate.
3. Verify the user has the Copilot Sys Features permission set or execute permission on system object 9690, Allow Copilot Chat.

Two conditional settings deserve attention:

• Allow data movement: If this toggle appears, Copilot requires permission to move data between the environment’s geography and the Azure OpenAI Service geography. Make that decision under organizational policy. If How do I govern my copilot data? appears instead, Microsoft says to skip this task.
• Enable Bing Search: Required for Chat answers about installed add-on apps; it is not a blanket prerequisite for all chat use.

After configuration changes, ask affected users to sign out and sign back in. Microsoft notes that some capability changes require a fresh session. These checks establish access; they do not force delivery of the refreshed interface.

Try the documented chat workflow​

Microsoft’s current instructions describe the existing experience, rather than a verified walkthrough of every refreshed control:

1. Select the Copilot icon in the upper-right corner.
2. Enter a focused question in Ask a question and press Enter.
3. Review the answer and any returned Business Central record or documentation reference.
4. Use a follow-up question to refine the result.

Existing Chat functions include finding records, explaining tasks and fields, and grouping or calculating data to generate an analysis tab. A successful test should therefore produce an appropriate answer, record reference, or analysis result—not merely open the panel.

If answers drift, Microsoft recommends clearer prompts, one question at a time, and a new chat session when changing subjects. Follow-up questions retain conversational context; starting a new session clears recent conversational memory.

The practical takeaway is straightforward: verify access and governance first, then update user guidance around the interface actually present in your environment. A familiar dashboard is welcome—but it should not distract from checking what the assistant returns.