{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiclajrn3scmypxfphwbbis5cuiv77p3c3ll2bizhftyf4v36h6xgq",
    "uri": "at://did:plc:xxrzfynfiasdpbxteqxi4jgq/app.bsky.feed.post/3micuro6kson2"
  },
  "description": "Custom domain configuration is no longer required for custom HTML editing in Teams event emails, effective immediately. However, configuring a custom domain is still recommended for better sender identity, email deliverability, and trust, especially for external audiences. Documentation will be u...",
  "path": "/m365-message-center/message/mc1266025/",
  "publishedAt": "2026-03-31T00:00:18.000Z",
  "site": "https://blog.tophhie.cloud",
  "textContent": "We're clarifying our guidance around custom domain configuration for Teams event emails, based on customer feedback and recent questions.\n\nIn a previous Message Center post (MC1234575 and MC1176301), we communicated that configuring a custom domain was required to use custom HTML editing for event emails. Based on customer feedback, this is no longer mandatory effecting immediately.\n\n## When this will happen\n\nEffective immediately\n\n## How this affects your organization\n\nPremium feature of custom HTML editing for Teams Events (Webinar and Townhall) emails is no longer blocked if your tenant does not have a custom domain configured.\n\nYou can continue creating and sending event emails even without configuring a custom domain.\n\nHowever, we still strongly recommend configuring a custom domain for the best and most consistent email experience, especially for events sent to external audiences.\n\n_Why we still recommend configuring a custom domain_\n\nConfiguring a custom domain helps:\n\n  * Provide clearer and more recognizable sender identity for recipients associated to your tenant\n  * Improve email deliverability and reduce the likelihood of messages being flagged or questioned\n  * Create a more trusted experience for attendees receiving event invitations, updates, and reminders\n\n\n\nIf a custom domain is not configured, event-related emails will continue to leverage Microsoft provided domains, which can appear unfamiliar to recipients.\n\n## What you can do to prepare\n\n  * Review your tenant’s domain configuration in Microsoft 365\n  * Consider configuring and validating a custom domain if your organization regularly hosts external or large-scale Teams events\n  * Update internal guidance to reflect that custom domains are recommended, but no longer required, for advanced email customization\n\n\n\n _Documentation updates_\n\nWe are updating our documentation and guidance to clearly reflect:\n\n  * The removal of the custom-domain requirement for custom HTML editing\n  * When and why configuring a custom domain is still recommended\n\n\n\nYou can learn more about managing email communications for Teams events on our learn page.\n\n_We’re listening_\n\nThis update reflects direct customer feedback. We’ll continue monitoring support signals and feedback to further simplify and improve the event email experience.",
  "title": "MC1266025: Update on custom domain guidance for Teams Event emails",
  "updatedAt": "2026-03-31T00:00:18.249Z"
}