The planned scope includes Web, Android, and iOS in Worldwide Standard Multi-Tenant environments. That is a release target, not a shipment announcement: Microsoft explicitly describes its roadmap dates as estimates that can change.
What the additional field types change
The roadmap describes a focused improvement: AI-powered suggestions should cover more parts of a form, reducing the entries users still need to complete manually.
Microsoft Learn currently lists text, numeric, choice, and date as supported field types inside apps. It lists lookup support separately for Microsoft Copilot Chat—not for the existing in-app experience. That distinction matters: support in a conversational form does not establish support in the model-driven app itself.
The announced additions are:
- Lookup fields
- Rich text fields
- Multi-select choice fields
The item does not identify supported control configurations, exceptions, or a specific rollout day. Nor does its mobile platform listing establish that every existing web workflow will behave identically on Android and iOS.
The practical interpretation is straightforward: broader field coverage is planned, but makers should wait for implementation documentation before promising compatibility across every form.
What administrators can check now
Microsoft’s existing documentation provides a useful readiness baseline. These are current prerequisites and limitations, not new settings announced by this roadmap item:
- Web apps require the modern, refreshed appearance.
- At least one AI form-fill environment feature setting must be enabled.
- Relevant columns need Allow form fill assistance enabled.
- Power Apps users require a Premium license.
- Column-secured fields remain unsupported.
For administrators, the sensible preparation is to identify which forms would benefit, then verify those prerequisites before testing the new field types when they arrive. A roadmap entry is a planning signal, not an instruction to reconfigure production.
There is also a platform boundary worth retaining: Microsoft’s current prerequisite documentation specifically describes web availability, whereas the forthcoming item names web and mobile platforms.
Suggestions still need a human decision
Microsoft’s responsible-AI FAQ says form-fill suggestions can draw on recent app usage, supplied clipboard content, or uploaded files. Users can accept, reject, or ignore them; unaccepted suggestions are discarded. Microsoft also directs users to check accuracy and appropriateness before accepting anything.
That review requirement becomes particularly important as coverage grows. The useful test is not simply whether more fields receive suggestions, but whether those suggestions reduce correction work. Less typing is welcome; faster acceptance of incorrect data is not.
Bottom line: November 2026 is the target to watch for lookup, rich text, and multi-select choice support in Power Apps model-driven forms. Prepare the relevant apps and columns, but keep rollout expectations separate from confirmed availability—and keep users in charge of what gets accepted.