Microsoft Entra Global Secure Access
GeneralHow to configure custom headers (preview)
In brief
The page title now marks custom headers as preview and notes that rollout is expected to complete by September 10, 2026.
What Entra admins need to know
Administrators can use the date to set expectations for feature availability; no action is specified.
This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.
Documentation change
View on Microsoft LearnThe comparison below shows only the changed extract. Use the full-page view for complete context.
How to configure custom headers (preview)
Custom headers in Global Secure Access (GSA) lets you add custom HTTP headers to outbound web requests for specific destinations. You configure headers as part of a web filtering policy rule, so the headers are added only to traffic that matches the fully qualified domain names (FQDNs) that you select.
Custom headers in Global Secure Access (GSA) lets you add custom HTTP headers to outbound web requests for specific destinations. You configure headers as part of a web filtering policy rule, so the headers are added only to traffic that matches the fully qualified domain names (FQDNs) that you select.
@@ -9,7 +9,10 @@ ms.subservice: entra-internet-access ai-usage: ai-assisted --- -# How to configure custom headers+# How to configure custom headers (preview)++> [!NOTE]+> This feature is being rolled out with the expected completion date of September 10, 2026. Custom headers in Global Secure Access (GSA) lets you add custom HTTP headers to outbound web requests for specific destinations. You configure headers as part of a web filtering policy rule, so the headers are added only to traffic that matches the fully qualified domain names (FQDNs) that you select.