Email Marketing

How important is the authentication process in email marketing

How important is the authentication process in email marketing

This method of email domain authentication to gain members and understand the policy of this best way 

How important is the authentication process in email marketing
How important is the authentication process in email marketing

Domain authentication is important for two reasons:

  • For  marketing email messages , domain authentication enables recipient email servers to confirm that the address that appears on all of your messages belongs to your organization. The authentication also confirms that your organization has consented to Dynamics 365 Marketing sending messages on its behalf. Messages that fail this test will most likely be filtered away as spam, which can significantly affect your message delivery.
  • For  externally hosted forms , domain authentication confirms that you own the domain, creating an improved trust relationship with your domain. An enhanced trust relationship allows pre-built marketing forms to be populated with data from known contacts.

The primary purpose of domain-email authentications is to detect fraudulent messages and domains, thus preventing spam, phishing or other fraudulent activities. A method called  DomainKeys Identified Mail  (dkim) helps

you make this authentication possible. Domain authentication is performed through an Internet System DSN, and is based on public/private key encryption and signatures.

When you verify the error or transfer a marketing email message to direct mode, the verification system prompts that you use a sender address that identifies the registered and confirmed authentication domain for your organization.

You will receive a warning if you try to send a message containing an address sent from an unregistered domain. You will also receive an error message if you try to send a message that uses an address from a domain registered as affiliated with another organization. You can ignore the warning (but this may reduce the chances that your message can be delivered), but you can’t go live with this error.

To learn more about email marketing and new deliverability, see  Best Practices for Email Marketing . To learn more about embedded forms and prefilling, see  Integrate with landing pages on external websites .

When real-time marketing features are installed, a domain authentication wizard is included for both real-time marketing and outbound marketing. To learn how to use the Real-time Marketing Domain Authentication Wizard, see the Real-time Marketing Domain Authentication article. If real-time marketing is not installed, you must follow the setup below in this article to authenticate domains for use in outbound marketing features.

Authenticated default domain

All new Dynamics 365 Marketing installations by default come with a pre-authenticated sending domain ending with A pre-authenticated domain means you can start sending authenticated emails right away. This domain is only designed for testing or demonstration

purposes because it does not have an email reputation and is not associated with your organization. But you should still set authentication on your actual sending domains immediately so that your authenticated messages show a sender address that recipients will recognize as a sender from your organization.

Authenticating your own domain will allow you to manage your sending reputation and improve brand recognition and delivery results.

When a user creates a new email,  the sender address is  automatically mapped to the email address registered to the user’s account in Dynamics 365 Marketing However, if that email address uses a domain that has not yet been authenticated with DKIM,  the prototype address will be modified  to use a domain Authenticated (email addresses use the form  account-name*@*domain-name).  The resulting  form title will still  show the name of the  user account creating the message, but it will now show  the name of a  DKIM-authenticated domain that’s registered for your Marketing instance (for example,, providing a delivery feature, but it may not be a valid sender address. Users can override this by editing  the return address After the message is created, this will weaken the delivery feature.

Domains that for authentication

Set up as many authenticated domains as you need to cover all the addresses you use in your marketing email messages, as well as all the domains and subdomains where you want to support inline forms with prefilling enabled.

  • When you authenticate an email domain, use the full domain name as it appears in your email addresses. Email addresses take the form  <MailAccount> @ <domain> , so if it’s your email address, the domain you need to authenticate is (and not any other subdomain).
  • When you authenticate a domain to support prefilled forms, each subdomain must be authenticated individually. Even if you have forms on, and, then you must set up a separate domain authentication record for each and specify the full subdomain each time.

Domain Authentication

To set up Dynamics 365 Marketing and DNS to authenticate inline marketing email messages and forms for a specific domain:

  1. Go to  Settings  >  Email Marketing  >  Domain Authentication . A list of existing authenticated domains opens.
  2. On the command bar, select  New  to add a new domain.
  3. A new authenticator domain record is opened. Set the following settings:
    • In the  Domain name field , enter the name of the domain you want to authenticate. This must be a domain that your organization owns, and that you can access through your DNS provider.
    • Enable to send email : Select this check box if you want to authenticate email for this domain using DKIM.
    • Enable to host forms : Select this check box if you want to authenticate marketing forms included in this field for the purpose of supporting pre-population of known contacts. This check box also enables customization of the page on this domain.
  4. From the command bar, select  Save . Dynamics 365 Marketing saves the new record and generates a set of authentication keys for your specified domain. The page reloads to show the new keys. The following is provided:
    • Ownership Authentication Key : Proves that your organization owns the domain.
    • DKIM Email Authentication Keys : Verifies that Dynamics 365 Marketing is authorized to send messages that show your organization’s domain in the sender address.

    التسويق عبر البريد الإلكتروني 1

    1. Contact your DNS provider and tell them that you’d like to create some DNS records for domain and DKIM authentication. They will usually provide you with an online form where you can create DNS records by submitting the  host values  ​​and  the value  for each authentication key generated by Dynamics 365 Marketing, or they may instead ask you to send them these values ​​in an email. The procedure varies by DNS provider, so be sure to follow their instructions.

    Create a CNAME record.

    After entering the Envelope From field, select  Save . The appropriate DNS record values ​​will be generated for you. You can find the record values ​​in the  Encapsulated Key section of .

    Next, you need to create another CNAME record for the envelope domain for validation. Contact your DNS provider and tell them that you want to create another CNAME DNS record with the value taken from the  key segment encapsulated from .

    After the DNS record is created, wait at least 30 minutes before continuing to the last step. DNS servers need some time to populate the newly created DNS records.

    After the DNS record update is complete, select  Update  and then  Confirm . If everything is set up correctly, your domain status in the upper right corner should be changed to  Confirmed , as in the image below.

    authenticate dns update

    After you confirm  the envelope status from  your domain, the sender domain of your envelope will adhere to your envelope settings each time you use the specified domain when sending email messages in Dynamics 365 Marketing.

    Example DNS records for the domain

    This example is valid if you are adding DNS records in the main domain

    txt record
    TXT name: @
    TXT value: d365mktkey=abc123abc123abc123abc123

    Record 1 CNAME
    Host name or Alias: eurkey1._domainkey
    Points to address:

    Record 2 CNAME
    Host name or Alias: eurkey2._domainkey
    Points to address:

    CNAME record 3 (encapsulated from)
    Host name or Alias: bouncing
    Points to address:

    Example DNS records for subdomain

    txt record
    TXT name: promo
    TXT value: d365mktkey=abc234abc234abc234abc234

    Record 1 CNAME
    Host name or Alias:
    Points to address:

    Record 2 CNAME
    Host name or Alias:
    Points to address:

    CNAME record 3 (encapsulated from)
    Host name or Alias: bouncingpromo
    Points to address:

Related Articles