The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Email validation keeps your Microsoft Forms data clean by rejecting typos like gmai.com or missing domains. When you’re collecting leads, support requests, or registrations, proper validation also reduces downstream errors in CRM, email automations, and reporting.
This updated guide focuses on the practical reality of Microsoft Forms: you can’t run custom scripts inside Forms, but you can use answer validation with Regular expression for Text questions. Where Forms falls short, you can add server-side enforcement using Power Automate.
As an Amazon Associate I earn from qualifying purchases.
Why email validation matters in Microsoft Forms
Bad email addresses cause avoidable work: bounced messages, broken workflows, and “duplicate” contacts created from one-character differences. Email validation won’t be perfect, but it catches the mistakes that happen most often.
- Higher deliverability: fewer typos mean fewer bounces and spam-like patterns.
- Cleaner automation: Power Automate and integrations rely on predictable formats.
- Lower support load: you can immediately prompt respondents to correct errors.
Prerequisites and what Microsoft Forms can (and can’t) validate
To add validation in Microsoft Forms, you need a Forms question that supports answer validation rules. In practice, this means you’ll typically validate Text questions with a regex pattern.
What works well
- Text question with Answer validation using Regular expression
- Custom error messages that explain the expected format
- Optional domain restrictions (work emails only)
What doesn’t work the way people expect
- Forms can’t truly verify deliverability (no way to confirm an address exists).
- Forms can’t validate “real-time” against an SMTP server or a company directory.
- Email validation via regex can be strict and reject edge-case valid addresses, depending on how you write the pattern.
Method 1: Add email validation to a Text question using Regular expression
This is the most direct method. You’ll add a Text question, then set its answer validation rule to a regex that matches email addresses.
Step-by-step (with exact UI labels)
- Open Microsoft Forms and edit your form.
- Click + Add new and choose Text.
- Enter your question prompt, for example: Work email address.
- Click the question’s More options (or the ellipsis
…), then choose Answer validation. Depending on your tenant/UI, the option may appear directly in the question settings. - Set Answer validation to Regular expression.
- Paste an email regex (see next section).
- Set an Error message, for example: Please enter a valid email address like [email protected].
- Save the form and test it by previewing and submitting both valid and invalid inputs.
Use a tested email regex (copy/paste)
Forms regex behavior can differ slightly from other tools, so use a practical pattern that catches common mistakes without trying to perfectly implement the full RFC specification.
Paste this into the Regular expression field:
^[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Za-z]{2,}$
This pattern rejects missing @, missing dots in the domain, and most obvious typos.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsOptional: tighten the rules to match your requirements
If you want to reduce acceptance of unusual formats (for example, forcing a longer top-level domain), modify the last part [A-Za-z]{2,} to your needs.
- Require at least 3-letter TLD:
\.[A-Za-z]{3,}$ - Require at least one dot in domain: the base regex already does via
\.[A-Za-z] - Allow plus addressing: included via
%+-in the local part
Method 2: Validate specific domains (work email only)
If you’re collecting company-only emails, use a domain-restricted regex. This prevents submissions like [email protected] when you only want [email protected].
Examples: allow only microsoft.com, example.com, or multiple domains
Single allowed domain:
^[A-Za-z0-9._%+-]+@microsoft\.com$
Another single allowed domain:
^[A-Za-z0-9._%+-]+@example\.com$
Allow multiple domains:
^[A-Za-z0-9._%+-]+@(example\.com|microsoft\.com|yourdomain\.org)$
Allow subdomains too (e.g., [email protected]):
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall^[A-Za-z0-9._%+-]+@([A-Za-z0-9-]+\.)*example\.com$
Method 3: Validate multiple emails in one response (semicolon/comma separated)
Sometimes forms collect a list of emails (e.g., shared inboxes or team members). A single regex can validate a comma-separated or semicolon-separated list, but keep the rule readable for maintainers.
Common patterns and rules
Comma-separated list:
^[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Za-z]{2,}(\s,\s[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Za-z]{2,})*$
Semicolon-separated list:
^[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Za-z]{2,}(\s;\s[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Za-z]{2,})*$
Error message that reduces confusion: Use something like Enter one or more emails separated by commas or semicolons (e.g., [email protected], [email protected]).
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Method 4: Enforce email validation at submission time with Power Automate
Client-side validation in Forms improves UX, but it can’t guarantee deliverability and it can be bypassed if someone uses an automation path. If your process requires stronger enforcement, pair Forms with a Power Automate flow.
Flow overview
- Create a new flow in Power Automate using a trigger like When a new response is submitted for Microsoft Forms.
- Read the email field from the response.
- Validate it using regex in the flow (or use built-in validation actions if available in your environment).
- Handle failures: notify you, store the invalid response to a separate location, or mark it in a status system.
How to block bad submissions vs. notify admins
Power Automate can’t retroactively stop the response from being submitted (Forms already accepted it), but you have practical options:
- Notify admins: send an email or Teams message to request correction.
- Quarantine: route valid vs. invalid responses to different SharePoint lists, Dataverse tables, or CRM records.
- Secondary validation gate: only trigger downstream automations for responses that pass.
If you need deliverability checks (DNS MX records, SMTP validation), you typically call an external service (via HTTP action) and store the result.
Common mistakes and gotchas
- Forgetting anchors: Always use
^and$so Forms doesn’t accept partial matches. - Overly strict regex: The “perfect email regex” often rejects valid but uncommon addresses. Start practical.
- Unescaped dots: In regex,
.means any character—escape it like\.com. - Whitespace issues: Tell users to avoid leading/trailing spaces. If your regex is strict, space will fail validation.
- Domain restrictions too narrow: If you only allow
example\.com, addresses like[email protected]will fail unless you include the optional subdomain pattern.
Troubleshooting: When the validation fails or behaves oddly
If respondents can’t submit even valid emails, or invalid emails slip through, go through this checklist.
Recommended Free Tools
1) Test the regex with the same input Forms uses
Forms may treat the entire response string literally. Confirm the exact characters being entered (no accidental spaces, full-width characters, or copy/paste formatting).
2) Confirm you selected the right question type
- Email regex validation applies to Text questions.
- Choice questions require different logic (and aren’t ideal for email formatting checks).
3) Try a simpler pattern to isolate the issue
If you used a complex domain or multi-email regex, temporarily replace it with the base email regex:
^[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Za-z]{2,}$
Once that works, reintroduce domain restriction or list support.
4) Check for UI settings conflicts
- Make sure the question isn’t marked as optional when you expect it to be required.
- Verify you actually clicked Save or published changes before testing.
5) If Forms won’t allow the rule you want, use Power Automate
If your validation needs go beyond regex (for example, MX record checks or directory validation), implement server-side logic in Power Automate and gate downstream actions there.
Alternatives and design choices
Sometimes the best approach isn’t “perfect validation”—it’s good UX and clean data handling.
Use “required” plus a friendly error message
Turn on required validation for the question itself and use a regex error message that points to the expected format (e.g., [email protected]). This reduces frustration compared to generic “invalid input” errors.
Collect work email and personal email separately
If you accept both, use two separate questions, each with its own regex rule (or no domain restriction). This keeps the user experience clear.
Prefer Power Automate for “hard” validation
For critical workflows, use Forms validation for quick feedback, then enforce the stricter rules in your automation flow.
Frequently Asked Questions
Can Microsoft Forms validate email addresses without regex?
Forms doesn’t provide a dedicated “email format” validator in the same way it might for other field types. The most reliable built-in option is using Answer validation with Regular expression on a Text question.
Will the regex reject valid emails like [email protected]?
The provided base regex includes plus addressing via %+-, so [email protected] should pass. If you use a custom “tight” pattern, confirm it still allows plus signs if your users rely on them.
Why do some real emails fail validation?
RFC-compliant emails include edge cases that most practical regex patterns can’t represent safely. If you control the data source (for example, internal users), domain restrictions can be more useful than trying to accept every theoretical valid format.
Can Forms verify that an email actually exists?
No. Forms can validate formatting, not deliverability. For existence checks, use an external service via Power Automate (for example, MX lookup or SMTP verification) and store the result.
How do I let users type multiple emails?
Use a multi-email regex for comma- or semicolon-separated input and provide a clear error message with examples. Alternatively, create multiple email questions with separate validation if you need strict structure.
Bottom Line
If you just need to stop obvious typos, the regex-based approach in Microsoft Forms is the fastest win: add a Text question, set Answer validation to Regular expression, and use a solid pattern like ^[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\.[A-Za-z]{2,}$.
When you need stronger guarantees (deliverability, MX checks, directory validation, or workflow gating), pair Forms with Power Automate so automation only runs for responses that pass your stricter rules.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
