Merge branch 'main' into v-liuamson-CI6613

Author: Amson Liu

.openpublishing.redirection.json

@@ -13761,6 +13761,45 @@
     {
       "source_path": "support/windows-client/performance/stop-error-or-blue-screen-error-troubleshooting.md",
       "redirect_url": "/troubleshoot/windows-client/performance/stop-code-error-troubleshooting"
+    },
+    {
+      "source_path": "support/power-platform/power-automate/desktop-flows/office-automation/excel/launch-excel-action-failures.md",
+      "redirect_url": "/troubleshoot/power-platform/power-automate/desktop-flows/office-automation/excel/troubleshoot-excel-errors"
+    },
+    {
+      "source_path": "support/sql/database-engine/install/windows/install-reporting-service.md",
+      "redirect_url": "/previous-versions/troubleshoot/sql/install/install-reporting-service",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "support/sql/database-engine/install/windows/issues-install-sql-server.md",
+      "redirect_url": "/previous-versions/troubleshoot/sql/install/issues-install-sql-server",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "support/sql/database-engine/install/windows/sql-server-2008-setup-issues.md",
+      "redirect_url": "/previous-versions/troubleshoot/sql/install/sql-server-2008-setup-issues",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "support/sql/database-engine/install/windows/sql-server-2012-setup-issues.md",
+      "redirect_url": "/previous-versions/troubleshoot/sql/install/sql-server-2012-setup-issues",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "support/sql/database-engine/security/instructions-in-fips-140-2-compliant-mode.md",
+      "redirect_url": "/previous-versions/troubleshoot/sql/security/instructions-in-fips-140-2-compliant-mode",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "support/sql/database-engine/security/sql-2014-fips-140-2-compliant-mode.md",
+      "redirect_url": "/previous-versions/troubleshoot/sql/security/sql-2014-fips-140-2-compliant-mode",
+      "redirect_document_id": false
+    },
+    {
+      "source_path": "support/sql/tools/error-you-run-sqlmaint-utility.md",
+      "redirect_url": "/previous-versions/troubleshoot/sql/tools/error-you-run-sqlmaint-utility",
+      "redirect_document_id": false
     }
   ]
 }

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

@@ -56,8 +56,8 @@ The following table contains the error codes (also known as enhanced status code
 |550 5.1.20|`Multiple From addresses are not allowed without Sender address`|An email message has multiple email addresses in the **From** field, but no email address in the **Sender** field.|For more information, see [Fix NDR error code 550 5.1.20 "Multiple From addresses are not allowed without Sender address"](/exchange/troubleshoot/email-delivery/ndr/fix-error-code-550-5-1-20-multiple-from-addresses).|
 |5.1.90|`Your message can't be sent because you've reached your daily limit for message recipients`|The sender has exceeded the recipient rate limit, as described in [Sending limits](/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits#sending-limits).|This could indicate that the account was compromised and is being used to send spam. For more information, see [Responding to a compromised account](/defender-office-365/responding-to-a-compromised-email-account).|
 |5.2.2|`Submission quota exceeded`|The sender has exceeded the recipient rate limit or the message rate limit as described in [Sending limits](/office365/servicedescriptions/exchange-online-service-description/exchange-online-limits#sending-limits).|This could indicate the account was compromised and is being used to send spam. For more information, see [Responding to a compromised account](/defender-office-365/responding-to-a-compromised-email-account).|
-|5.2.121|`Recipient's per hour message receive limit from specific sender exceeded`|The sender has exceeded the maximum number of messages that they're allowed to send per hour to a specific recipient in Exchange Online.|The automated mailer or sender should try again later, and reduce the number of messages that they send per hour to a specific recipient. <br/><br/> This limit helps protect Microsoft 365 or Office 365 users from rapidly filling their Inboxes with many messages from errant automated notification systems or other single-sender mail storms.|
-|5.2.122|`Recipient's per hour message receive limit exceeded`|The Microsoft 365 or Office 365 recipient has exceeded the number of messages that they can receive per hour from all senders.|The automated mailer or sender should try again later, and reduce the number of messages that they send per hour to a specific recipient. <br/><br/> This limit helps protect Microsoft 365 and Office 365 users from rapidly filling their Inboxes with many messages from errant automated notification systems or other mail storms.|
+|5.2.121|`Recipient's per hour message receive limit from specific sender exceeded`|The sender has exceeded the maximum number of messages that they're allowed to send per hour to a specific recipient in Exchange Online.|The automated mailer or sender should try again later, and reduce the number of messages that they send per hour to a specific recipient. <br/><br/> This limit helps protect Microsoft 365 and Office 365 users from rapidly filling their Inboxes with many messages from errant automated notification systems or other single-sender mail storms. <br/><br/> The ["Mailboxes exceeding receiving limits"](/exchange/monitoring/mail-flow-reports/mailboxes-exceeding-receiving-limits-report) report shows detailed information about the mailboxes that are receiving large volumes of messages in a short time.|
+|5.2.122|`Recipient's per hour message receive limit exceeded`|The Microsoft 365 or Office 365 recipient has exceeded the number of messages that they can receive per hour from all senders.|The automated mailer or sender should try again later, and reduce the number of messages that they send per hour to a specific recipient. <br/><br/> This limit helps protect Microsoft 365 and Office 365 users from rapidly filling their Inboxes with many messages from errant automated notification systems or other mail storms. <br/><br/> The ["Mailboxes exceeding receiving limits"](/exchange/monitoring/mail-flow-reports/mailboxes-exceeding-receiving-limits-report) report shows detailed information about the mailboxes that are receiving large volumes of messages in a short time.|
 |5.3.190|`Journaling on-premises messages to Microsoft 365 or Office 365 not supported when Journaling Archive is disabled`|Journaling on-premises messages to Microsoft 365 or Office 365 isn't supported for this organization because the organization hasn't turned on Journaling Archive in its settings.|A journaling rule is configured in the organization's on-premises environment to journal on-premises messages to Microsoft 365 or Office 365, but Journaling Archive is disabled. For this scenario to work, the organization's Office 365 administrator should either enable Journaling Archive or change the journaling rule to journal messages to a different location.|
 |5.4.1|`Relay Access Denied`|The mail server that's generating the error doesn't accept mail for the recipient's domain. This error is caused by mail server or DNS misconfiguration.|For more information, see [Fix email delivery issues for error code 5.4.1 in Exchange Online](https://support.microsoft.com/topic/c0e98a8e-81db-49c2-9bf1-32a1734d3e77).|
 |5.4.1|`Recipient address rejected: Access denied`|The recipient's address doesn't exist.|For more information, see [Use Directory Based Edge Blocking to reject messages sent to invalid recipients](/exchange/mail-flow-best-practices/use-directory-based-edge-blocking).|

Microsoft365/purview/diagnostics/purview-compliance-diagnostics.md

@@ -15,13 +15,11 @@ ms.reviewer: shadans, sathyana, meerak, v-shorestris
 appliesto:
   - Microsoft Purview
 search.appverid: MET150
-ms.date: 05/05/2025
+ms.date: 07/21/2025
 ---
 
 # Self-help diagnostics for Microsoft Purview
 
-<!-- This article has been reviewed and approved for the specific use of global admin perms. -->
-
 You can run diagnostics to identify and resolve issues in Microsoft Purview. The diagnostics offer insights into known issues and provide instructions to fix them. Although the diagnostics can fix some configuration issues, they don't make changes to your tenant without your consent.
 
 Self-help diagnostics that relate to Microsoft Purview are available in the following locations:
@@ -55,7 +53,7 @@ You can find these diagnostics on the following portal pages:
 
 The following table lists the available diagnostics on **Solutions** pages. You can access the diagnostics by selecting the associated link in the third column. When you're prompted, sign in to the Microsoft Purview portal.
 
-**Note**: To run these diagnostics, you must be a Microsoft 365 global administrator.
+**Note**: To run these diagnostics, the minimum requirement is that you're an administrator with the Organization Configuration role assigned to you.
 
 | **Issue** | **Checks performed** | **Solutions page** |
 |-|-|-|