minor changes

Author: lucciz01

support/power-platform/dataverse/email-exchange-synchronization/http-server-returned-forbidden-exception.md

@@ -5,72 +5,72 @@ ms.reviewer:
 ms.date: 12/10/2024
 ms.custom: sap:Email and Exchange Synchronization
 ---
-# "Http server returned Forbidden exception" error appears in Microsoft Dynamics 365 mailbox
+# "Http server returned Forbidden exception" error when testing a Dynamics 365 mailbox
 
-This article provides a solution to an error that occurs when you select the **Test & Enable Mailbox** button on a mailbox record in Dynamics 365.
+This article provides a solution to an error that occurs when you select the **Test & Enable Mailbox** button on a mailbox record in Microsoft Dynamics 365.
 
 _Applies to:_   Microsoft Dynamics 365  
 _Original KB number:_   4483440
 
 ## Symptoms
 
-When you select the **Test & Enable Mailbox** button on a mailbox record in Dynamics 365, the test results section shows Failure and the following alert is logged:
+When you select the **Test & Enable Mailbox** button on a mailbox record in Dynamics 365, the test results section shows **Failure** and the following alert is logged:
 
-> "The email message "Your mailbox is now connected to Dynamics 365" cannot be sent because an error occurred while establishing a secure connection to the email server. Mailbox [Mailbox Name] didn't synchronize. The owner of the email server profile Microsoft Exchange Online has been notified.  
-Email Server Error Code: Http server returned Forbidden exception."
+> The email message "Your mailbox is now connected to Dynamics 365" cannot be sent because an error occurred while establishing a secure connection to the email server. Mailbox [Mailbox Name] didn't synchronize. The owner of the email server profile Microsoft Exchange Online has been notified.  
+> **Email Server Error Code**: Http server returned Forbidden exception.
 
-If you select **Details**, the following other details are shown:
+If you select **Details**, the following details are shown:
 
-> "Error : System.Net.WebException: The request failed with HTTP status 403: Forbidden.  
-   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)  
-   at System.Web.Services.Protocols.SoapHttpClientProtocol.EndInvoke(IAsyncResult asyncResult)  
-   at Microsoft.Crm.Asynchronous.EmailConnector.ExchangeServiceBinding.EndCreateItem(IAsyncResult asyncResult)  
-   at Microsoft.Crm.Asynchronous.EmailConnector.ExchangeOutgoingEmailProvider.EndCreateItem()"
+> Error : System.Net.WebException: The request failed with HTTP status 403: Forbidden.  
+> at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)  
+> at System.Web.Services.Protocols.SoapHttpClientProtocol.EndInvoke(IAsyncResult asyncResult)  
+> at Microsoft.Crm.Asynchronous.EmailConnector.ExchangeServiceBinding.EndCreateItem(IAsyncResult asyncResult)  
+> at Microsoft.Crm.Asynchronous.EmailConnector.ExchangeOutgoingEmailProvider.EndCreateItem()
 
 ## Cause
 
-Dynamics 365 communicates with Microsoft Exchange using Exchange Web Services (EWS) requests. If EWS is disabled, this error will occur. The following contents are some potential ways that EWS may be disabled or restricted in Exchange:
+Dynamics 365 communicates with Microsoft Exchange using Exchange Web Services (EWS) requests. If EWS is disabled, this error will occur. Here are some potential ways that EWS might be disabled or restricted in Exchange:
 
-1. EWS is disabled for the mailbox
-2. EWS is disabled for the entire organization
-3. The `EwsApplicationAccessPolicy` is set to **EnforceAllowList** and `the EwsAllowList` doesn't allow access from Dynamics 365 (CRM).
-4. The `EwsApplicationAccessPolicy` is set to **EnforceBlockList** and `the EwsBlockList` includes Dynamics 365 (CRM).
+1. EWS is disabled for the mailbox.
+2. EWS is disabled for the entire organization.
+3. The `EwsApplicationAccessPolicy` is set to **EnforceAllowList** and the `EwsAllowList` doesn't allow access from Dynamics 365.
+4. The `EwsApplicationAccessPolicy` is set to **EnforceBlockList** and the `EwsBlockList` includes Dynamics 365.
 
 ## Resolution
 
-**If the issue only occurs for some mailboxes, check if EWS is disabled for the mailbox:**
+### Check if EWS is disabled for the mailbox if the issue only occurs for some mailboxes
 
-1. First check to see if EWS has been disabled for the mailbox. Use the following PowerShell command:
+1. First, check if EWS is disabled for a specific mailbox using this PowerShell command:
 
     ```powershell
     Get-CASMailbox <mailbox-alias> | ft EwsEnabled
     ```
 
-2. If **EwsEnabled** is set to **False**, use the following PowerShell command to enable Exchange Web Services (EWS) for the mailbox:
+2. If **EwsEnabled** is set to **False**, enable it using this command:
 
     ```powershell
     Set-CASMailbox <mailbox-alias> -EwsEnabled $True
     ```
 
     > [!IMPORTANT]
-    > After running this command, it may take up to 120 minutes before the setting change takes effect.
+    > After running this command, it might take up to 120 minutes before the setting change takes effect.
 
- **If the issue occurs for all mailboxes, check if EWS is disabled at the organization level, or if the EwsAllowList is being used to limit what EWS traffic is allowed.**
+## Check if EWS is disabled at the organization level or if the EwsAllowList limits the EWS traffic if the issue occurs for all mailboxes
 
-1. Use the following PowerShell command to see if any of the EWS settings are configured:
+1. Use this PowerShell command to check organization-level settings:
 
     ```powershell
     Get-OrganizationConfig |ft Name, EwsEnabled,EwsApplicationAccessPolicy,EwsBlockList,EwsAllowList
     ```
 
-2. Verify that **EwsEnabled** isn't set to **False**. The following command can be used to set **EwsEnabled** to **True** if it's currently set to **False**:
+2. Ensure that `EwsEnabled` isn't set to **False**. If it is, enable it using:
 
     ```powershell
     Set-OrganizationConfig -EwsEnabled $True
     ```
 
     > [!IMPORTANT]
-    > After running this command, it may take up to 120 minutes before the setting change takes effect.
+    > After running this command, it might take up to 120 minutes before the setting change takes effect.
 
 3. If `EwsApplicationAccessPolicy` is set to **EnforceAllowList** and the `EwsAllowList` doesn't contain a value for CRM (Example: CRM/\*), which would prevent Dynamics 365 (CRM) from being able to communicate with Exchange. Use the following command to update the list to include CRM/* and whatever other applications you want to allow (\<PreviousAllowList> in the following example):
 
@@ -79,16 +79,16 @@ Dynamics 365 communicates with Microsoft Exchange using Exchange Web Services (E
     ```
 
     > [!IMPORTANT]
-    > After running this command, it may take up to 120 minutes before the setting change takes effect.
+    > After running this command, it might take up to 120 minutes before the setting change takes effect.
 
-4. If `EwsApplicationAccessPolicy` is set to **EnforceBlockList** and the **EwsAllowList** contains a value for CRM (Example: CRM/*), which would prevent Dynamics 365 (CRM) from being able to communicate with Exchange. Use the following command to update the list to no longer include CRM:
+4. If `EwsApplicationAccessPolicy` is set to **EnforceBlockList** and the `EwsAllowList` contains a value for CRM (Example: CRM/*), which would prevent Dynamics 365 (CRM) from being able to communicate with Exchange. Use the following command to update the list to no longer include CRM:
 
     ```powershell
     Set-OrganizationConfig -EwsApplicationAccessPolicy:EnforceBlockList -EwsBlockList:<PreviousBlockList WITH CRM REMOVED>
     ```
 
     > [!IMPORTANT]
-    > After running this command, it may take up to 120 minutes before the setting change takes effect.
+    > After running this command, it might take up to 120 minutes before the setting change takes effect.
 
 ## More information