Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update select-domain-to-use-for-email-from-microsoft-365-products.md #13730

Open
wants to merge 1 commit into
base: public
Choose a base branch
from
+2 −2
Open

Update select-domain-to-use-for-email-from-microsoft-365-products.md #13730

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions ...t-365/admin/email/select-domain-to-use-for-email-from-microsoft-365-products.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 [email protected]_, [email protected]_, [email protected]_.

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, **[email protected] [External]** could become **[email protected]**, 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, **[email protected] [External]** could become **[email protected]**, 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.
Expand Down Expand Up @@ -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.

<a name="excludedscenarios"></a>
## Excluded Scenarios
Expand Down