Microsoft adds domain checks for email fields in model-driven apps
Reviewed by Helen Jones
A preview setting now lets makers turn on smart email validation at both the environment and app level for model-driven apps. The check runs on columns set to the Email data type and rejects entries that fail format rules, have non-existent domains, or use known throwaway addresses. The feature applies before a record is saved. It does not confirm the recipient exists, only that the address looks real enough to accept. Both the environment toggle and the per-app setting must be enabled. The change is limited to Dataverse-backed model-driven apps.
Until now, makers working in Dataverse had to write their own validation or accept whatever text users typed into email fields. Bad addresses only surfaced later during sends or exports. The new toggle moves that check earlier and makes it automatic, but only inside model-driven apps that already sit on Dataverse. Canvas apps on SharePoint lists receive nothing.
Analysis
This is a trap to avoid. Do not start rebuilding your current SharePoint canvas app just to chase a validation feature that only exists in a different architecture. Instead, list every email field your app collects and decide in the next two weeks whether those fields justify moving the data to Dataverse or whether you will keep handling validation yourself with simple Power Fx.
Pulse published by Collab365 Spaces, reviewed by Helen Jones on . Cite as "Microsoft adds domain checks for email fields in model-driven apps", Collab365 Spaces. 1 source referenced.