MC1176301 – M365 Change Digest

One-line summary

From November 17, 2025, Teams Events custom HTML email templates require authenticated, customer-owned sending domains; Microsoft will stop sending these from its default address.

Similar updates

Details

Summary

Starting November 17, 2025, organizations using premium custom HTML templates for Teams Events email notifications must set up and verify their sending domain in Microsoft 365. Without this, custom templates cannot be used, and event emails must originate from an authenticated, customer-owned domain.

Body (from Message Center)

[Introduction]

To improve the security and reliability of event email notifications in Microsoft Teams, we're updating how custom HTML templates are supported. Starting November 17, 2025, organizations using premium custom HTML templates for Teams Events must ensure their sending domain is properly set up and authenticated. This change helps reduce the risk of event emails being flagged as spam or phishing by ensuring they originate from trusted, customer-owned domains.

[When this will happen:]

This change will take effect on November 17, 2025.

[How this affects your organization:]

Who is affected:
- Organizations using premium custom HTML templates for Teams Events email notifications.
What will happen:
- Users will no longer be able to edit or use custom HTML templates for Teams Events unless the sending domain is properly set up and verified.
- Event emails must be sent from a domain authenticated within your tenant.
- Microsoft will no longer send these notifications from its default external email address for these templates.

[What you can do to prepare:]

Set up and verify your organization's domain in Microsoft 365 tenant settings.
Configure the domain to allow Microsoft products to send notifications from your organization’s email address.
This is a one-time setup and must be completed before November 17, 2025.
Refer to the official guidance for step-by-step instructions: Select domain to use for email from Microsoft 365 products

[Compliance considerations:]

No compliance considerations identified, review as appropriate for your organization.

Raw JSON (for debugging)

Expand/collapse the full payload below.

Show/hide raw

{
  "snapshot_item": {
    "action_required_by": "2025-11-17T08:00:00Z",
    "ai_action_required_by": null,
    "ai_actions": [
      "Set up and verify your organization\u0027s sending domain",
      "Configure domain for Microsoft 365 email notifications"
    ],
    "ai_master_tags": [
      "User",
      "Admin",
      "Security"
    ],
    "ai_model": "gpt-4.1",
    "ai_summary": "From November 17, 2025, Teams Events custom HTML email templates require authenticated, customer-owned sending domains; Microsoft will stop sending these from its default address.",
    "ai_topics": [
      "Teams"
    ],
    "category": "planForChange",
    "details_map": {
      "Summary": "Starting November 17, 2025, organizations using premium custom HTML templates for Teams Events email notifications must set up and verify their sending domain in Microsoft 365. Without this, custom templates cannot be used, and event emails must originate from an authenticated, customer-owned domain."
    },
    "id": "MC1176301",
    "importance": 5,
    "is_major_change": true,
    "last_modified": "2025-10-20T18:37:45Z",
    "ms_products": [
      "Teams"
    ],
    "platforms": null,
    "roadmap_ids": [],
    "services": [
      "Microsoft Teams"
    ],
    "severity": "normal",
    "tags": [
      "User impact",
      "Admin impact"
    ],
    "title": "Action Required \u2013 Domain Setup for Custom HTML Templates in Teams Events Email Notifications"
  }
}