Updates from editor

Author: Celiazhou1

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

@@ -2,7 +2,7 @@
 title: Http server returned Forbidden exception
 description: Provides a solution to an error that occurs when you select the Test & Enable Mailbox button on a mailbox record in Dynamics 365.
 ms.reviewer: 
-ms.date: 12/10/2024
+ms.date: 12/26/2024
 ms.custom: sap:Email and Exchange Synchronization
 ---
 # "Http server returned Forbidden exception" error when testing a Dynamics 365 mailbox
@@ -29,7 +29,7 @@ If you select **Details**, the following details are shown:
 
 ## Cause
 
-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:
+Dynamics 365 communicates with Microsoft Exchange using Exchange Web Services (EWS) requests. If EWS is disabled, this error occurs. 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.
@@ -72,7 +72,7 @@ Dynamics 365 communicates with Microsoft Exchange using Exchange Web Services (E
     > [!IMPORTANT]
     > 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):
+3. If `EwsApplicationAccessPolicy` is set to **EnforceAllowList** and the `EwsAllowList` doesn't contain a value for CRM (for example, CRM/\*), which prevents Dynamics 365 (CRM) from communicating with Exchange. Use the following command to update the list to include CRM/* and any other applications you want to allow (\<PreviousAllowList> in the following example):
 
     ```powershell
     Set-OrganizationConfig -EwsApplicationAccessPolicy:EnforceAllowList -EwsAllowList:CRM/*,<PreviousAllowedList>
@@ -81,7 +81,7 @@ Dynamics 365 communicates with Microsoft Exchange using Exchange Web Services (E
     > [!IMPORTANT]
     > 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 (for example, CRM/*), which prevents Dynamics 365 (CRM) from communicating 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>