Share via

AxiosError: Network Error

Andre Livingston 0 Reputation points
2026-06-17T17:04:58.16+00:00

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.

User's image

Microsoft Security | Microsoft Purview
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Pilladi Padma Sai Manisha 10,190 Reputation points Microsoft External Staff Moderator
    2026-06-18T08:58:35.3166667+00:00

    Hi @Andre Livingston

    Thank you for the detailed write-up and for already checking permissions, cache, and VPN I understand how disruptive it is to be blocked from creating eDiscovery cases. The good news is that AxiosError: Network Error is a client-side network/reachability issue (the browser's request to the Purview API isn't getting through), rather than a permissions problem which matches what your admin found.

    Please try these in order:

    1. Isolate the browser/profile
    • Open an InPrivate/Incognito window, disable all extensions, and retry creating the eDiscovery case.
    • Test a different browser and, if possible, a different machine on the same network.
    1. Isolate the network/VPN
    • Disconnect VPN, wait ~1 minute, reconnect, and retry.
    • Test from a different network (e.g., mobile hotspot, no VPN). If it works off-VPN but fails on corporate network, the block is in your corporate proxy/firewall engage your network team.
    1. Validate firewall/proxy & TLS (network team)
    • Allow outbound HTTPS/443 to the required Microsoft endpoints, including the M365/Defender/Purview portal URLs (e.g., login.microsoftonline.com, *.security.microsoft.com, security.microsoft.com, *.blob.core.windows.net, secure.aadcdn.microsoftonline-p.com)2.
    • Confirm TLS 1.2 is enabled and that SSL/TLS inspection is not breaking the connection to Microsoft services.
    • Confirm your Purview/compliance setup does not have Public network access = Deny / private endpoint that would require access from inside the corporate VNet2.
    1. If still failing
    • Capture a browser network trace (HAR) while reproducing the error, and open a Microsoft support case with the trace attached so we can pinpoint the exact blocked endpoint.

    Reference docs: Troubleshoot portal access / required URLs and Resolve eDiscovery errors.

    Please run steps 1–2 first and let me know the results ,that will tell us whether the block is browser-side or network-side.

    Was this answer helpful?

  2. AI answer

    2026-06-17T17:05:11.89+00:00

    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:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.