Manage Private Access traffic forwarding profiles
Microsoft's edit ·
Microsoft's commit message in MicrosoftDocs/entra-docs · commit bc164c5 · +3 −5 lines · also on GitHub
11
---
2
−title: How to manage the Private Access profile
2
+title: How to Manage the Private Access Profile
33
description: Learn how to manage the Private Access traffic forwarding profile for Microsoft Entra Private Access.
44
author: kenwith
55
ms.author: kenwith
66
manager: amycolannino
77
ms.topic: how-to
8
−ms.date: 05/02/2024
8
+ms.date: 12/23/2024
99
ms.service: global-secure-access
1010
ms.subservice: entra-private-access
1111
ms.reviewer: katabish
⋯ 15 unchanged lines
2727
2828
### Known limitations
2929
30
−- At this time, Private Access traffic can only be acquired with the Global Secure Access Client. Private Access traffic can't be acquired from remote networks.
31
−- Tunneling traffic to Private Access destinations by IP address is supported only for IP ranges outside of the end-user device local subnet.
32
−- You must disable DNS over HTTPS (Secure DNS) to tunnel network traffic based on the rules of the fully qualified domain names (FQDNs) in the traffic forwarding profile.
30
+[!INCLUDE [known-limitations-include](../includes/known-limitations-include.md)]
3331
3432
## Enable the Private Access traffic forwarding profile
3533
⋯ 39 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 9 Oct 23:06 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.