Skip to content

Commit da09314

Browse files
authored
some changes
1 parent 5177ef4 commit da09314

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Http server returned Forbidden exception
33
description: Provides a solution to an error that occurs when you select the Test & Enable Mailbox button on a mailbox record in Dynamics 365.
44
ms.reviewer:
5-
ms.date: 12/26/2024
5+
ms.date: 12/30/2024
66
ms.custom: sap:Email and Exchange Synchronization
77
---
88
# "Http server returned Forbidden exception" error when testing a Dynamics 365 mailbox
@@ -55,7 +55,7 @@ Dynamics 365 communicates with Microsoft Exchange using Exchange Web Services (E
5555
> [!IMPORTANT]
5656
> After running this command, it might take up to 120 minutes before the setting change takes effect.
5757
58-
## Check if EWS is disabled at the organization level or if the EwsAllowList limits the EWS traffic if the issue occurs for all mailboxes
58+
## Check if EWS is disabled at the organization level or if the EwsAllowList limits the EWS traffic
5959
6060
1. Use this PowerShell command to check organization-level settings:
6161
@@ -72,7 +72,7 @@ Dynamics 365 communicates with Microsoft Exchange using Exchange Web Services (E
7272
> [!IMPORTANT]
7373
> After running this command, it might take up to 120 minutes before the setting change takes effect.
7474
75-
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):
75+
3. If `EwsApplicationAccessPolicy` is set to **EnforceAllowList**, check if the `EwsAllowList` contains a value for CRM (for example, CRM/\*) to allow Dynamics 365 (CRM) to communicate with Exchange. If it does not, use the following command to update the list to include CRM/* and any other applications you want to allow. In this example \<PreviousAllowedList> is the list of applications that were previously in the allowlist:
7676
7777
```powershell
7878
Set-OrganizationConfig -EwsApplicationAccessPolicy:EnforceAllowList -EwsAllowList:CRM/*,<PreviousAllowedList>
@@ -81,7 +81,7 @@ Dynamics 365 communicates with Microsoft Exchange using Exchange Web Services (E
8181
> [!IMPORTANT]
8282
> After running this command, it might take up to 120 minutes before the setting change takes effect.
8383
84-
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:
84+
4. If `EwsApplicationAccessPolicy` is set to **EnforceBlockList**, check if the `EwsBlockList` contains a value for CRM (for example, CRM/*), which prevents Dynamics 365 (CRM) from communicating with Exchange. If it does, use the following command to update the list to no longer include CRM. In this example \<PreviousBlockList WITH CRM REMOVED> is the list of applications that were previously in the blocklist except for CRM:
8585
8686
```powershell
8787
Set-OrganizationConfig -EwsApplicationAccessPolicy:EnforceBlockList -EwsBlockList:<PreviousBlockList WITH CRM REMOVED>

0 commit comments

Comments
 (0)