This is a development announcement, not a release. The roadmap entry targets preview availability in December 2026 and general availability in April 2027, for the web platform in the Worldwide Standard Multi-Tenant cloud. Microsoft cautions that roadmap dates are estimates and can change.
What Auto paste is intended to change
The proposed workflow starts with information users have already copied from an external source. Rather than requiring them to isolate and paste each value separately, Auto paste would use AI to identify useful information and match it to Business Central fields.
That is the important distinction: interpreting copied content, rather than simply inserting it into the selected field. Microsoft positions the feature as an extension of Autofill, intended to reduce manual entry across more everyday Business Central workflows.
The potential benefit is straightforward. Less time shuttling values between applications could leave more time for checking the resulting record. Whether that trade-off delivers meaningful savings will depend on mapping accuracy and the effort needed to review or correct the results; the announcement supplies no performance measurements.
Auto paste and existing Autofill are not the same thing
Microsoft Learn already documents Business Central’s Autofill as a production-ready preview. It suggests values while users create or modify records, drawing on Business Central data, AI-generated information and, where enabled, web search. Planned Auto paste instead explicitly starts with copied text or HTML.
Existing Autofill also has defined boundaries: it operates on supported editable fields within FastTabs on card and document pages, including fields added by extensions. It is not a general-purpose assistant for every page or field. Those documented restrictions describe Autofill today, not a confirmed compatibility list for Auto paste.
One particularly useful safeguard in current Autofill is that suggestions are not saved automatically. Users review and accept them, and Microsoft warns that AI suggestions can be incorrect. The Auto paste announcement does not establish whether its eventual review and saving behavior will be identical.
In short, “building on Autofill” provides product context—not permission to assume every existing behavior carries over.
What administrators can prepare now
Business Central already provides a Copilot & agent capabilities page where administrators can inspect available capabilities and activate or deactivate individual features. Microsoft’s configuration documentation also lists user-access controls; existing Autofill requires the Copilot Sys Features permission set or execute permission on system object 9700, Allow Copilot Autofill. These are current Autofill controls, not confirmed Auto paste prerequisites.
For a future Auto paste evaluation, a sensible acceptance checklist would be:
- Mapping accuracy: Does copied information land in the intended fields?
- Ambiguity handling: What happens when the content contains competing values?
- Review controls: Can users inspect and correct mappings before committing changes?
- Data handling: What clipboard content is processed, where, and under which retention rules?
- Workflow coverage: Which pages, fields and languages are explicitly supported?
These are evaluation questions, not announced capabilities. The roadmap description does not settle them.
The practical takeaway is to track Auto paste as a targeted data-entry improvement, not autonomous record creation. Its promise is refreshingly ordinary: fewer repetitive transfers into business forms. The real test will be whether it removes more checking work than it creates.