Skip to content

Commit 62da01c

Browse files
authored
Merge pull request #506 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/defender-docs (branch public)
2 parents 5424aee + 3f42fea commit 62da01c

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -344,7 +344,7 @@ If you'd rather use PowerShell to enable DKIM signing of outbound messages using
344344
5. After a while, return to Exchange Online PowerShell, replace \<Domain\> with the domain that you configured, and run the following command:
345345
346346
```powerShell
347-
Set-DkimConfig -Identity \<Domain\> -Enabled $true [-BodyCanonicalization <Relaxed | Simple>] [-HeaderCanonicalization <Relaxed | Simple>]
347+
Set-DkimSigningConfig -Identity \<Domain\> -Enabled $true [-BodyCanonicalization <Relaxed | Simple>] [-HeaderCanonicalization <Relaxed | Simple>]
348348
```
349349

350350
- The _BodyCanonicalization_ parameter specifies the sensitivity level to changes in the message body:
@@ -357,13 +357,13 @@ If you'd rather use PowerShell to enable DKIM signing of outbound messages using
357357
For example:
358358

359359
```powerShell
360-
Set-DkimConfig -Identity contoso.com -Enabled $true
360+
Set-DkimSigningConfig -Identity contoso.com -Enabled $true
361361
```
362362

363363
Or
364364

365365
```powerShell
366-
Set-DkimConfig -Identity contoso.onmicrosoft.com -Enabled $true
366+
Set-DkimSigningConfig -Identity contoso.onmicrosoft.com -Enabled $true
367367
```
368368

369369
- For a custom domain, if Microsoft 365 is able to detect the CNAME records at the domain registrar, the command runs without error, and the domain is now used to DKIM sign outbound messages from the domain.

0 commit comments

Comments
 (0)