Edge : AutofillAddressEnabled partially working for logins containing @

Hi Julien PETUAUD-LETANG,

I understand the confusion, but this how Microsoft Edge internally classifies email‑shaped inputs when autofill policies are applied. When AutofillAddressEnabled is disabled, Edge also disables parts of the “addresses & identity” autofill pipeline.

In Edge, email‑formatted strings (containing @) are treated as identity data, not as plain usernames. On some websites, the login “username” field is technically classified as an address/email field by the site’s HTML attributes. Same “email login”, different HTML semantics create different Edge behavior. E.g.

• Meraki and some banking sites use input definitions that Edge classifies under address / identity autofill
• HP DCC uses a login field Edge treats as credentials only, so it still works
• So this is site‑dependent, not random.

Re‑enabling AutofillAddressEnabled restores the identity autofill pipeline, allowing Edge to suggest saved emails and match email‑like usernames again. Unfortunately, there is currently no separate policy to disable ERP address capture while keeping email‑username autocomplete fully intact.

Tl;dr: This happens because some websites expose email logins in a way Edge classifies as address/identity autofill, which is disabled together with AutofillAddressEnabled.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.