From bdc3fad3d1585775e6753885a47a0a91ca469f8b Mon Sep 17 00:00:00 2001 From: Scott Stewart <33209066+Stealth7777@users.noreply.github.com> Date: Mon, 3 Feb 2025 16:56:48 -0800 Subject: [PATCH] Update select-domain-to-use-for-email-from-microsoft-365-products.md Updated to explicitly call out that the tenants own domain would be used as support ask this question even though it is called out multiple times --- ...ect-domain-to-use-for-email-from-microsoft-365-products.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/microsoft-365/admin/email/select-domain-to-use-for-email-from-microsoft-365-products.md b/microsoft-365/admin/email/select-domain-to-use-for-email-from-microsoft-365-products.md index 3e37a28caa7..9b5a80ceb96 100644 --- a/microsoft-365/admin/email/select-domain-to-use-for-email-from-microsoft-365-products.md +++ b/microsoft-365/admin/email/select-domain-to-use-for-email-from-microsoft-365-products.md @@ -42,7 +42,7 @@ Emails sent out to users as they interact with each other and across various pro There are several scenarios where emails are sent from a “no-reply” system-based product account. For example, batched comments, news, digests, and system notification emails are currently sent from a no-reply product address. These include addresses such _no-reply@sharepointonline.com_, _no-reply@planner.com_, _no-reply@project.com_. -The default option is that users receive no-reply emails sent by Microsoft on behalf of your organization. Your users receive these emails as [EXTERNAL] notifications. You can now use a custom domain as the sender of these notifications. Using this feature means that emails are sent from your own Exchange Online instance and they become internal communication. For example, **no-reply@sharepointonline.com [External]** could become **no-reply@contoso.com**, if **Contoso.com** is the selected domain. +The default option is that users receive no-reply emails sent by Microsoft on behalf of your organization (the emails are sent from Microsoft-owned domains. Your users receive these emails as [EXTERNAL] notifications. You can now use a custom domain as the sender of these notifications. Using this feature means that emails are sent from **your own selected domain and Exchange Online instance** and they become internal communication. For example, **no-reply@sharepointonline.com [External]** could become **no-reply@contoso.com**, if **Contoso.com** is the selected domain. > [!NOTE] > Only domains registered within your tenant can be used and ownership must be verified through the existing add domains process within Microsoft 365. Please use the following steps and note the Domain Name System (DNS) records required when configuring a domain for sending email. @@ -93,7 +93,7 @@ Please note that the following products currently support this feature: - Teams > [!NOTE] -> The supported products list will be updated as each product migrates to support the setting and no action will be required as these products onboard to the centralized setting. +> The supported products list will be updated as each product migrates to support the setting and no action will be required as these products onboard to the centralized setting. ## Excluded Scenarios