minor changes

Author: lucciz01

support/power-platform/dataverse/email-exchange-synchronization/exception-appears-server-side-sync.md

@@ -1,34 +1,34 @@
 ---
-title: UnknownIncomingEmailIntegrationError appears in server-side synchronization
-description: Solves the UnknownIncomingEmailIntegrationError that occurs in a Microsoft Dynamics 365 mailbox record.
+title: UnknownIncomingEmailIntegrationError logged during server-side synchronization
+description: Solves the UnknownIncomingEmailIntegrationError that's logged in a Microsoft Dynamics 365 mailbox record.
 ms.reviewer: 
 ms.date: 12/20/2024
 ms.custom: sap:Email and Exchange Synchronization
 ---
-# UnknownIncomingEmailIntegrationError appears in mailbox alerts in Microsoft Dynamics 365
+# UnknownIncomingEmailIntegrationError logged in mailbox alerts in Microsoft Dynamics 365
 
-This article provides a solution to an error that occurs within mailbox alerts in Microsoft Dynamics 365.
+This article provides a solution to an `UnknownIncomingEmailIntegrationError` error code that's logged in mailbox alerts in Microsoft Dynamics 365.
 
 _Applies to:_   Microsoft Dynamics 365  
 _Original KB number:_   4471762
 
 ## Symptoms
 
-When [viewing the alerts section](/power-platform/admin/monitor-email-processing-errors#view-alerts) within a mailbox record in Dynamics 365, you see the following message:
+When [viewing the Alerts section](/power-platform/admin/monitor-email-processing-errors#view-alerts) within a mailbox record in Dynamics 365, you might see the following message:
 
 > An unknown error occurred while receiving email through the mailbox "\<Mailbox Name>". The owner of the associated email server profile \<Profile Name> has been notified. The system will try to receive email again later.
 >
 > **Email Server Error Code:** Exchange server returned UnknownIncomingEmailIntegrationError -2147220956 exception.
 
 ## Cause
 
-The error code indicates an IsvUnexpected error. It typically indicates that a custom plugin or workflow throws an error and causing the creation of the item to fail.
+The error code indicates an IsvUnexpected error. It typically means that a custom plugin or workflow throws an error, causing the creation of the item to fail.
 
 ## Resolution
 
-To solve this issue, check if any custom plugins or workflows are running synchronously when creating the record type (email, appointment, contact, or task) mentioned in the error. If a plugin or workflow is causing an error during record creation, server-side synchronization can't create the record successfully.
+To solve this issue, check if any custom plugins or workflows are running synchronously when creating the record type (email, appointment, contact, or task) mentioned in the error. If a plugin or workflow causes an error during record creation, [server-side synchronization](/power-platform/admin/server-side-synchronization) can't create the record successfully.
 
-The following steps can help you identify if there are any workflows or plugins in your organization that run during the creation of an email. Use the same steps for other entities like appointments and tasks by replacing the Entity with the appropriate record type.
+The following steps can help you identify any workflows or plugins in your organization running during the email creation. These steps can also be used for other entities like appointments and tasks by replacing `Entity` with the appropriate record type.
 
 ### Workflow
 
@@ -42,9 +42,9 @@ The following steps can help you identify if there are any workflows or plugins
 5. If the **Start when** options have the **Record is created** option selected, and the **Run this workflow in the background (recommended)** option isn't selected, this workflow might be the cause.
 
     > [!NOTE]
-    > If you're troubleshooting this type of error with an Appointment, Contact, or Task, also check if the workflow is configured to run during update of that type of record.
+    > If you're troubleshooting this type of error with an appointment, contact, or task, also check if the workflow is configured to run during update of that type of record.
 
-6. Select the **Process Sessions** section on the left side of the page and look for any failures related to the email that wasn't created successfully.
+6. Select **Process Sessions** on the left side of the page and look for failures related to successfully created email.
 
 ### Plugin
 
@@ -59,7 +59,7 @@ If you're able to reproduce the issue consistently, you can try disabling the wo
 
 |Email Server Error Code|Cause|Resolution|
 |--|--|--|
-|-2147220970|This warning might appear if Server-Side Synchronization attempted to retrieve emails but encountered an unexpected error. This is typically a temporary issue and the emails will be retrieved successfully on the next synchronization cycle (typically 15 minutes).|If this message does not persist on the next synchronization cycle (typically 15 minutes), this warning can be ignored. If this message persists, you can contact Microsoft Support.|
-|-2147218677|This error occurs if there was an invalid email address included on the To or Cc line of the email.|Review the email message that encountered this error and verify all email addresses on the To and Cc lines are [valid email addresses](https://tools.ietf.org/html/rfc5322#section-3.4.1).|
-|-2147220192|Error -2147220192 indicates the owner of the queue does not have sufficient privileges to work with the queue. The user is likely missing sufficient Read access to the Queue entity.|Verify the user's Microsoft Dynamics 365 security role has Read access to the Queue entity. Within a Microsoft Dynamics 365 security role, privileges for the Queue entity are located on the Core Records tab. <br> **NOTE**: If you verify the owner of the mailbox record has Read access to the Queue entity, check if there are other Microsoft Dynamics 365 users or queues that received the same email. You may need to verify privileges for those users as well.|
-|-2147167669|This warning is logged if the owner of the mailbox record does not have a Microsoft Dynamics 365 license assigned.|Verify the owner of the mailbox has a Microsoft Dynamics 365 license assigned.<br> **NOTE**: If you verify the user does have a license, verify there are not any other Microsoft Dynamics 365 mailbox records with the same email address. If there is another mailbox with the same email address and the owner of that mailbox does not have a license, change the email address value in the other mailbox record.|
+|UnknownIncomingEmailIntegrationError -2147220970|This error might occur if [server-side synchronization](/power-platform/admin/server-side-synchronization) tries to retrieve emails but receives an unexpected error. This is typically a temporary issue and the emails will be retrieved successfully on the next synchronization cycle (typically 15 minutes.)|If this message doesn't persist on the next synchronization cycle (typically 15 minutes), this warning can be ignored. If this message persists, you can contact Microsoft Support through the **Help + Support** experience in the [Power Platform admin center](https://admin.powerplatform.microsoft.com/support).|
+|UnknownIncomingEmailIntegrationError -2147218677|This error occurs if an invalid email address is included on the **To** or **Cc** line of the email.|Review the email message that receives this error and verify all email addresses on the **To** and **Cc** lines are [valid email addresses](https://tools.ietf.org/html/rfc5322#section-3.4.1).|
+|UnknownIncomingEmailIntegrationError -2147220192|This error indicates the owner of the queue doesn't have sufficient privileges to work with the queue. The user is likely missing sufficient **Read** access to the `Queue` entity.|Verify the user's Dynamics 365 security role has **Read** access to the `Queue` entity. Within a Dynamics 365 security role, privileges for the `Queue` entity are located on the **Core Records** tab. <br> **NOTE**: If you verify the owner of the mailbox record has **Read** access to the `Queue` entity, check if there are other Dynamics 365 users or queues that receive the same email. You might need to verify privileges for those users as well.|
+|UnknownIncomingEmailIntegrationError -2147167669|This error is logged if the owner of the mailbox record doesn't have a Dynamics 365 license assigned.|Verify the owner of the mailbox has a Dynamics 365 license assigned.<br> **NOTE**: If you verify that the user has a license, verify there aren't any other Dynamics 365 mailbox records with the same email address. If there's another mailbox with the same email address and the owner of that mailbox doesn't have a license, change the email address value in the other mailbox record.|