Internet Access traffic forwarding profile
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/entra-docs · commit 3bf15ed · +4 −1 lines · also on GitHub
⋯ 1 unchanged line
22
title: How to manage the Internet Access profile
33
description: Learn how to manage the Internet Access traffic forwarding profile for Microsoft Entra Internet Access.
44
ms.topic: how-to
5
−ms.date: 10/26/2026
5
+ms.date: 10/27/2026
66
ms.subservice: entra-internet-access
77
ms.reviewer: katabish
88
ai-usage: ai-assisted
⋯ 87 unchanged lines
9696
| IP subnet | `0.0.0.0/0` | `0-65535` | UDP |
9797
9898
Keep the bypass policies in place. Traffic matching a bypass rule remains excluded even when it also matches a wildcard acquisition rule. Private Access routing takes precedence over Internet Access; traffic routed through Private Access isn't subject to Internet Access cloud firewall rules.
99
+
100
+> [!NOTE]
101
+> DNS traffic acquisition isn't supported by the Internet Access traffic forwarding profile in this preview. Wildcard acquisition rules don't enable DNS acquisition, so cloud firewall policies don't filter DNS traffic. Configuring an FQDN destination doesn't enable DNS query acquisition.
99102
100103
The `0.0.0.0/0` destination covers IPv4, not IPv6. You can restrict the port ranges and destinations instead of using this broad acquisition configuration.
101104
⋯ 44 unchanged lines
Microsoft's Markdown source from MicrosoftDocs/entra-docs, © Microsoft Corporation, under MIT. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 28 Oct 00:34 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.