Skip to content

Commit 2cddff5

Browse files
authored
Update default outbound access explanation
Clarified the implications of default outbound connectivity for VMs and recommended explicit configuration for deterministic behavior.
1 parent aabc9ee commit 2cddff5

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

articles/virtual-network/ip-services/default-outbound-access.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ Examples of explicit outbound connectivity for virtual machines are:
2626

2727
## How and when default outbound access is provided
2828

29-
If a Virtual Machine (VM) is deployed without an explicit outbound connectivity method, Azure assigns it a default outbound public IP address. This IP, known as the default outbound access IP, is owned by Microsoft and can change without notice. Additionally, default outbound is an implicit behavior and may change due to service updates, so it isn’t recommended for production workloads or scenarios that require deterministic outbound connectivity.
29+
If a Virtual Machine (VM) is deployed without an explicit outbound connectivity method, Azure assigns it a default outbound public IP address. This IP, known as the default outbound access IP, is owned by Microsoft and can change without notice. Additionally, default outbound connectivity relies on an implicit platform behavior and may be affected by platform‑level changes. For scenarios requiring deterministic outbound behavior, we recommend using an explicit configuration.
3030

3131
:::image type="content" source="./media/default-outbound-access/decision-tree-load-balancer.png" alt-text="Diagram of decision tree for default outbound access." lightbox="./media/default-outbound-access/decision-tree-load-balancer.png":::
3232

0 commit comments

Comments
 (0)