AxiosError: Network Error

Question

I am attempting to create a case in eDiscovery. When signing into Purview, I receive a pop-up error on the right side.

I have cleared my cache; I have signed into my VPN to connect to the network. My admin has gone over my permissions, and according to them, all looks correct. I was able to use the Purview service early in May but have not used it since then.

Can you please help me get past this issue so I can create cases again? Thank you.

Answer 1

The error indicates a client-side network problem reaching the Purview APIs rather than a permissions issue.

Try the following steps in order:

1. Rule out browser/profile issues
   • Open an InPrivate/Incognito window and sign in to the Purview portal there.
   • Disable all browser extensions in that session and try to open eDiscovery and create a case again.
   • If possible, test from a different browser and from a different machine on the same network.
2. Check local network / DNS issues
   • From the affected machine, disconnect from VPN, wait a minute, then reconnect and try again.
   • If the error still appears, try from a different network (for example, mobile hotspot) without VPN.
   • If it only fails on the corporate network/VPN, provide this information to the network team.
3. Verify firewall and proxy allow required endpoints
   The error is consistent with corporate firewalls or proxies blocking required Microsoft endpoints. Ask the network/security team to:
   • Ensure outbound access over HTTPS (port 443) is allowed to the required Microsoft Purview IP addresses and domains, as well as other Azure/Microsoft 365 endpoints configured for the tenant.
   • Confirm TLS 1.2 is enabled and that no SSL inspection or proxy rule is breaking the TLS connection to Microsoft services.
4. Capture a browser network trace and open a support case
   If the issue persists after validating browser, machine, and network configuration:
   • Capture a browser network trace while reproducing the error.
   • Open a support case from the Azure or Microsoft 365 admin portal and attach the trace so support can identify which endpoint is failing and whether it is being blocked or returning an error.

These steps will help distinguish whether the problem is with the local browser, the corporate network/VPN, or the service, and give the admin/support team the data needed to unblock access so cases can be created again.

---

References:

• Investigate failures, performance, and transactions with Application Insights
• Client Request Aborted or Failed to fetch error in Power Automate
• Troubleshooting access and session controls for admin users