<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Entra Internet Access on Chris Brumm's Blog</title><link>https://chris-brumm.com/tags/entra-internet-access/</link><description>Recent content in Entra Internet Access on Chris Brumm's Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 15 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://chris-brumm.com/tags/entra-internet-access/index.xml" rel="self" type="application/rss+xml"/><item><title>Why you should enable the Microsoft Traffic Forwarding Profile</title><link>https://chris-brumm.com/2026/04/Why-you-should-enable-the-Microsoft-Traffic-Forwarding-Profile/</link><pubDate>Wed, 15 Apr 2026 00:00:00 +0000</pubDate><guid>https://chris-brumm.com/2026/04/Why-you-should-enable-the-Microsoft-Traffic-Forwarding-Profile/</guid><description>This post is part of a series on the Microsoft Traffic Forwarding Profile in Global Secure Access:
Why you should enable the Microsoft Traffic Forwarding Profile (this post) Token Replay Protection and the Compliant Network Check Universal Tenant Restrictions Coexistence with other Secure Web Gateways Logging The case for enabling it The Microsoft Traffic Forwarding Profile tends to get overlooked in two different situations. In organizations that are already running a GSA project – typically starting with Entra Private Access – it often gets deprioritized because the focus is on getting the connector infrastructure in place and migrating VPN users.</description></item></channel></rss>