<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Microsoft 365 on justinverstijnen.nl</title><link>https://justinverstijnen.nl/categories/microsoft-365/</link><description>Recent content in Microsoft 365 on justinverstijnen.nl</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 18 Apr 2026 14:32:09 +0200</lastBuildDate><atom:link href="https://justinverstijnen.nl/categories/microsoft-365/index.xml" rel="self" type="application/rss+xml"/><item><title>Encrypt your Microsoft 365 emails with S/MIME</title><link>https://justinverstijnen.nl/encrypt-your-microsoft-365-emails-with-s-mime/</link><pubDate>Sun, 05 Apr 2026 00:00:00 +0000</pubDate><guid>https://justinverstijnen.nl/encrypt-your-microsoft-365-emails-with-s-mime/</guid><description>&lt;p&gt;A great way to encrypt your Microsoft 365 outbound emails using a similar technique as SSL is to use S/MIME. In this guide I will show you how to get certificates and configure S/MIME for your users.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="requirements"&gt;Requirements&lt;a class="td-heading-self-link" href="#requirements" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Around 30 minutes of your time&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.9.0"&gt;Exchange Online Powershell module&lt;/a&gt; installed&lt;/li&gt;
&lt;li&gt;S/MIME certificate for your mailbox&lt;/li&gt;
&lt;li&gt;Microsoft 365 tenant/mailbox to configure S/MIME&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h2 id="smime-explained"&gt;S/MIME explained&lt;a class="td-heading-self-link" href="#smime-explained" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;S/MIME means Secure / Multipurpose Internet Mail Extensions. It’s an email security standard defined by the Internet Engineering Task Force which allows you to encrypt your email messages and attachments sent. In simple terms:&lt;/p&gt;</description></item><item><title>Getting started with Microsoft 365 Backup</title><link>https://justinverstijnen.nl/getting-started-with-microsoft-365-backup/</link><pubDate>Fri, 03 Apr 2026 00:00:00 +0000</pubDate><guid>https://justinverstijnen.nl/getting-started-with-microsoft-365-backup/</guid><description>&lt;h2 id="requirements"&gt;Requirements&lt;a class="td-heading-self-link" href="#requirements" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;A Microsoft 365 environment with Global Administrator permissions&lt;/li&gt;
&lt;li&gt;An Azure Subscription with PAYG capabilities&lt;/li&gt;
&lt;li&gt;Around 30 minutes of your time&lt;/li&gt;
&lt;li&gt;Basic knowledge of Microsoft 365&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h2 id="what-is-microsoft-365-backup"&gt;What is Microsoft 365 Backup?&lt;a class="td-heading-self-link" href="#what-is-microsoft-365-backup" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Microsoft 365 Backup is an integrated solution of Microsoft to backup Microsoft 365 items. This applies to these items:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Exchange Mailboxes&lt;/li&gt;
&lt;li&gt;OneDrive accounts&lt;/li&gt;
&lt;li&gt;SharePoint sites/Teams&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Microsoft 365 Backup can be used to extend the retention period of certain data. By default, spaces like SharePoint sites have a retention of 93 days if you count the recycle bin and versioning. But this is not really a backup, only some techniques to quicky restore a single file or folder. This doesn&amp;rsquo;t include things like permissions, which Microsoft 365 Backup does.&lt;/p&gt;</description></item><item><title>What is MTA-STS and how to use it to protect your email flow</title><link>https://justinverstijnen.nl/what-is-mta-sts-and-how-to-protect-your-email-flow/</link><pubDate>Thu, 08 Jan 2026 00:00:00 +0000</pubDate><guid>https://justinverstijnen.nl/what-is-mta-sts-and-how-to-protect-your-email-flow/</guid><description>&lt;h2 id="requirements"&gt;Requirements&lt;a class="td-heading-self-link" href="#requirements" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Around 30 minutes of your time&lt;/li&gt;
&lt;li&gt;Access to your domains&amp;rsquo; DNS hosting to create DNS records&lt;/li&gt;
&lt;li&gt;An Azure Subscription if you want to publish your policy with a Static Web App
&lt;ul&gt;
&lt;li&gt;A Github account if you use this option&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;An Azure Subscription if you want to publish your policy with a Function App&lt;/li&gt;
&lt;li&gt;Basic knowledge of DNS records&lt;/li&gt;
&lt;li&gt;Basic knowledge of Email security&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h2 id="mta-sts-versus-smtp-dane"&gt;MTA-STS versus SMTP DANE&lt;a class="td-heading-self-link" href="#mta-sts-versus-smtp-dane" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;MTA-STS overlaps with the &lt;a href="https://justinverstijnen.nl/configure-dnssec-and-smtp-dane-with-exchange-online-microsoft-365/"&gt;newer SMTP DANE&lt;/a&gt; option, and they both help securing your email flow but each in its own manner. Some differences:&lt;/p&gt;</description></item><item><title>Disable users' self service license trials</title><link>https://justinverstijnen.nl/disable-users-self-service-license-trials/</link><pubDate>Thu, 04 Dec 2025 00:00:00 +0000</pubDate><guid>https://justinverstijnen.nl/disable-users-self-service-license-trials/</guid><description>&lt;p&gt;&lt;img src="https://sajvwebsiteblobstorage.blob.core.windows.net/blog/disable-users-self-service-license-trials-5454/jv-media-5454-b2e8595ef8fb.png" alt=""&gt;&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="why-should-you-disable-trial-licenses"&gt;Why should you disable trial licenses?&lt;a class="td-heading-self-link" href="#why-should-you-disable-trial-licenses" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;You can disable self service trial licenses if you want to avoid users to use un-accepted apps. This could result in shadow-it happening in your environment.&lt;/p&gt;
&lt;p&gt;Let&amp;rsquo;s say, your company uses Zoom to call with each other, and users are starting to use Microsoft Teams. Teams then is an application not accepted by your organization and users then should not be able to use it. If you give them the possibility, they will. This all of course assuming you don&amp;rsquo;t have paid licenses for Microsoft Teams.&lt;/p&gt;</description></item><item><title>Enhance email security with SPF/DKIM/DMARC</title><link>https://justinverstijnen.nl/enhance-email-security-with-spf-dkim-dmarc/</link><pubDate>Mon, 16 Jun 2025 00:00:00 +0000</pubDate><guid>https://justinverstijnen.nl/enhance-email-security-with-spf-dkim-dmarc/</guid><description>&lt;div class="alert alert-info" role="alert"&gt;
&lt;p&gt;&lt;a href="https://techcommunity.microsoft.com/blog/microsoftdefenderforoffice365blog/strengthening-email-ecosystem-outlook%E2%80%99s-new-requirements-for-high%E2%80%90volume-senders/4399730"&gt;Microsoft announced&lt;/a&gt; that starting from May 5, 2025: SPF, DKIM and DMARC will become mandatory for inbound email delivery. Not configuring all three can result in your emails not being delivered correctly.&lt;/p&gt;
&lt;/div&gt;
&lt;p&gt;These 3 techniques are:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;SPF&lt;/strong&gt;: Sender Policy Framework&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;DKIM&lt;/strong&gt;: Domain Keys Identified Mail&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;DMARC&lt;/strong&gt;: Domain-based Message Authentication Reporting and Conformance&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;When using Microsoft 365 as your messaging service, I also highly recommend to configure SMTP DANE. A detailed guide of configuring this can be found here: &lt;a href="https://justinverstijnen.nl/configure-dnssec-and-smtp-dane-with-exchange-online-microsoft-365/"&gt;https://justinverstijnen.nl/configure-dnssec-and-smtp-dane-with-exchange-online-microsoft-365/&lt;/a&gt;&lt;/p&gt;</description></item><item><title>Disable DirectSend in Exchange Online</title><link>https://justinverstijnen.nl/disable-directsend-in-exchange-online/</link><pubDate>Sun, 04 May 2025 00:00:00 +0000</pubDate><guid>https://justinverstijnen.nl/disable-directsend-in-exchange-online/</guid><description>&lt;h2 id="what-is-directsend"&gt;What is DirectSend?&lt;a class="td-heading-self-link" href="#what-is-directsend" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;DirectSend (Microsoft 365) lets devices or applications (like printers, scanners, or internal apps) send email directly to users inside your organization without authentication. Instead of using authentication, it uses your MX record directly with port 25.&lt;/p&gt;
&lt;p&gt;Some details about DirectSend:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Only works for internal recipients (same tenant)&lt;/li&gt;
&lt;li&gt;No mailbox or license required for the sending device/app&lt;/li&gt;
&lt;li&gt;Uses SMTP to your tenant’s MX endpoint&lt;/li&gt;
&lt;li&gt;Commonly used for scanners, alerts, and legacy systems&lt;/li&gt;
&lt;li&gt;Does not support sending to external email addresses&lt;/li&gt;
&lt;li&gt;Possibly exposing public IP addresses in your DNS records&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;We can see it like a internal relay, possible to send email to all users in your tenant, which is actively used to distribute malicious activity. This consists of sending mailware or credential harvesting, bypassing different security controls active on normal email.&lt;/p&gt;</description></item><item><title>Set a domain alias for every user in Microsoft 365</title><link>https://justinverstijnen.nl/set-a-domain-alias-for-every-user-in-microsoft-365/</link><pubDate>Fri, 13 Dec 2024 00:00:00 +0000</pubDate><guid>https://justinverstijnen.nl/set-a-domain-alias-for-every-user-in-microsoft-365/</guid><description>&lt;h2 id="logging-in-exchange-online-powershell"&gt;Logging in Exchange Online Powershell&lt;a class="td-heading-self-link" href="#logging-in-exchange-online-powershell" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;To configure a alias for every user, we need to login into Exchange Online Powershell:&lt;/p&gt;

 &lt;div class="td-card card border me-4"&gt;
&lt;div class="card-header code"&gt;
 &lt;strong&gt;POWERSHELL&lt;/strong&gt;
 &lt;/div&gt;
&lt;div class="card-body code p-0 m-0"&gt;
 &lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-powershell" data-lang="powershell"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nb"&gt;Connect-ExchangeOnline&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;
 &lt;/div&gt;

&lt;p&gt;If you don&amp;rsquo;t have the module already installed on your computer, run the following command on an elevated window:&lt;/p&gt;

 &lt;div class="td-card card border me-4"&gt;
&lt;div class="card-header code"&gt;
 &lt;strong&gt;POWERSHELL&lt;/strong&gt;
 &lt;/div&gt;
&lt;div class="card-body code p-0 m-0"&gt;
 &lt;div class="highlight"&gt;&lt;pre tabindex="0" class="chroma"&gt;&lt;code class="language-powershell" data-lang="powershell"&gt;&lt;span class="line"&gt;&lt;span class="cl"&gt;&lt;span class="nb"&gt;Install-Module&lt;/span&gt; &lt;span class="n"&gt;ExchangeOnlineManagement&lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/div&gt;
 &lt;/div&gt;

&lt;p&gt;Source: &lt;a href="https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.7.2"&gt;https://www.powershellgallery.com/packages/ExchangeOnlineManagement/3.7.2&lt;/a&gt;&lt;/p&gt;
&lt;h2 id="adding-the-365-domain-alias-to-every-user"&gt;Adding the 365 domain alias to every user&lt;a class="td-heading-self-link" href="#adding-the-365-domain-alias-to-every-user" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;After succesfully logged in, run the following command:&lt;/p&gt;</description></item><item><title>Configure DNSSEC and SMTP DANE Microsoft 365</title><link>https://justinverstijnen.nl/configure-dnssec-and-smtp-dane-with-exchange-online-microsoft-365/</link><pubDate>Thu, 31 Oct 2024 00:00:00 +0000</pubDate><guid>https://justinverstijnen.nl/configure-dnssec-and-smtp-dane-with-exchange-online-microsoft-365/</guid><description>&lt;h2 id="domain-name-system-security-extensions-dnssec"&gt;Domain Name System Security Extensions (DNSSEC)&lt;a class="td-heading-self-link" href="#domain-name-system-security-extensions-dnssec" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;DNSSEC is a feature where a client can validate the DNS records received by a DNS server to ensure a record is originated from the DNS server and not manipulated by a Man in the Middle attack.&lt;/p&gt;
&lt;p&gt;DNSSEC is developed to prevent attacks like in the topology below:&lt;/p&gt;
&lt;p&gt;&lt;img src="https://sajvwebsiteblobstorage.blob.core.windows.net/blog/configure-dnssec-and-smtp-dane-with-exchange-online-microsoft-365-499/jv-media-499-1494f13639ce.png" alt=""&gt;&lt;/p&gt;
&lt;p&gt;Here a attacker injects a fake DNS record and sends the user to a different IP-address, not the actual IP-address of the real website but a fake, mostly spoofed website. This way, a user sees for example &lt;a href="https://portal.azure.com"&gt;https://portal.azure.com&lt;/a&gt; in his address bar but is actually on a malicious webserver. This makes the user far more vulnerable to credential harvesting or phising attacks.&lt;/p&gt;</description></item><item><title>Solved - Microsoft 365 tenant dehydrated</title><link>https://justinverstijnen.nl/microsoft-365-tenant-dehydrated/</link><pubDate>Fri, 20 Sep 2024 00:00:00 +0000</pubDate><guid>https://justinverstijnen.nl/microsoft-365-tenant-dehydrated/</guid><description>&lt;h2 id="what-is-tenant-dehydrated"&gt;What is &amp;ldquo;Tenant dehydrated&amp;rdquo;?&lt;a class="td-heading-self-link" href="#what-is-tenant-dehydrated" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Microsoft sometimes will dehydrate Microsoft 365 tenants where things will not often change to the tenant. This closes some parts of the tenant for changing, even if you have Global Administrator permissions.&lt;/p&gt;
&lt;p&gt;The cause of this is for Microsoft to save on infrastructure cost. They will set the tenant in this sort of &amp;ldquo;sleep mode&amp;rdquo; where everything works properly but some configuration changes cannot be done. You can get this error with all sorts of changes:&lt;/p&gt;</description></item><item><title>Create a Catch all mailbox in Exchange Online</title><link>https://justinverstijnen.nl/create-a-catch-all-mailbox-in-exchange-online/</link><pubDate>Thu, 11 Jul 2024 00:00:00 +0000</pubDate><guid>https://justinverstijnen.nl/create-a-catch-all-mailbox-in-exchange-online/</guid><description>&lt;p&gt;I also created a full customizable PowerShell script for this task which you can find here:&lt;/p&gt;
&lt;p&gt;&lt;a class="btn btn-primary" href="https://github.com/JustinVerstijnen/M365CatchAllScript"&gt;&lt;i class="fa-brands fa-github"&gt;&lt;/i&gt; Download script from GitHub&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;This way you can skip the guide for a faster solution. Otherwise, follow the steps below to do everything by hand and get a better understanding of the relevant steps needed.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id="requirements"&gt;Requirements&lt;a class="td-heading-self-link" href="#requirements" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Around 20 minutes of your time&lt;/li&gt;
&lt;li&gt;A Microsoft 365 environment&lt;/li&gt;
&lt;li&gt;Basic knowledge of Exchange Online&lt;/li&gt;
&lt;li&gt;Basic knowledge of PowerShell&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h2 id="how-does-this-solution-work"&gt;How does this solution work?&lt;a class="td-heading-self-link" href="#how-does-this-solution-work" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;The solution described in this guide works with 3 components:&lt;/p&gt;</description></item><item><title>Microsoft 365 create a shared mailbox with same alias</title><link>https://justinverstijnen.nl/microsoft-365-exchange-online-create-shared-mailbox-with-same-alias/</link><pubDate>Thu, 06 Jun 2024 00:00:00 +0000</pubDate><guid>https://justinverstijnen.nl/microsoft-365-exchange-online-create-shared-mailbox-with-same-alias/</guid><description>&lt;h2 id="the-problem-of-multiple-shared-mailboxes-with-same-alias"&gt;The problem of multiple shared mailboxes with same alias&lt;a class="td-heading-self-link" href="#the-problem-of-multiple-shared-mailboxes-with-same-alias" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Let&amp;rsquo;s say, we have a Microsoft 365 tenant with 3 domains;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;domain1.com&lt;/li&gt;
&lt;li&gt;domain2.com&lt;/li&gt;
&lt;li&gt;domain3.com&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;When you already have a mailbox called &amp;ldquo;&lt;a href="mailto:info@domain1.com"&gt;info@domain1.com&lt;/a&gt;&amp;rdquo; you are unable to create a &amp;ldquo;&lt;a href="mailto:info@domain2.com"&gt;info@domain2.com&lt;/a&gt;&amp;rdquo; in the portal. The cause of this problem is that every mailbox has a underlying &amp;ldquo;alias&amp;rdquo; and that this alias is the same when created in the portal. I have tried this in the Microsoft 365 admin center, Exchange Online admin center and Powershell. I get the following error:&lt;/p&gt;</description></item><item><title>Migrate data to SharePoint/OneDrive with SPMT</title><link>https://justinverstijnen.nl/sharepoint-data-migration/</link><pubDate>Mon, 20 May 2024 00:00:00 +0000</pubDate><guid>https://justinverstijnen.nl/sharepoint-data-migration/</guid><description>&lt;p&gt;At the moment, SharePoint is a better option to store your files because it has the following benefits over a traditional SMB share:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Single permissions system (No SMB/NTFS permissions)&lt;/li&gt;
&lt;li&gt;High available by default&lt;/li&gt;
&lt;li&gt;No server infrastructure needed&lt;/li&gt;
&lt;li&gt;Users can work at the same file simultaneously&lt;/li&gt;
&lt;li&gt;Integration with Microsoft Teams&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h2 id="the-microsoft-sharepoint-migration-tool"&gt;The Microsoft SharePoint Migration Tool&lt;a class="td-heading-self-link" href="#the-microsoft-sharepoint-migration-tool" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Microsoft has a tool available which is free and which can migrate your local data to SharePoint. The targets you can specify are:&lt;/p&gt;</description></item><item><title>Dynamic Distribution Groups in Microsoft 365</title><link>https://justinverstijnen.nl/dynamic-distribution-groups-in-microsoft-365/</link><pubDate>Sat, 21 Oct 2023 00:00:00 +0000</pubDate><guid>https://justinverstijnen.nl/dynamic-distribution-groups-in-microsoft-365/</guid><description>&lt;p&gt;Sometimes you want to have a distribution group with all your known mailboxes in it. For example an &lt;a href="mailto:employees@justinverstijnen.nl"&gt;employees@justinverstijnen.nl&lt;/a&gt; or &lt;a href="mailto:all@justinverstijnen.nl"&gt;all@justinverstijnen.nl&lt;/a&gt; address to send a mail company wide. A normal distribution group is possible, but requires a lot of manual maintenance, like adding and removing users.&lt;/p&gt;
&lt;p&gt;To apply a little more automation you can use the Dynamic Distribution Group feature of Exchange Online. This is a feature like the Dynamic groups feature of Microsoft Entra which automatically adds new user mailboxes after they are created to make sure every new employee is added automatically.&lt;/p&gt;</description></item></channel></rss>