You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/power-platform/dataverse/email-exchange-synchronization/http-server-returned-forbidden-exception.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Http server returned Forbidden exception
3
3
description: Provides a solution to an error that occurs when you select the Test & Enable Mailbox button on a mailbox record in Dynamics 365.
4
4
ms.reviewer:
5
-
ms.date: 12/26/2024
5
+
ms.date: 12/30/2024
6
6
ms.custom: sap:Email and Exchange Synchronization
7
7
---
8
8
# "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
55
55
> [!IMPORTANT]
56
56
> After running this command, it might take up to 120 minutes before the setting change takes effect.
57
57
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
59
59
60
60
1. Use this PowerShell command to check organization-level settings:
61
61
@@ -72,7 +72,7 @@ Dynamics 365 communicates with Microsoft Exchange using Exchange Web Services (E
72
72
> [!IMPORTANT]
73
73
> After running this command, it might take up to 120 minutes before the setting change takes effect.
74
74
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:
@@ -81,7 +81,7 @@ Dynamics 365 communicates with Microsoft Exchange using Exchange Web Services (E
81
81
> [!IMPORTANT]
82
82
> After running this command, it might take up to 120 minutes before the setting change takes effect.
83
83
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:
85
85
86
86
```powershell
87
87
Set-OrganizationConfig -EwsApplicationAccessPolicy:EnforceBlockList -EwsBlockList:<PreviousBlockList WITH CRM REMOVED>
0 commit comments