Microsoft is changing email sending – what this means for your website's forms

Microsoft is changing email sending – what this means for your website's forms

17.11.2026

At the end of December 2026, Microsoft will disable SMTP sign-in with a password by default in Microsoft 365. In addition, your IT department can block what is known as "Direct Send". Many websites currently use these two methods to send their contact requests, job applications and confirmations. Below you will find out whether your website is affected and how we will switch it over in good time.

What is changing?

In Microsoft 365 (Exchange Online), Microsoft is closing two older methods that websites currently use to send emails:

  • SMTP sign-in with a password: At the end of December 2026, Microsoft will disable it by default in existing Microsoft 365 environments. Your IT department can temporarily re-enable it, but only until the final cut-off date. Microsoft will announce this date in the second half of 2027.
  • Direct Send: Since April 2025, your IT department can have mail rejected that arrives without authentication using your own sender address. For new environments, Microsoft plans to make this block the default.

Important note: The change only affects companies whose email runs through Microsoft 365. If your mailboxes are hosted, for example, with Hostpoint or Mittwald, or on an Exchange server that you or your IT partner operate yourselves, nothing changes for you.

Sources: Microsoft Exchange Team Blog, "Updated Exchange Online SMTP AUTH Basic Authentication Deprecation Timeline" (27 January 2026) and "Introducing more control over Direct Send in Exchange Online" (28 April 2025, updated 20 May 2026).

Why does this affect your website?

Your website sends contact requests, job applications and confirmations to visitors as emails. Depending on how it is set up, it uses one of three methods:

  • SMTP with username and password: The website logs in to smtp.office365.com with the password of a Microsoft 365 account. Affected from the end of December 2026.
  • The hosting provider's mail server (sendmail): The website sends via the web server, with your address as the sender. Emails to your own mailbox arrive as Direct Send. Affected as soon as your IT department blocks Direct Send.
  • Microsoft Graph with OAuth 2.0: The website sends directly from your mailbox, without a password and without SMTP. Not affected.

If the method stops working, the website still shows the visitor "Thank you very much". But the email does not arrive, and nobody sees an error message. Because the cut-off date falls during the holidays, an outage can easily go unnoticed until January.

Already an issue today: In our checks, we have found websites whose emails already end up in spam or are rejected today. The reason: the domain's SPF record does not authorise the hosting provider's server. Switching to Microsoft Graph fixes this too.

Our solution: sending via Microsoft Graph

We are switching your website so that it sends directly from your own Microsoft 365 mailbox. To do this, we have developed our own mail module for TYPO3.

  • No password, no SMTP: TYPO3 signs in with its own app permission (OAuth 2.0). It needs neither a user account nor an exception from multi-factor authentication.
  • Genuine sender: The email comes from Microsoft's servers, from your mailbox. SPF, DKIM and DMARC all pass, exactly as with an email sent from Outlook.
  • Access to one mailbox: The permission applies to only one mailbox, for example info@. Microsoft rejects reading and sending in other mailboxes.
  • Not affected by either change: Neither the end of password sign-in nor a block on Direct Send affects this method.
     

Already in use: For a first customer, sending has been running via Microsoft Graph since the beginning of November 2026, for the contact form and for job applications with CVs. It takes about three seconds from submitting the form to arriving in the inbox.

Why not simply re-enable password sign-in?

This is usually the first question. There are three ways for your website to keep sending emails after the end of December:

  • Re-enabling password sign-in: This only works until the final cut-off date, which Microsoft will announce in the second half of 2027. Until then, it still requires an account with a password and an exception from multi-factor authentication. After that, the same switchover is due again.
  • An external sending service (for example SendGrid, Mailjet or Brevo): This works permanently, but the emails then run through the provider's servers instead of through your Microsoft 365. It requires its own DNS entries, another contract, a cost per email depending on volume, and another data processor for personal data.
  • Microsoft Graph (our solution): This works after the final date too, without an account with a password and without an additional contract. The sender is your own mailbox, and the emails stay in your Microsoft 365. If Microsoft is briefly unreachable, the website sets the email aside and sends it again automatically.

Process and schedule

To ensure the switch is completed before Microsoft's cut-off date, we recommend the following schedule:

  • By 27 November – Review: We review all forms and sending paths on your website, including confirmations and job applications with attachments. You don't need to check anything yourself.
  •  By 4 December – Approval at Microsoft: Your IT partner or Microsoft 365 admin registers the app and restricts it to one mailbox. This takes about 15 minutes. We provide them with instructions and ready-made commands.
  • By 9 December – Testing: We test delivery, large attachments and permissions. The website continues to run unchanged in the meantime.
  • By 18 December – Switchover: With no downtime and with a real form test. During the transition period, switching back is possible at any time.
  • January 2027 – Follow-up check: Two weeks after the switchover, we check sending again. After that, your IT department can turn off password sign-in and Direct Send.

Note: TYPO3 13 is a prerequisite. If your website runs on an older version, we will discuss the way forward with you.

What do we need from you?

  • Your "yes" to the switch: A short email is enough.
  • The contact details of your IT partner or Microsoft 365 admin: They need about 15 minutes for the approval.
  • A quick decision: Should the website's emails appear in your mailbox under "Sent Items"? 
     

We take care of everything else: setup, testing, the switchover, the follow-up check and renewing the app key before it expires.

Our support for you

We are informing customers whose emails run through Microsoft 365 personally by email in the coming days. You don't have to work out for yourself which method applies to you: we look after your website and will check this for you. If your TYPO3 website is not maintained by us, we will gladly check whether it is affected.