<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>DKIM Archive - MEB-IT | Blog</title>
	<atom:link href="https://blog.meb-it.de/en/tags/dkim/feed/" rel="self" type="application/rss+xml" />
	<link>https://blog.meb-it.de/en/tags/dkim/</link>
	<description>Networking &#124; Security &#124; Cloud</description>
	<lastBuildDate>Fri, 30 Jul 2021 14:51:17 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.2.2</generator>
	<item>
		<title>Howto enable DKIM in Microsoft 365</title>
		<link>https://blog.meb-it.de/en/howto-enable-dkim-in-microsoft-365/</link>
					<comments>https://blog.meb-it.de/en/howto-enable-dkim-in-microsoft-365/#respond</comments>
		
		<dc:creator><![CDATA[Marcel]]></dc:creator>
		<pubDate>Fri, 30 Jul 2021 14:50:24 +0000</pubDate>
				<category><![CDATA[Office365]]></category>
		<category><![CDATA[Powershell]]></category>
		<category><![CDATA[DKIM]]></category>
		<category><![CDATA[M365]]></category>
		<category><![CDATA[Microsoft365]]></category>
		<category><![CDATA[O365]]></category>
		<guid isPermaLink="false">https://blog.meb-it.de/?p=43</guid>

					<description><![CDATA[<p>DKIM (Domain Keys Identified Mail) should always be enabled on all of your domains used for email. If you do not enable DKIM your mails may inadvertently get treated as spam. The following tutorial shows you how to enable DKIM for your sending domain(s) in Microsoft365 / Office365. As the first step we need to [&#8230;]</p>
<p>Der Beitrag <a rel="nofollow" href="https://blog.meb-it.de/en/howto-enable-dkim-in-microsoft-365/">Howto enable DKIM in Microsoft 365</a> erschien zuerst auf <a rel="nofollow" href="https://blog.meb-it.de/en">MEB-IT | Blog</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p>DKIM (Domain Keys Identified Mail) should always be enabled on all of your domains used for email. If you do not enable DKIM your mails may inadvertently get treated as spam. The following tutorial shows you how to enable DKIM for your sending domain(s) in Microsoft365 / Office365.</p>



<p>As the first step we need to connect to our M365 Powershell. The last paragraph in <a href="https://blog.meb-it.de/en/powershell-on-linux/" target="_blank" rel="noreferrer noopener">this article</a> describes how to do this.</p>



<p>The following command shows a comprehensive list of DKIM related information for domain &#8220;domain.com&#8221;:</p>



<pre class="wp-block-code"><code>Get-DkimSigningConfig -Identity domain.com | Format-List</code></pre>



<p>If we just want to check the DKIM status of our domains we can use the following command:</p>



<pre class="wp-block-code"><code>Get-DkimSigningConfig</code></pre>



<figure class="wp-block-image size-large"><img decoding="async" width="1024" height="187" src="https://blog.meb-it.de/wp-content/uploads/2021/07/01-getdkimsigningconfig-1024x187.png" alt="" class="wp-image-49" srcset="https://blog.meb-it.de/wp-content/uploads/2021/07/01-getdkimsigningconfig-1024x187.png 1024w, https://blog.meb-it.de/wp-content/uploads/2021/07/01-getdkimsigningconfig-300x55.png 300w, https://blog.meb-it.de/wp-content/uploads/2021/07/01-getdkimsigningconfig-768x141.png 768w, https://blog.meb-it.de/wp-content/uploads/2021/07/01-getdkimsigningconfig.png 1536w" sizes="(max-width: 1024px) 100vw, 1024px" /><figcaption>cmdlet Get-DkimSigningConfig</figcaption></figure>



<p>My example shows that DKIM is enabled for our Microsoft tenant domain but isn&#8217;t for our primary sending domain. Before we are able to enable DKIM for our sending domain we need to setup DNS records for verification:</p>



<pre class="wp-block-code"><code>Get-DkimSigningConfig -Identity domain.com | Format-List Selector1CNAME, Selector2CNAME</code></pre>



<figure class="wp-block-image size-large"><img decoding="async" loading="lazy" width="1024" height="152" src="https://blog.meb-it.de/wp-content/uploads/2021/07/02-getdkimsigningconfig-1024x152.png" alt="" class="wp-image-50" srcset="https://blog.meb-it.de/wp-content/uploads/2021/07/02-getdkimsigningconfig-1024x152.png 1024w, https://blog.meb-it.de/wp-content/uploads/2021/07/02-getdkimsigningconfig-300x44.png 300w, https://blog.meb-it.de/wp-content/uploads/2021/07/02-getdkimsigningconfig-768x114.png 768w, https://blog.meb-it.de/wp-content/uploads/2021/07/02-getdkimsigningconfig-1536x227.png 1536w, https://blog.meb-it.de/wp-content/uploads/2021/07/02-getdkimsigningconfig.png 1553w" sizes="(max-width: 1024px) 100vw, 1024px" /><figcaption>cmdlet Get-Dkim-SigningConfig</figcaption></figure>



<p>Now we need to set the CNAME records in our dns. Copy selector1 and create a new CNAME entry in your DNS settings. Repeat for selector2 (Destination is just an example, use the output generated in the previous step):</p>



<pre class="wp-block-code"><code>Host: selector1._domainkey
Destination: selector1-domain-com._domainkey.youronmicrosoftdomain.onmicrosoft.com

Host: selector2._domainkey
Destination: selector2-domain-com._domainkey.youronmicrosoftdomain.onmicrosoft.com</code></pre>



<p>At this point we need to wait until the dns records have been propagated. Wait at least 10 &#8211; 15 minutes until you proceed. Chose on of the options below:</p>



<p></p>



<h3 class="wp-block-heading">Option 1: Via Powershell</h3>



<p>Open a Powershell session to your M365 tenant and type the following command:</p>



<pre class="wp-block-code"><code>Set-DkimSigningConfig -Identity domain.com -Enabled $true</code></pre>



<hr class="wp-block-separator"/>



<h3 class="wp-block-heading">Option 2: Via Security Admin center</h3>



<ul><li>Login to M365 Admin center (https://admin.microsoft.com)</li><li>Go to Security Admin center</li><li>Go to Threat management -&gt; Policy</li><li>Click on DKIM</li><li>Click on your domain</li><li>Turn the disabled slider to enabled and save</li></ul>



<hr class="wp-block-separator"/>



<h3 class="wp-block-heading">Option 3: Via old Exchange Admin center</h3>



<ul><li>Login to M365 Admin center (https://admin.microsoft.com)</li><li>Go to Exchange Admin center</li><li>Go to Classic Exchange admin center</li><li>Go to Protection -> dkim</li><li>Double click your sending domain and click on Enable</li></ul>



<p></p>



<p>If you encounter an error in on of the above steps make sure that your DNS records are set properly. You can check the entries with the following command for Linux:</p>



<pre class="wp-block-code"><code>dig selector1._domainkey.domain.com
dig selector2._domainkey.domain.com</code></pre>



<p>The output should include the CNAME entry for selector1/selector2 you created in your domain name settings. If you are using Windows you can use the following cmd command:</p>



<pre class="wp-block-code"><code>nslookup -q=CNAME selector1._domainkey.domain.com
nslookup -q=CNAME selector2._domainkey.domain.com</code></pre>



<p>Both selectors must be correctly set before Microsoft allows you to enable DKIM for your domain. If both entries are correct wait another 15 -30 minutes and try to enable DKIM via one of the above options again.</p>
<p>Der Beitrag <a rel="nofollow" href="https://blog.meb-it.de/en/howto-enable-dkim-in-microsoft-365/">Howto enable DKIM in Microsoft 365</a> erschien zuerst auf <a rel="nofollow" href="https://blog.meb-it.de/en">MEB-IT | Blog</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://blog.meb-it.de/en/howto-enable-dkim-in-microsoft-365/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
