Merge pull request #10469 from MicrosoftDocs/main

Auto Publish – main to live - 2026-01-08 10:00 UTC

Author: learn-build-service-prod[bot]

Exchange/ExchangeOnline/email-delivery/ndr/non-delivery-reports-in-exchange-online.md

@@ -1,6 +1,6 @@
 ---
 title: Email non-delivery report (NDR) and SMTP errors in Exchange Online
-ms.date: 10/14/2024
+ms.date: 01/07/2026
 author: cloud-writer
 ms.author: meerak
 manager: dcscontentpm
@@ -82,6 +82,7 @@ The following table contains the error codes (also known as enhanced status code
 |5.7.136|`Sender was not authenticated`|The recipient address is a mail user that is set up to reject messages sent from outside its organization. Only an email administrator for the recipient's organization can change this.|For more information, see [Fix email delivery issues for error code 5.7.136 in Exchange Online](fix-error-code-5-7-136-in-exchange-online.md).|
 |5.7.232|`Your message can't be sent because your trial tenant has exceeded its daily limit for sending email to external recipients (tenant external recipient rate limit)`|The number of external recipients emailed in a 24-hour period exceeds the external recipient rate limit in Exchange Online. The limit applies per trial tenant.|The external recipient rate limit is tracked over a 24-hour rolling window. When the count for the most recent 24-hour period falls below the limit, users in the trial tenant can resume sending messages to external recipients. The limit helps prevent the distribution of unsolicited bulk messages.|
 |5.7.233|`Your message can't be sent because your tenant exceeded its daily limit for sending email to external recipients (tenant external recipient rate limit)`|The number of external recipients emailed in a 24-hour period exceeds the external recipient rate limit in Exchange Online. The limit applies per tenant.|The external recipient rate limit is tracked over a 24-hour rolling window. When the count for the most recent 24-hour period falls below the limit, users in the tenant can resume sending messages to external recipients. The limit helps prevent the distribution of unsolicited bulk messages.|
+|5.7.236|`Your message can't be sent because your tenant has exceeded its daily limit for sending email to external recipients from your tenant's onmicrosoft.com domains`|Your organization has exceeded the limit of sending emails to 100 external recipients from your organization’s onmicrosoft.com (MOERA) domain within a 24‑hour rolling window. This limit is enforced per tenant.|MOERA (onmicrosoft.com) domains are intended only for testing, and shouldn't be used to send regular email messages. Messages sent from these domains are limited to 100 external recipients for a rolling 24-hour period. Inbound emails are not affected. External recipients are counted after any recipient list expansion. To avoid this limitation, purchase and migrate to a custom domain. Then ensure that only the custom domain is used to send email messages to external recipients.|
 |5.7.321|`starttls-not-supported: Destination mail server must support TLS to receive mail.`|<ul><li>DNSSEC checks have passed, yet, upon connection, the destination mail server doesn't respond to the `STARTTLS` command. </li><li>The destination server responds to the `STARTTLS` command, but the TLS handshake fails. </li></ul>| This message usually indicates an issue on the destination mail server. Check the validity of the recipient address and determine if the destination server is configured correctly to receive messages.|
 |5.7.322|`certificate-expired: Destination mail server's certificate is expired.`| DNSSEC checks have passed, yet, upon establishing the connection, the destination mail server provides a certificate that is expired. | A valid X.509 certificate that isn't expired must be presented. X.509 certificates must be renewed after their expiration, most commonly on an annual basis.|
 |5.7.323|`tlsa-invalid: The domain failed DANE validation.`| Records are DNSSEC authentic but one or more of the following things occurred: <ul><li> The destination mail server's certificate doesn't match what is expected per the authentic TLSA record.</li><li> The authentic TLSA record is misconfigured. </li><li> The destination domain is being attacked.</li><li> The certificate start date is in the future. </li><li> Any other DANE failure.</li></ul>| This message usually indicates an issue exists on the destination mail server. Check the validity of the recipient address and determine if the destination server is configured correctly to receive messages. <br/><br/> For more information about DANE, see [https://datatracker.ietf.org/doc/html/rfc7671](https://datatracker.ietf.org/doc/html/rfc7671).|

support/mem/configmgr/mdt/troubleshooting-reference.md

@@ -8,7 +8,12 @@ ms.custom: sap:Operating Systems Deployment (OSD)\MDT Integration or User Driven
 
 # Troubleshooting Reference for the Microsoft Deployment Toolkit
 
-The deployment of operating systems and applications as well as the migration of user state can be a challenging endeavor, even when you are equipped with appropriate tools and guidance. This reference, which is part of Microsoft® Deployment Toolkit (MDT) 2013, provides information on current known issues, possible workarounds for those issues, and troubleshooting guidance.  
+##  Microsoft Deployment Toolkit (MDT) is now retired
+
+> [!IMPORTANT]
+> **Microsoft Deployment Toolkit (MDT) is now retired.** MDT integration with Configuration Manager and MDT Standalone are **no longer supported**. To prevent task sequence corruption and modification failures, **remove all MDT task sequence steps**, and then **remove MDT integration**. Consider moving to modern provisioning solutions such as Windows Autopilot to obtain cloud‑driven, zero‑touch provisioning for Windows devices. [Learn more about Autopilot](/windows/deployment/windows-autopilot/windows-autopilot). For customers who have on-premises infrastructure and existing Configuration Manager environments, OSD remains a fully supported option.
+>
+>For full details about this retirement, see the [Removed and Deprecated Features](/intune/configmgr/core/plan-design/changes/deprecated/removed-and-deprecated-cmfeatures) page.
 
 > [!NOTE]
 > In this document, *Windows* applies to the Windows 8.1, Windows 8, Windows 7, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2 operating systems unless otherwise noted. MDT does not support ARM processor–based versions of Windows. Similarly, *MDT* refers to MDT 2013 unless otherwise stated.  

support/windows-server/setup-upgrade-and-drivers/deployment-toolkit-support.md

@@ -1,6 +1,6 @@
 ---
-title: Microsoft Deployment Toolkit support life cycle
-description: Discusses the support life cycle for Microsoft Deployment Toolkits.
+title: Microsoft Deployment Toolkit support lifecycle
+description: Discusses the support lifecycle for Microsoft Deployment Toolkits.
 ms.date: 01/15/2025
 manager: dcscontentpm
 audience: itpro
@@ -12,22 +12,22 @@ ms.custom:
 appliesto:
   - <a href=https://learn.microsoft.com/windows/release-health/windows-server-release-info target=_blank>Supported versions of Windows Server</a>
 ---
-# Microsoft Deployment Toolkit support life cycle
+# Microsoft Deployment Toolkit support lifecycle
 
-This article discusses the support life cycle for Microsoft Deployment Toolkits.
+This article discusses the support lifecycle for Microsoft Deployment Toolkits.
 
 _Original KB number:_ &nbsp; 2872000
 
-## Summary
+##  Microsoft Deployment Toolkit (MDT) is now retired
 
-The latest version of the Microsoft Deployment Toolkit can be downloaded from the following Microsoft Download Center website:
-[Microsoft Download Center](https://go.microsoft.com/fwlink/?LinkId=325278)
-For more information about the Microsoft Deployment Toolkit, see the following Windows website:
-[Microsoft Deployment Toolkit documentation](https://www.microsoft.com/mdt)
+> [!IMPORTANT]
+> **Microsoft Deployment Toolkit (MDT) is retired.** MDT integration with Configuration Manager and MDT Standalone are **no longer supported**. To prevent task sequence corruption and modification failures, **remove all MDT task sequence steps**, and then **remove MDT integration**. Consider moving to modern provisioning solutions such as Windows Autopilot to obtain cloud‑driven, zero‑touch provisioning for Windows devices. [Learn more about Autopilot](/windows/deployment/windows-autopilot/windows-autopilot). For customers who have on-premises infrastructure and existing Configuration Manager environments, OSD remains a fully supported option.
+>
+>For full details about this retirement, see the [Removed and Deprecated Features](/intune/configmgr/core/plan-design/changes/deprecated/removed-and-deprecated-cmfeatures) page.
 
 ## More information
 
-Microsoft Deployment Toolkits use the following support life cycle:
+Microsoft Deployment Toolkits use the following support lifecycle:
 
 - MDT releases will support only scenarios that use underpinning technologies that are still under their mainstream support policy.
 - MDT releases will be supported for one (1) year after the next version is released, whichever date is last.