403 Forbidden Microsoft-Azure-Application-Gateway/v2

The message 403 Forbidden Microsoft-Azure-Application-Gateway/v2 means the website’s server (in this case, fronted by Azure Application Gateway) is actively blocking access to the page being requested. It is not Microsoft randomly blocking pension information; the block is coming from the website or its security configuration.

For Azure Application Gateway specifically, a 403 usually appears when the Web Application Firewall (WAF) is in Prevention mode and decides that the request looks unsafe. When that happens, the gateway returns 403 Forbidden instead of letting the request reach the pension site.

To try to fix or work around this from a non‑technical standpoint:

1. Try a private browsing window
   • In Microsoft Edge, open an InPrivate window and go to the pension site again.
   • This avoids old cookies or cached data that might be confusing the site.
2. Clear browser cache and cookies for that site
   • In Edge, clear browsing data (especially cookies and cached images/files) and then try again.
3. Try a different browser or device
   • Use another browser (for example, Chrome) or another device (phone, tablet, or another PC) to see if the problem is specific to the current browser or machine.
4. Contact the pension provider’s support
   • Explain that when trying to log in or view pension information, a page appears with 403 Forbidden and mentions Microsoft-Azure-Application-Gateway/v2.
   • The pension provider (or their IT team) controls the Application Gateway and WAF rules. They must adjust their security configuration or permissions so the request is allowed.
5. If this is via a work or organization portal
   • Contact the organization’s IT helpdesk or administrator and provide the exact error text. They may need to change access rules, firewall/WAF rules, or permissions.

In summary, the 403 is a security/permissions decision made by the site’s infrastructure (using Azure Application Gateway), not a general decision by Microsoft about who may see pension data. Only the site owner or administrator can permanently fix it; local steps (private window, clearing cache, different browser) can sometimes help if the block is related to cookies or cached authentication.

References:

• HTTP response codes in Application Gateway