Merge branch 'main' into merge-and-improve

Author: lucciz01

.openpublishing.redirection.json

@@ -12884,6 +12884,10 @@
       "source_path": "support/power-platform/dataverse/d365-app-outlook/we-cannot-load-this-app.md",
       "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/error-when-opening-365-app-outlook"
     },   
+    {
+      "source_path": "support/power-platform/dataverse/d365-app-outlook/error-incomingemailrejected-install-dynamics-365-app-outlook.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/error-install-dynamics-365-app-outlook"
+    },
     {
       "source_path": "support/power-platform/dataverse/d365-app-outlook/current-user-role-not-have-required-permissions.md",
       "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/privilege-error-occurs-when-using-dynamics-365-app-for-outlook"

support/azure/virtual-machines/linux/serial-console-linux.md

@@ -12,7 +12,7 @@ ms.collection: linux
 ms.topic: article
 ms.tgt_pltfrm: vm-linux
 ms.workload: infrastructure-services
-ms.date: 02/10/2025
+ms.date: 03/11/2025
 ms.author: mbifeld
 ---
 
@@ -131,7 +131,7 @@ Serial Console uses the storage account configured for boot diagnostics in its c
    | UAE | UAE Central, UAE North | 20.38.141.5, 20.45.95.64, 20.45.95.65, 20.45.95.66, 20.203.93.198, 20.233.132.205, 40.120.87.50, 40.120.87.51 |
    | United Kingdom | UK South, UK West | 20.58.68.62, 20.58.68.63, 20.90.32.180, 20.90.132.144, 20.90.132.145, 51.104.30.169, 172.187.0.26, 172.187.65.53 |
    | United States | US Central, US East, US East 2, US East 2 EUAP, US North, US South, US West, US West 2, US West 3 | 4.149.249.197, 4.150.239.210, 20.14.127.175, 20.40.200.175, 20.45.242.18, 20.45.242.19, 20.45.242.20, 20.47.232.186, 20.51.21.252, 20.69.5.160, 20.69.5.161, 20.69.5.162, 20.83.222.100, 20.83.222.101, 20.83.222.102, 20.98.146.84, 20.98.146.85, 20.98.194.64, 20.98.194.65, 20.98.194.66, 20.168.188.34, 20.241.116.153, 52.159.214.194, 57.152.124.244, 68.220.123.194, 74.249.127.175, 74.249.142.218, 157.55.93.0, 168.61.232.59, 172.183.234.204, 172.191.219.35 |
-   | USGov | All US Government Cloud regions | 20.140.104.48, 20.140.105.3, 20.140.144.58, 20.140.144.59, 20.140.147.168, 20.140.53.121, 20.141.10.130, 20.141.10.131, 20.141.13.121, 20.141.15.104, 52.127.55.131, 52.235.252.252, 52.235.252.253, 52.243.247.124, 52.245.155.139, 52.245.156.185, 62.10.196.24, 62.10.196.25, 62.10.84.240, 62.11.6.64, 62.11.6.65 |
+   | USGov | All US Government Cloud regions | 20.140.104.48, 20.140.105.3, 20.140.144.58, 20.140.144.59, 20.140.147.168, 20.140.53.121, 20.141.10.130, 20.141.10.131, 20.141.13.121, 20.141.15.104, 52.127.55.131, 52.235.252.252, 52.235.252.253, 52.243.247.124, 52.245.155.139, 52.245.156.185, 62.10.84.240 |
 
    > [!IMPORTANT]
    > - The IPs that need to be permitted are specific to the region where the VM is located. For example, a virtual machine deployed in the North Europe region needs to add the following IP exclusions to the storage account firewall for the Europe geography: 52.146.139.220 and 20.105.209.72. View the table above to find the correct IPs for your region and geography.

support/azure/virtual-machines/windows/serial-console-windows.md

@@ -11,7 +11,7 @@ ms.collection: windows
 ms.topic: article
 ms.tgt_pltfrm: vm-windows
 ms.workload: infrastructure-services
-ms.date: 01/10/2025
+ms.date: 03/11/2025
 ms.author: mbifeld
 ms.custom: sap:VM Admin - Windows (Guest OS)
 ---
@@ -185,7 +185,7 @@ Serial Console uses the storage account configured for boot diagnostics in its c
    | UAE | UAE Central, UAE North | 20.38.141.5, 20.45.95.64, 20.45.95.65, 20.45.95.66, 20.203.93.198, 20.233.132.205, 40.120.87.50, 40.120.87.51 |
    | United Kingdom | UK South, UK West | 20.58.68.62, 20.58.68.63, 20.90.32.180, 20.90.132.144, 20.90.132.145, 51.104.30.169, 172.187.0.26, 172.187.65.53 |
    | United States | US Central, US East, US East 2, US East 2 EUAP, US North, US South, US West, US West 2, US West 3 | 4.149.249.197, 4.150.239.210, 20.14.127.175, 20.40.200.175, 20.45.242.18, 20.45.242.19, 20.45.242.20, 20.47.232.186, 20.51.21.252, 20.69.5.160, 20.69.5.161, 20.69.5.162, 20.83.222.100, 20.83.222.101, 20.83.222.102, 20.98.146.84, 20.98.146.85, 20.98.194.64, 20.98.194.65, 20.98.194.66, 20.168.188.34, 20.241.116.153, 52.159.214.194, 57.152.124.244, 68.220.123.194, 74.249.127.175, 74.249.142.218, 157.55.93.0, 168.61.232.59, 172.183.234.204, 172.191.219.35 |
-   | USGov | All US Government Cloud regions | 20.140.104.48, 20.140.105.3, 20.140.144.58, 20.140.144.59, 20.140.147.168, 20.140.53.121, 20.141.10.130, 20.141.10.131, 20.141.13.121, 20.141.15.104, 52.127.55.131, 52.235.252.252, 52.235.252.253, 52.243.247.124, 52.245.155.139, 52.245.156.185, 62.10.196.24, 62.10.196.25, 62.10.84.240, 62.11.6.64, 62.11.6.65 |
+   | USGov | All US Government Cloud regions | 20.140.104.48, 20.140.105.3, 20.140.144.58, 20.140.144.59, 20.140.147.168, 20.140.53.121, 20.141.10.130, 20.141.10.131, 20.141.13.121, 20.141.15.104, 52.127.55.131, 52.235.252.252, 52.235.252.253, 52.243.247.124, 52.245.155.139, 52.245.156.185, 62.10.84.240 |
 
    > [!IMPORTANT]
    > - The IPs that need to be permitted are specific to the region where the VM is located. For example, a virtual machine deployed in the North Europe region needs to add the following IP exclusions to the storage account firewall for the Europe geography: 52.146.139.220 and 20.105.209.72. View the table above to find the correct IPs for your region and geography.

support/entra/entra-id/app-integration/error-code-aadsts50173-grant-expired-revoked.md

@@ -45,10 +45,10 @@ On the application that experiences the issues, try to locate an option to reaut
 
 If the application is using [Microsoft Authentication Library (MSAL)](/entra/identity-platform/msal-overview), follow [this guidance to handle errors and exceptions in MSAL](/entra/msal/dotnet/advanced/exceptions/msal-error-handling).
 
-If the application isn't using [Microsoft Authentication Library (MSAL)](/entra/identity-platform/msal-overview), follow this guidance to [handle errors and exceptions in MSAL](/entra/msal/dotnet/advanced/exceptions/msal-error-handling), and try to implement a similar approach on the application. The goal is to request that the user reauthenticate and obtain a fresh token.
+If the application isn't using MSAL, follow this guidance to [handle errors and exceptions in MSAL](/entra/msal/dotnet/advanced/exceptions/msal-error-handling), and try to implement a similar approach on the application. The goal is to request that the user reauthenticate and obtain a fresh token.
 
 ## More information
 
 For a full list of authentication and authorization error codes, see [Microsoft Entra authentication and authorization error codes](/entra/identity-platform/reference-error-codes). 
 
-To investigate individual errors, go to [https://login.microsoftonline.com/error](https://login.microsoftonline.com/error).
+To investigate individual errors, go to [https://login.microsoftonline.com/error](https://login.microsoftonline.com/error).

support/power-platform/dataverse/d365-app-outlook/error-incomingemailrejected-install-dynamics-365-app-outlook.md

@@ -1,36 +1,67 @@
 ---
-title: IncomingEmailS2SApprovalNeeded when you install Dynamics 365 App for Outlook
-description: This article provides a resolution for the problem that occurs when you attempt to install Dynamics 365 App for Outlook, the Status column shows Issue when adding to Outlook.
+title: IncomingEmailS2SApprovalNeeded or IncomingEmailRejected when installing Dynamics 365 App for Outlook
+description: Solves errors that occur when you try to install Microsoft Dynamics 365 App for Outlook.
 ms.reviewer: 
-ms.topic: troubleshooting
-ms.date: 03/31/2021
+ms.date: 03/12/2025
 ms.custom: sap:Dynamics 365 App for Outlook Add-In
 ---
-# IncomingEmailS2SApprovalNeeded error when attempting to install Dynamics 365 App for Outlook
+# IncomingEmailS2SApprovalNeeded or IncomingEmailRejected error when you install Dynamics 365 App for Outlook
 
-This article helps you resolve the problem that occurs when you attempt to install Dynamics 365 App for Outlook, the Status column shows **Issue when adding to Outlook**.
+This article helps you resolve errors that might occur when you try to install Microsoft Dynamics 365 App for Outlook.
 
 _Applies to:_   Dynamics 365 App for Outlook  
-_Original KB number:_   3211621  
+_Original KB number:_   3211621, 3211627  
 
-## Symptoms
+## Error: IncomingEmailS2SApprovalNeeded
 
-When you attempt to install Dynamics 365 App for Outlook, the Status column shows **Issue when adding to Outlook**. When you click the **Learn more** link, you see a dialog with the following details:
+When you try to [install Dynamics 365 App for Outlook](/dynamics365/outlook-app/deploy-dynamics-365-app-for-outlook), the **Status** column shows **Issue when adding to Outlook**. When you select the **Learn more** link, you see a dialog with the following details:
 
 > There was an issue when attempting to add the app to Outlook.  
-Crm : IncomingEmailS2SApprovalNeeded
+> Crm : IncomingEmailS2SApprovalNeeded
 
-## Cause
+### Cause
 
-This error can occur if the Mailbox record has not been approved by an Office 365 Global Administrator.
+This error can occur if the mailbox record isn't approved by a Microsoft 365 Global Administrator.
 
-## Resolution
+### Resolution
 
-Approve the Mailbox record as a user with the Global Administrator role in Office 365.
+To solve this issue, approve the mailbox record as a user with the Global Administrator role in Microsoft 365.
 
-1. Sign in to Dynamics 365 as a user with the Global Administrator role in Office 365.
-2. Click **Settings** and then click **Email Configuration**.
-3. Within the **Email Configuration** area, click **Mailboxes** and then change the view from **My Active Mailboxes** to **Active Mailboxes**.
-4. Select the Mailbox record that encountered the error and then click **Approve Email**.
-5. After the email address has been approved, click the **Test & Enable Mailboxes** button.
-6. After the mailbox has completed testing, attempt to install Dynamics 365 App for Outlook again. This can be located by clicking **Settings** and then clicking Dynamics 365 App for Outlook.
+1. Sign in to Dynamics 365 as a user with the Global Administrator role in Microsoft 365.
+2. Select **Settings** > **Email Configuration**.
+
+3. Within the **Email Configuration** area, select **Mailboxes**, and then change the view from **My Active Mailboxes** to **Active Mailboxes**.
+
+4. Select the mailbox record that encountered the error, and then select **Approve Email**.
+5. After the email address is approved, select the **Test & Enable Mailboxes** button.
+
+6. After the mailbox has completed testing, try to install Dynamics 365 App for Outlook again. This can be located by selecting **Settings** > **Dynamics 365 App for Outlook**.
+
+## Error: IncomingEmailRejected
+
+When you try to install Dynamics 365 App for Outlook, the **Status** column shows **Issue when adding to Outlook**. When you select the **Learn more** link, you see a dialog with the following details:
+
+> There was an issue when attempting to add the app to Outlook.  
+> Crm : IncomingEmailRejected
+
+### Cause
+
+This error can occur due to one of the following reasons:
+
+- The email address for the mailbox record in Dynamics 365 isn't approved.
+- The Exchange mailbox is currently linked to another Dynamics 365 organization. An Exchange mailbox (email address) can only synchronize appointments, contacts, and tasks with one organization, and a user that belongs to that organization can only synchronize appointments, contacts, and tasks with one Exchange mailbox.
+
+### Resolution
+
+Verify the email address for the mailbox is approved and associated with the desired Dynamics 365 organization.
+
+1. Sign in to Dynamics 365 as a user with the System Administrator role.
+2. Select **Settings** > **Email Configuration**.
+
+3. Within the **Email Configuration** area, select **Mailboxes**, and then change the view from **My Active Mailboxes** to **Active Mailboxes**.
+4. Select the mailbox record that encountered the error, and then select **Approve Email**.
+5. After the email address is approved, select the **Test & Enable Mailboxes** button.
+
+6. Within the **Test Email Configuration** dialog, make sure to select the [Sync items with Exchange from this Dynamics 365 Organization only, even if Exchange was set to sync with a different Organization](/dynamics365/customerengagement/on-premises/admin/when-would-want-use-check-box) checkbox, and then select **OK**.
+
+7. After the mailbox has completed testing, try to install Dynamics 365 App for Outlook again. This can be located by selecting **Settings** > **Dynamics 365 App for Outlook**.

support/power-platform/dataverse/d365-app-outlook/error-install-dynamics-365-app-outlook.md

@@ -40,9 +40,7 @@
       href: d365-app-outlook/errors-when-opening-365-app-outlook.md
     - name: Experience without Server-Side Synchronization
       href: d365-app-outlook/experience-without-server-side-synchronization.md
-    - name: IncomingEmailRejected error when installing App for Outlook
-      href: d365-app-outlook/error-incomingemailrejected-install-dynamics-365-app-outlook.md
-    - name: IncomingEmailS2SApprovalNeeded error when installing App for Outlook
+    - name: IncomingEmailS2SApprovalNeeded or IncomingEmailRejected error during installation
       href: d365-app-outlook/error-install-dynamics-365-app-outlook.md
     - name: Item level Server-Side Synchronization issues
       href: d365-app-outlook/troubleshoot-item-level-server-side-synchronization-issues.md

support/power-platform/dataverse/toc.yml

@@ -1,12 +1,12 @@
 ---
-title: Troubleshooting recovery queueing in an Always On availability group
+title: Troubleshooting recovery (redo) queueing in an Always On availability group
 description: This article helps you to troubleshoot problems that are related to recovery queueing in an Always On availability group. 
-ms.date: 02/10/2023
+ms.date: 03/11/2025
 ms.custom: sap:Always On Availability Groups (AG)
-ms.reviewer: ramakoni, v-jayaramanp
+ms.reviewer: ramakoni, v-jayaramanp, jopilov
 ---
 
-# Troubleshooting recovery queueing in an Always On availability group
+# Troubleshooting recovery (redo) queueing in an Always On availability group
 
 This article provides resolutions to problems related to recovery queueing.
 
@@ -28,7 +28,7 @@ For more information, see the [Data latency on secondary replica](/sql/database-
 
 ### Failover time is longer or RTO is exceeded
 
-Recovery Time Objective (RTO) is the maximum database downtime that an organization can handle. RTO also describes how quickly the organization can regain access to the database after an outage. If substantial recovery queueing is present on a secondary replica when a failover occurs, recovery may take longer. After recovery, the database will transition to the primary role and represent the state of the database that existed before the failover. A longer recovery time can delay how quickly production resumes after a failover.
+Recovery Time Objective (RTO) is the maximum database downtime that an organization can handle. RTO also describes how quickly the organization can regain access to the database after an outage. If substantial recovery queueing is present on a secondary replica when a failover occurs, recovery might take longer than the RTO. After recovery, the database will transition to the primary role and represent the state of the database that existed before the failover. A longer recovery time can delay how quickly production resumes after a failover.
 
 ### Various diagnostic features report availability group recovery queueing
 

support/sql/database-engine/availability-groups/troubleshooting-recovery-queuing-in-alwayson-availability-group.md

@@ -1,20 +1,20 @@
 ---
-title: Error 0x80004005 occurs when SSIS packages fail to run
+title: Error 0x80004005 When an SSIS Package Fails to Run as a SQL Agent Job
 description: This article helps you resolve the 0x80004005 error that might arise when you try to run SSIS packages by using the SQL Server Agent.
-ms.date: 04/18/2024
+ms.date: 03/11/2025
 author: prmadhes-msft
 ms.author: prmadhes
 ms.reviewer: jopilov, haiyingyu, v-jayaramanp
 ms.custom: sap:Database Connectivity and Authentication
 ---
 
-# Connectivity error 0x80004005 occurs from SQL Sever Agent SSIS failures
+# Connectivity error 0x80004005 occurs when you run an SSIS package as a SQL Agent job
 
-This article provides a resolution to a connectivity issue in which SQL Server Integration Services (SSIS) packages that use an SQL Agent fail to run.
+This article provides a solution to a connectivity issue in which SQL Server Integration Services (SSIS) packages that use SQL Server Agent fail to run.
 
 ## Symptoms
 
-When you try to run SSIS packages that use an SQL agent, the packages don't run, and you receive the following error messages:
+When you try to run an SSIS package as a SQL Server Agent job, the package doesn't run, and you receive the following error messages:
 
 > An OLE DB record is available. Source "Microsoft OLE DB Driver for SQL Server" Hresult. 0x80004005 Description "Protocol error in TDS stream".