web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Microsoft Dynamics 365 | Integration, Dataverse...
Suggested answer

Dynamics 365: Exclude internal employees by domain?

(0) ShareShare
ReportReport
Posted on by

We’re using Microsoft Dynamics 365 (CRM) with Exchange/Outlook integration. When employees register for newsletters or events using a company email (e.g., @company.com), a Contact/Lead is created and all Outlook email communication is automatically tracked in CRM—making internal emails visible to everyone, which we must prevent for privacy/compliance.

So the goal is - to decouple Outlook from CRM only for internal mail while keeping normal external tracking.

Our team thought of 2 possible options:
1) complete preventing from being created in the CRM,
or
2) the contact can be deleted immediately after automatic creation. 

So the main question(s):

  • Which settings in Dynamics 365/Exchange/App for Outlook can block tracking of internal (same-domain) emails globally? (e.g., server-side sync rules, org/system email settings, mailbox settings, turning off auto-capture for internal domains, etc.)

  • What’s the recommended way to exclude our domain from contact/lead creation on form submissions—without blocking the submission—(e.g., domain suppression rules in Customer Insights/Journeys, Power Automate/Dataverse flows, or plugins)?

  • If we keep employee records, how do we reliably flag and filter them out of marketing reports/segments and ensure no email messages are synced?

Scale: ~1,800 employees. Thanks for any best practices and/or implementation tips!

 

 


 
Categories:
I have the same question (0)
  • Suggested answer
    Tom_Gioielli Profile Picture
    2,447 Super User 2025 Season 2 on at
    Dynamics 365: Exclude internal employees by domain?
    For the email tracking, sounds like you want to turn of Correlation to prevent the email from automatically tracking when it finds a matching email address.
     
    Open CRM > Advanced Settings > Email Configuration > Email Settings > Configure folder-level tracking and email correlation > disable correlation
     
     
    Now when it comes to the contacts, I think either of your approaches can work.
    A plugin or even a real-time workflow can be run on creation of a contact. If the email address ends with "@yourdomain.com" then it can prevent the creation of the record. This has the benefit of stopping the create process entirely, but basically introduces a bunch of "errors" on create. I would think this would be the preferred option.
     
    For deletion after create, a Power Automate flow would do this easily. Trigger on create of a contact if the email address contains "@yourdomain.com", and delete the record if so. 

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Pallavi Phade – Community Spotlight

We are honored to recognize Pallavi Phade as our Community Spotlight honoree for…

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 77 Super User 2025 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 57 Most Valuable Professional

#3
Anthony Blake Profile Picture

Anthony Blake 43 Super User 2025 Season 2

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans