Microsoft has quietly signaled that Edge will soon handle a far more personal category of data. A new entry on the Microsoft 365 Roadmap shows the browser gaining the ability to autofill passport numbers, driver’s license details, and other identity-document fields, with general availability pencilled in for September 2026.

Roadmap ID 554938, first spotted this week, describes a feature that “expands Autofill beyond saved addresses” to include “passports, driver’s licenses, and other specialized document forms.” The entry is currently marked “in development,” and as with all roadmap items, dates and functionality remain aspirational until the bits ship.

What’s actually changing under the hood

Edge’s current Autofill already stores names, postal addresses, email addresses, and payment methods. That data lives inside the browser’s Addresses and more settings and gets injected into standard HTML form fields. The new work, however, is about recognizing a wider universe of non-standard forms — the kind peppered across airline check-in portals, visa application sites, and state motor vehicle departments.

Instead of just matching fields named “first-name” or “street-address,” the updated autofill engine learns to detect separate slots for document type, issuing country, number, and expiration date. Microsoft hasn’t said whether it will create a new settings pane for these documents or cram them into the existing address manager. The roadmap hints only that the capability “appears intended to recognize a wider range of form structures and document-specific fields.”

It’s a logical next step for a browser that already leans heavily on machine learning to suggest completions. Microsoft’s EdgeAutofillMlEnabled policy, introduced in late 2023, already lets IT admins switch off ML-powered suggestions for traditional fields. The new document autofill could piggyback on that same intelligence layer, though no policy specific to passports or licenses has been published yet.

What it means for you — and why you should pause before clicking “save”

For everyday users

The upside is speed. Anyone who has ever booked an international flight, submitted an ESTA application, or renewed a car registration knows the pain of hunting down a passport or fishing a license from a wallet while a session timer ticks down. Edge could shave minutes off each transaction.

The downside is the nature of the data. A stored postal address is practically public. A passport number is a cornerstone of identity theft. Store it in a browser, and it becomes accessible to:
- Any website that can convince the browser to autofill it (a risk if a site is compromised or malicious).
- Anyone with physical access to your unlocked device.
- The browser’s sync engine, which by default shuttles saved data across all your signed-in devices — potentially including a machine you share or one that has weaker security.

Microsoft’s roadmap makes no mention of extra authentication. Passwords can be guarded behind a primary password or Windows Hello; saved addresses cannot. If document data inherits the same protection level as addresses, you’ll want to think twice before storing it on a family PC or a work-issued laptop you don’t control.

For IT professionals and admins

The first task is finding out exactly where the data lives. Microsoft’s existing enterprise documentation for Edge Autofill doesn’t cover document-type fields, so admins should anticipate a new policy — or at least an extension of the EdgeAutofillMlEnabled toggle — to turn off the feature entirely. Until that appears, treat the September 2026 target as a signal to start a security review, not to flip a switch.

Key questions that need answers before a rollout:
- Does the data sync to the user’s Microsoft account, and can sync be scoped (e.g., blocked for document categories only)?
- Is there a dedicated Group Policy to disable or limit document autofill?
- Can the feature be turned off separately from regular address autofill?
- How does the browser protect the stored data at rest and in transit?

Microsoft has a history of phased rollouts for Edge features. Even after the code lands in the Stable channel, it may be gated behind an experiment flag, giving admins additional lead time. Your first concrete signal will likely be an Insider build with a settings UI and a corresponding configuration service provider or policy entry.

The long road to supercharged autofill

Browser autofill wasn’t always contentious. Early versions simply saved a name and address. Over time, credit card support arrived, followed by password managers that turned browsers into full-blown digital vaults. Each expansion brought new security scrutiny.

Edge’s journey accelerated in 2023 when Microsoft began rolling out “AI-powered autofill” that uses a local ML model to predict form fields more accurately. The EdgeAutofillMlEnabled policy appeared to give enterprises an off switch. The capability now hitting the roadmap is a direct continuation of that pursuit, pushing Edge into document territory that Chrome has experimented with but not released widely.

Why September 2026? The 24-month-plus window suggests a feature that needs substantial engineering: parsing hundreds of government form layouts, ensuring compliance with data-handling regulations across jurisdictions, and building the management stack for IT. It also buys Microsoft time to release a controlled private preview and iterate on feedback before general availability.

What to do right now

For everyone using Edge at home:
- Visit edge://settings/addresses and review what’s already saved. Remove any entries you no longer need.
- Disable sync for addresses if you use Edge on shared computers. Head to edge://settings/profiles/sync and turn off “Addresses and more.”
- When the new feature eventually arrives, don’t reflexively save sensitive documents. If you must use it, consider whether that machine is encrypted, protected by a strong Windows Hello login, and not used by anyone else.

For IT teams:
- Register for the Microsoft 365 Roadmap ID 554938 to receive updates directly.
- Open a review item for the next security steering committee: under what circumstances, if any, would your organization allow passport or license data in browser storage?
- Start testing the existing EdgeAutofillMlEnabled policy in your labs so you’re familiar with its behavior before a broader document-specific policy emerges. The registry path is HKLM\\Software\\Policies\\Microsoft\\Edge with a DWORD value of 0 to disable ML autofill.
- Watch the Microsoft Edge Enterprise documentation portal for a dedicated policy announcement; historically, these arrive a few months before feature rollout.

For developers:
- If you maintain forms that collect identity documents, keep an eye on the WHATWG autofill spec. Browser vendors are slowly standardizing autocomplete values like "passport-number" and "license-number". Edge’s move might accelerate that conversation, so it’s worth updating your fields with semantic autocomplete attributes sooner rather than later.

The outlook: convenience vs. the cost of trust

Microsoft has two years to get this right, but the trust calculus starts now. Passports and driver’s licenses aren’t just strings; they’re keys that unlock everything from bank accounts to border crossings. A single misstep — like syncing a license number to a stolen tablet — could erode confidence in Edge’s entire autofill system.

What to watch next: an Insider Dev or Canary build with a preliminary UI, followed by official documentation on data storage and policy controls. If Microsoft delivers those early and transparently, it stands a good chance of turning a risky-sounding feature into a genuine productivity win. If it ships silently in a routine update, expect a firestorm from privacy advocates and IT admins alike.

For now, the only sensible stance is cautious optimism — and a deliberate finger hovering over the “save” button when September 2026 finally arrives.