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: articles/virtual-network/troubleshoot-outbound-smtp-connectivity.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,19 +1,19 @@
1
1
---
2
-
title: Troubleshoot outbound SMTP connectivity in Azure
3
-
description: Learn the recommended method for sending email and how to troubleshoot problems with outbound SMTP connectivity in Azure.
2
+
title: Troubleshoot Outbound SMTP Connectivity in Azure
3
+
description: Learn how to troubleshoot outbound SMTP connectivity issues in Azure Virtual Machines. Discover recommended email delivery methods and resolve port 25 blocking problems.
4
4
services: virtual-network
5
5
author: asudbring
6
6
manager: dcscontentpm
7
7
ms.service: azure-virtual-network
8
8
ms.topic: troubleshooting
9
-
ms.date: 04/15/2025
9
+
ms.date: 07/28/2025
10
10
ms.author: allensu
11
11
# Customer intent: As a cloud administrator, I want to troubleshoot outbound SMTP connectivity issues in Azure, so that I can ensure reliable email delivery from my virtual machines without interruptions.
12
12
---
13
13
14
14
# Troubleshoot outbound SMTP connectivity problems in Azure
15
15
16
-
Outbound email messages that are sent directly to external domains (such as outlook.com and gmail.com) from a virtual machine (VM) are made available only to certain subscription types in Microsoft Azure.
16
+
Troubleshooting outbound SMTP connectivity in Azure can be challenging when email messages fail to reach external domains. Outbound email messages that are sent directly to external domains (such as outlook.com and gmail.com) from a virtual machine (VM) are made available only to certain subscription types in Microsoft Azure. This article helps you resolve SMTP connectivity issues and configure reliable email delivery from your Azure VMs.
17
17
18
18
> [!IMPORTANT]
19
19
> For the following examples, the process applies mainly to Azure Virtual Machines & Azure Virtual Machine Scale Sets resources (`Microsoft.Compute/virtualMachines` & `Microsoft.Compute/virtualMachineScaleSets`).
@@ -24,7 +24,7 @@ Outbound email messages that are sent directly to external domains (such as outl
24
24
25
25
## Recommended method of sending email
26
26
27
-
We recommend you use authenticated SMTP relay services to send email from Azure VMs or from Azure App Service. Connections to authenticated SMTP relay services are typically on TCP port 587 which isn't blocked. These services are used in part to maintain IP reputation which is critical for delivery reliability. [Azure Communication Services](/azure/communication-services/overview) offers an [authenticated SMTP relay service](/azure/communication-services/quickstarts/email/send-email-smtp/smtp-authentication). Ensure that the [default rate limits](/azure/communication-services/concepts/service-limits#rate-limits) are appropriate for your application and open a support case to raise them if needed.
27
+
We recommend you use authenticated SMTP relay services to send email from Azure VMs or from Azure App Service. Connections to authenticated SMTP relay services are typically on TCP port 587 and isn't blocked. These services are used in part to maintain IP reputation that is critical for delivery reliability. [Azure Communication Services](/azure/communication-services/overview) offers an [authenticated SMTP relay service](/azure/communication-services/quickstarts/email/send-email-smtp/smtp-authentication). Ensure that the [default rate limits](/azure/communication-services/concepts/service-limits#rate-limits) are appropriate for your application and open a support case to raise them if needed.
28
28
29
29
Using these email delivery services on authenticated SMTP port 587 isn't restricted in Azure, regardless of the subscription type.
30
30
@@ -36,15 +36,15 @@ For Enterprise Dev/Test subscriptions, port 25 is blocked by default. It's possi
36
36
37
37
After the subscription is exempted from this block, the VMs must be stopped, deallocated, and then restarted to get the new network policy, all VMs in that subscription are exempted going forward. If the virtual network owned by the exempted subscription has a delegated subnet (to an App Service Environment for example), you must add and remove a new temporary subnet in the Virtual Network. The exemption applies only to the subscription requested and only to VM traffic that is routed directly to the internet.
38
38
39
-
## All Other Subscription Types
39
+
## All other subscription types
40
40
41
-
The Azure platform blocks outbound SMTP connections on TCP port 25 for deployed VMs. This block is to ensure better security for Microsoft partners and customers, protect Microsoft's Azure platform, and conform to industry standards.
41
+
The Azure platform blocks outbound SMTP connections on TCP port 25 for deployed VMs. This block is to ensure better security for Microsoft partners and customers, protect Microsoft's Azure platform, and conform to industry standards.
42
42
43
43
If you're using a subscription type that isn't an Enterprise Agreement or MCA-E, we encourage you to use an authenticated SMTP relay service, as outlined earlier in this article.
44
44
45
45
## Changing subscription type
46
46
47
-
If you change your subscription type from Enterprise Agreement or MCA-E to another type of subscription, changes to your deployments might result in outbound SMTP being blocked.
47
+
If you change your subscription type from Enterprise Agreement or MCA-E to another type of subscription, changes to your deployments might result in outbound SMTP being blocked.
0 commit comments