Skip to content

Commit e9cb4e4

Browse files
Merge branch 'main' into maccruz-uniqueprocess
2 parents 17d1d4f + b42a197 commit e9cb4e4

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

defender-office-365/email-authentication-dkim-configure.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ f1.keywords:
55
ms.author: chrisda
66
author: chrisda
77
manager: deniseb
8-
ms.date: 1/29/2024
8+
ms.date: 04/08/2024
99
audience: ITPro
1010
ms.topic: conceptual
1111

@@ -93,10 +93,10 @@ The basic syntax of the DKIM CNAME records for custom domains that send mail fro
9393

9494
```text
9595
Hostname: selector1._domainkey
96-
Points to address or value: selector1-<CustomDomain>._domainkey.<InitialDomain>
96+
Points to address or value: selector1-<CustomDomain>._domainkey.<InitialDomainPrefix>.n-v1.dkim.mail.microsoft
9797
9898
Hostname: selector2._domainkey
99-
Points to address or value: selector2-<CustomDomain>._domainkey.<InitialDomain>
99+
Points to address or value: selector2-<CustomDomain>._domainkey.<InitialDomainPrefix>.n-v2.dkim.mail.microsoft
100100
```
101101

102102
- In Microsoft 365, two public-private key pairs are generated when DKIM signing using a custom domain or subdomain is enabled. The private keys that are used to sign the message are inaccessible. The CNAME records point to the corresponding public keys that are used to verify the DKIM signature. These records are known as _selectors_.
@@ -109,7 +109,7 @@ Points to address or value: selector2-<CustomDomain>._domainkey.<InitialDomain>
109109

110110
- **\<CustomDomain\>**: The custom domain or subdomain with periods replaced by dashes. For example, `contoso.com` becomes `contoso-com`, or `marketing.contoso.com` becomes `marketing-contoso-com`.
111111

112-
- **\<InitialDomain\>**: The \*.onmicrosoft.com that you used when you enrolled in Microsoft 365 (for example, contoso.onmicrosoft.com).
112+
- **\<InitialDomainPrefix\>**: The custom part of the \*.onmicrosoft.com you used to enroll in Microsoft 365. For example, if you used `contoso.onmicrosoft.com`, the value is `contoso`.
113113

114114
For example, your organization has the following domains in Microsoft 365:
115115

@@ -121,18 +121,18 @@ You need to create two CNAME records in each custom domain, for a total of four
121121
- **CNAME records in the cohovineyard.com domain**:
122122

123123
**Hostname**: `selector1._domainkey`<br>
124-
**Points to address or value**: `selector1-cohovineyard-com._domainkey.cohovineyardandwinery.onmicrosoft.com`
124+
**Points to address or value**: `selector1-cohovineyard-com._domainkey.cohovineyardandwinery.n-v1.dkim.mail.microsoft`
125125

126126
**Hostname**: `selector2._domainkey`<br>
127-
**Points to address or value**: `selector2-cohovineyard-com._domainkey.cohovineyardandwinery.onmicrosoft.com`
127+
**Points to address or value**: `selector2-cohovineyard-com._domainkey.cohovineyardandwinery.n-v2.dkim.mail.microsoft`
128128

129129
- **CNAME records in the cohowinery.com domain**:
130130

131131
**Hostname**: `selector1._domainkey`<br>
132-
**Points to address or value**: `selector1-cohowinery-com._domainkey.cohovineyardandwinery.onmicrosoft.com`
132+
**Points to address or value**: `selector1-cohowinery-com._domainkey.cohovineyardandwinery.n-v1.dkim.mail.microsoft`
133133

134134
**Hostname**: `selector2._domainkey`<br>
135-
**Points to address or value**: `selector2-cohowinery-com._domainkey.cohovineyardandwinery.onmicrosoft.com`
135+
**Points to address or value**: `selector2-cohowinery-com._domainkey.cohovineyardandwinery.n-v2.dkim.mail.microsoft`
136136

137137
## Configure DKIM signing of outbound messages in Microsoft 365
138138

0 commit comments

Comments
 (0)