Microsoft Forms automated email sender domain is changing
- Jul 14
- 2 min read
What and Why:
Microsoft Forms will update the email address used for automated notifications from maccount@microsoft.com to no-reply@forms.mail.microsoft. This email address is used for Microsoft Forms automated emails, including response receipts, email notifications for new responses, and Forms response monitoring updates.
For GCC, GCC High, and DoD environments, admins will now have the option to configure notification emails. These notifications will also use no-reply@forms.mail.microsoft, aligning with Worldwide environments.
Bring your own domain (BYOD) email addresses remain supported when configured by a tenant admin.
Rollout Schedule:
General Availability (Worldwide): Rollout begins in mid-August 2026 and is expected to complete by early September 2026.
General Availability (GCC, GCC High, DoD): Rollout begins in early September 2026 and is expected to complete by mid-September 2026.
Impact on Your Organization:
Who is affected:
Organizations using Microsoft Forms automated email notifications.
Organizations with mail flow rules, mailbox rules, or filtering policies that reference maccount@microsoft.com.
Platforms/Services:
Microsoft Forms
Exchange Online mail flow
Email filtering and anti-spam solutions
What will happen:
Microsoft Forms automated emails will be sent from no-reply@forms.mail.microsoft instead of maccount@microsoft.com.
Response receipts will use the new sender address.
Email notifications for new responses will use the new sender address.
Forms response monitoring updates will use the new sender address.
Admins will be able to configure notification emails that use the new sender address.
Existing mailbox rules, mail flow rules, or filtering policies that reference the previous sender address may no longer function as intended.
Action Required/Recommendations:
Review mail flow rules, mailbox rules, and filtering policies that reference maccount@microsoft.com.
Update any configurations that depend on the previous sender address.
Consider adding no-reply@forms.mail.microsoft to your organization's safe sender or allowed sender lists.
Communicate this change to end users and help desk teams as appropriate.
Review notification features that use this sender address and determine whether configuration changes are needed.
Compliance Considerations:
No compliance considerations identified. Review as appropriate for your organization.
