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/azure/azure-kubernetes/create-upgrade-delete/error-code-outboundconnfailvmextensionerror.md
+5-4Lines changed: 5 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Troubleshoot the OutboundConnFailVMExtensionError error code (50)
3
3
description: Learn how to troubleshoot the OutboundConnFailVMExtensionError error (50) when you try to start or create and deploy an Azure Kubernetes Service (AKS) cluster.
ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool)
@@ -111,12 +111,13 @@ There are many reasons why the traffic might be blocked. In any of these situati
111
111
> ```
112
112
## Solution
113
113
114
-
The following table lists specific reasons why traffic might be blocked, and the corresponding solution for each reason.
114
+
The following table lists specific reasons why traffic might be blocked, and the corresponding solution for each reason:
115
+
115
116
| Issue | Solution |
116
117
| ----- | -------- |
117
-
| Traffic is blocked by firewall rules, a proxy server or Network Security Group (NSG) | This issue occurs when the AKS required ports or Fully Qualified Domain Names (FQDNs) are blocked by a firewall, proxy server, or NSG. Ensure these ports and FQDNs are allowed. To determine what's blocked, check the connectivity provided in the preceeding [Cause](#cause) section. For more information about AKS required ports and FQDNs, see [Outbound network and FQDN rules for Azure Kubernetes Service (AKS) clusters](/azure/aks/outbound-rules-control-egress).|
118
+
| Traffic is blocked by firewall rules, a proxy server or Network Security Group (NSG) | This issue occurs when the AKS required ports or Fully Qualified Domain Names (FQDNs) are blocked by a firewall, proxy server, or NSG. Ensure these ports and FQDNs are allowed. To determine what's blocked, check the connectivity provided in the preceding [Cause](#cause) section. For more information about AKS required ports and FQDNs, see [Outbound network and FQDN rules for Azure Kubernetes Service (AKS) clusters](/azure/aks/outbound-rules-control-egress).|
118
119
| The AAAA (IPv6) record is blocked on the firewall | On your firewall, verify that nothing exists that would block the endpoint from resolving in Azure DNS. |
119
-
| Private cluster can't resolve internal Azure resources | In private clusters, the Azure DNS IP address (`168.63.129.16`) must be added as an upstream DNS server if custom DNS is used. Verify that the address is set on your DNS servers. For more information, see [Create a private AKS cluster](/azure/aks/private-clusters) and [What is IP address 168.63.129.16?](/azure/virtual-network/what-is-ip-address-168-63-129-16) |
120
+
| Private cluster can't resolve internal Azure resources | In private clusters, the Azure DNS IP address (`168.63.129.16`) must be added as an upstream DNS server if custom DNS is used. Verify that the address is set on your DNS servers. For more information, see [Create a private AKS cluster](/azure/aks/private-clusters) and [What is IP address 168.63.129.16?](/azure/virtual-network/what-is-ip-address-168-63-129-16). |
Copy file name to clipboardExpand all lines: support/azure/azure-kubernetes/error-codes/vmextensionerror-outboundconnfail.md
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Troubleshoot the VMExtensionError_OutboundConnFail error code
3
3
description: Learn how to troubleshoot the VMExtensionError_OutboundConnFail error (50) when you try to start or create and deploy an Azure Kubernetes Service (AKS) cluster.
ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool)
@@ -115,12 +115,11 @@ There are many reasons why the traffic might be blocked. In any of these situati
115
115
116
116
## Solution
117
117
118
-
The following table lists specific reasons why traffic might be blocked, and the corresponding solution for each reason.
118
+
The following table lists specific reasons why traffic might be blocked, and the corresponding solution for each reason:
119
119
120
120
| Issue | Solution |
121
121
| ----- | -------- |
122
-
| Traffic is blocked by firewall rules or a proxy server | In this scenario, a firewall or a proxy server does egress filtering. To verify that all required domains and ports are allowed, see [Control egress traffic for cluster nodes in Azure Kubernetes Service (AKS)](/azure/aks/limit-egress-traffic). |
123
-
| Traffic is blocked by a cluster network security group (NSG) | On any NSGs that are attached to your cluster, verify that there's no blocking on port 443, port 53, or any other port that might have to be used to connect to the endpoint. For more information, see [Control egress traffic for cluster nodes in Azure Kubernetes Service (AKS)](/azure/aks/limit-egress-traffic). |
122
+
| Traffic is blocked by firewall rules, a proxy server or Network Security Group (NSG) | This issue occurs when the AKS required ports or Fully Qualified Domain Names (FQDNs) are blocked by a firewall, proxy server, or NSG. Ensure these ports and FQDNs are allowed. To determine what's blocked, check the connectivity provided in the preceding [Cause](#cause) section. For more information about AKS required ports and FQDNs, see [Outbound network and FQDN rules for Azure Kubernetes Service (AKS) clusters](/azure/aks/outbound-rules-control-egress).|
124
123
| The AAAA (IPv6) record is blocked on the firewall | On your firewall, verify that nothing exists that would block the endpoint from resolving in Azure DNS. |
125
124
| Private cluster can't resolve internal Azure resources | In private clusters, the Azure DNS IP address (`168.63.129.16`) must be added as an upstream DNS server if custom DNS is used. Verify that the address is set on your DNS servers. For more information, see [Create a private AKS cluster](/azure/aks/private-clusters) and [What is IP address 168.63.129.16?](/azure/virtual-network/what-is-ip-address-168-63-129-16) |
description: Provides a solution to an error that occurs after you select the Test & Enable Mailbox button in Microsoft Dynamics 365.
2
+
title: Email message cannot be sent MailboxDisabled error
3
+
description: Provides a solution to a MailboxDisabled error that occurs when you try to test and enable a mailbox in Microsoft Dynamics 365.
4
4
ms.reviewer:
5
-
ms.topic: troubleshooting
6
-
ms.date: 11/19/2024
5
+
ms.date: 12/30/2024
7
6
ms.custom: sap:Email and Exchange Synchronization
8
7
---
9
-
# The email message "Your mailbox is now connected to Dynamics 365" cannot be sent because the mailbox [Mailbox Name] is deactivated or disabled for outgoing email
8
+
# MailboxDisabled error when you test and enable a mailbox in Dynamics 365
10
9
11
-
This article provides a solution to an error that occurs after you select the **Test & Enable Mailbox** button in Microsoft Dynamics 365.
10
+
This article provides a solution to a MailboxDisabled error that occurs when you try to test and enable a mailbox in Microsoft Dynamics 365.
12
11
13
12
_Applies to:_ Microsoft Dynamics 365
14
13
_Original KB number:_ 4481318
15
14
16
15
## Symptoms
17
16
18
-
After you select the **Test & Enable Mailbox** button in Dynamics 365, the tests fail and the following alert is logged:
17
+
When you try to [test and enable a mailbox](/power-platform/admin/connect-exchange-online#test-the-configuration-of-mailboxes) in Dynamics 365, the test fails, and the following alert is logged:
19
18
20
-
> "The email message "Your mailbox is now connected to Dynamics 365" cannot be sent because the mailbox [Mailbox Name] is deactivated or disabled for outgoing email.
21
-
**Email Server Error Code:** MailboxDisabled"
19
+
> The email message "Your mailbox is now connected to Dynamics 365" cannot be sent because the mailbox \<Mailbox Name\> is deactivated or disabled for outgoing email.
20
+
> **Email Server Error Code:** MailboxDisabled
22
21
23
22
## Cause
24
23
25
-
This error occurs if the mailbox is deactivated and the status is now Inactive.
24
+
This error occurs if the mailbox is deactivated and the status is **Inactive**.
26
25
27
-
A mailbox could have been deactivated by someone selecting the **Deactivate** button. If it's a user mailbox, the mailbox could have been deactivated automatically if the regarding user was deactivated. For example: If you remove a user's Dynamics 365 license, the user will be deactivated and also their mailbox record.
26
+
A mailbox can be deactivated if someone selects the **Deactivate** button. If it's a user mailbox, the mailbox can also be deactivated automatically when the user is deactivated. For example, if you remove a user's Dynamics 365 license, the user and their mailbox record will be deactivated.
28
27
29
28
## Resolution
30
29
31
-
1. Select the **Activate** button on the mailbox record and verify the status shown in the footer of the page shows as**Active**.
30
+
1. Select the **Activate** button on the mailbox record and verify that the status shown in the footer of the page is**Active**.
32
31
2. Select the **Test & Enable Mailbox** button.
33
-
3. If the tests don't succeed, review the alerts that appear.
32
+
3. If the test doesn't succeed, review the alerts that appear.
34
33
35
34
> [!IMPORTANT]
36
-
> If the mailbox had been deactivated because the associated user was disabled, you should also make sure the user is enabled with a valid [Dynamics 365 license](/power-platform/admin/wp-license-management#assign-a-license-to-a-user) and [security role](/power-platform/admin/create-users-assign-online-security-roles#assign-a-security-role-to-a-user).
35
+
> If the mailbox was deactivated because the associated user was disabled, ensure the user is re-enabled with a valid [Dynamics 365 license](/power-platform/admin/wp-license-management#assign-a-license-to-a-user) and [security role](/power-platform/admin/create-users-assign-online-security-roles#assign-a-security-role-to-a-user).
When attempting to test and enable a mailbox in Dynamics 365, the results show as failure and the following error alerts appear:
17
+
When you try to [test and enable a mailbox](/power-platform/admin/connect-exchange-online#test-the-configuration-of-mailboxes) in Dynamics 365, the test results section shows **Failure**, and one of the following alerts is logged:
19
18
20
-
> "The mailbox location could not be determined while sending the email message "Your mailbox is now connected to Dynamics 365". Mailbox [Mailbox Name] didn't synchronize. The owner of the associated email server profile [Email Server Profile Name] has been notified."
21
-
22
-
> "The location of the mailbox [Mailbox Name] could not be determined while receiving email. The owner of the associated email server profile [Email Server Profile Name] has been notified. The system will try to receive email again later."
19
+
-> The mailbox location could not be determined while sending the email message "Your mailbox is now connected to Dynamics 365". Mailbox \<Mailbox Name\> didn't synchronize. The owner of the associated email server profile \<Email Server Profile Name\> has been notified.
20
+
-> The location of the mailbox \<Mailbox Name\> could not be determined while receiving email. The owner of the associated email server profile \<Email Server Profile Name\> has been notified. The system will try to receive email again later.
23
21
24
22
## Cause
25
23
26
-
This error can occur when you're connecting to Exchange on-premises and the Email Server Profile record in Dynamics 365 is configured with the **Auto Discover Server Location** setting set to **Yes**. When this option is selected, you don't provide your Exchange Web Services URL. Instead, Dynamics 365 tries to use the [Autodiscover for Exchange](/exchange/client-developer/exchange-web-services/autodiscover-for-exchange) to retrieve the correct location. If there are issues with the autodiscover service or it isn't configured correctly, this error can occur.
24
+
The alerts can occur when connecting to Exchange on-premises and the email server profile record in Dynamics 365 is configured with the **Auto Discover Server Location** setting set to **Yes**. When this option is enabled, you don't need to provide your Exchange Web Services (EWS) URL. Instead, Dynamics 365 tries to use [Autodiscover for Exchange](/exchange/client-developer/exchange-web-services/autodiscover-for-exchange) to retrieve the correct location. If there are issues with the Autodiscover service or it isn't configured correctly, the alerts might occur.
27
25
28
26
## Resolution
29
27
30
-
Either fix the autodiscover issue with Exchange or change the **Auto Discover Server Location** setting to **No**, and provide the Exchange Web Service URL. Use the steps below to change the Auto Discover Server Location setting.
31
-
32
-
1. Access the Dynamics 365 web application as a user with the System Administrator security role.
33
-
2. Navigate to **Settings** and then select **Email Configuration**.
34
-
3. Select **Email Server Profiles**.
35
-
4. Open your email server profile record for your Exchange on-premises configuration.
36
-
5. Change the **Auto Discover Server Location** setting to **No.**
37
-
6. Set the **Incoming Server Location** and **Outgoing Server Location** settings to your Exchange Web Services URL.
38
-
For example: `https://mail.yourdomain.com/EWS/Exchange.asmx`
39
-
7. Select **Save**.
40
-
8. Try to test and enable the mailboxes again.
28
+
To resolve this issue, you can either fix the Autodiscover issue with Exchange or change the **Auto Discover Server Location** setting to **No** and provide the EWS URL.
29
+
30
+
Follow these steps to change the **Auto Discover Server Location** setting:
31
+
32
+
1. Sign in to the Dynamics 365 web application as a user with the "System Administrator" security role.
33
+
2. Navigate to **Settings** > **Email Configuration** > **Email Server Profiles**.
34
+
3. Open your email server profile record for your Exchange on-premises configuration.
35
+
4. Change the **Auto Discover Server Location** setting to **No**.
36
+
37
+
5. Enter your EWS URL in the **Incoming Server Location** and **Outgoing Server Location** fields. For example, `https://mail.yourdomain.com/EWS/Exchange.asmx`.
38
+
39
+
6. Select **Save**.
40
+
7.[Test and enable the mailbox](/power-platform/admin/connect-exchange-online#test-the-configuration-of-mailboxes) again.
When you attempt to test and enable a mailbox in Microsoft Dynamics 365, you receive the following error:
17
+
When you try to [test and enable a mailbox](/power-platform/admin/connect-exchange-online#test-the-configuration-of-mailboxes) in Microsoft Dynamics 365, you receive the following error:
19
18
20
-
> "An unknown error occurred while sending the email message "Your mailbox is now connected to Dynamics 365". Mailbox \<Mailbox Name> didn't synchronize. The owner of the associated email server profile \<Profile Name> has been notified."
19
+
> An unknown error occurred while sending the email message "Your mailbox is now connected to Dynamics 365". Mailbox \<Mailbox Name> didn't synchronize. The owner of the associated email server profile \<Profile Name> has been notified.
21
20
22
-
If you select the **Details** section, you may also see more details such as the following text:
21
+
If you select the **Details** section, you might find the following details:
23
22
24
-
> "Error : System.Net.Mail.SmtpException: Syntax error, command unrecognized. The server response was:
25
-
at System.Net.Mail.SmtpConnection.ConnectAndHandshakeAsyncResult.End(IAsyncResult result)
26
-
at System.Net.Mail.SmtpTransport.EndGetConnection(IAsyncResult result)
27
-
at System.Net.Mail.SmtpClient.ConnectCallback(IAsyncResult result)"
23
+
> Error : System.Net.Mail.SmtpException: Syntax error, command unrecognized. The server response was:
> at System.Net.Mail.SmtpClient.ConnectCallback(IAsyncResult result)
28
27
29
28
## Cause
30
29
31
-
This error can occur if the Outgoing Port value within the Advanced section of the email server profile isn't correct.
30
+
This error can occur if the **Outgoing Port** value in the **Advanced** section of the email server profile isn't correct.
32
31
33
32
## Resolution
34
33
35
34
To fix this issue, follow these steps:
36
35
37
-
1. Navigate to **Settings**, **Email Configuration**, and then select **Email Server Profiles**.
38
-
2. Open the Email Server Profile that is used by the mailbox meeting this error.
36
+
1. Sign in to your Dynamics 365 organization with a user account that has the "System Administrator" role.
37
+
1. Navigate to **Settings** > **Email Configuration**, and then select **Email Server Profiles**.
38
+
39
+
1. Open the email server profile that's used by the mailbox receiving this error.
39
40
40
41
> [!NOTE]
41
-
> You can also select the name of the Email Server Profile within the error message. It appears as a hyperlink which will open the correct Email Server Profile record.
42
+
> You can also select the name of the email server profile in the error message. It appears as a hyperlink that will open the correct email server profile record.
42
43
43
-
3. Select **Advanced**.
44
-
4. Correct the **Outgoing Port** value and then select **Save**.
44
+
1. Select **Advanced**.
45
+
1. Correct the **Outgoing Port** value and then select **Save**.
45
46
46
47
> [!NOTE]
47
-
> Refer to the documentation from your email provider for the correct ports to use when connecting to the SMTP service. For [Gmail](https://support.google.com/mail/answer/7104828) the port is 587.
48
+
> Refer to the documentation from your email provider for the correct ports when connecting to the SMTP service. For example, for [Gmail](https://support.google.com/mail/answer/7104828), use port 587 for TLS/STARTTLS connections.
49
+
50
+
1. Select **Mailboxes**, and then select the mailbox that received the error.
51
+
1. Select the **Test & Enable Mailboxes** button.
48
52
49
-
5. Select **Mailboxes** and then select the mailbox that received the error.
50
-
6. Select the **Test & Enable Mailboxes** button.
51
-
7. After the tests complete, open the mailbox record and view the **Alerts** section if the results don't appear as Success.
53
+
1. After the test is complete, open the mailbox record and view the **Alerts** section if the results don't appear as **Success**.
0 commit comments