Performance differences for Insipix web terminal between Microsoft Edge and other browsers on Windows 11

Question

Performance differences for Insipix web terminal between Microsoft Edge and other browsers on Windows 11

Davis Mein 0

Hi everyone,

I’m writing from Australia and have noticed some unusual behaviour with a web‑based trading terminal that we access via --PII REMOVED-- in Microsoft Edge on Windows 11. I’d like to understand if this could be related to browser / policy settings in a Microsoft 365 environment rather than to the platform itself.

The setup looks like this:

Users on Windows 11 Pro in Australia.

Microsoft Edge (latest stable build) as the default browser.

Signed in to Microsoft 365 (work or school account) and using Edge profiles synced with those accounts.

Accessing a multi‑asset trading terminal provided via the --PII REMOVED-- website (pure web app, no desktop client).

What we’re seeing:

In Edge, the --PII REMOVED-- terminal occasionally shows delayed updates in price feeds and order status compared to other browsers on the same machine.

Some real‑time components (for example streaming quotes or WebSocket‑style data) seem to stall or reconnect more often when Edge is running with the Microsoft 365 profile active.

If the same user opens the --PII REMOVED-- terminal in Chrome or Firefox, or in Edge without signing into the Microsoft 365 profile, the delays are reduced or disappear.

Steps already tested:

Clearing cache and cookies for Edge.

Disabling all extensions.

Using InPrivate mode for --PII REMOVED--.

Setting --PII REMOVED-- as an exception in tracking prevention.

Checking that time, region and network settings are correct on the Windows 11 machines in Australia.

My questions for the community are:

Are there any known interactions between Microsoft Edge profiles tied to Microsoft 365 accounts and third‑party web apps that rely heavily on real‑time connections (for example, WebSockets or long‑lived HTTP connections), like a trading terminal on --PII REMOVED--?

Could security policies such as Conditional Access, Defender for Cloud Apps or other Microsoft 365 / Azure AD controls impact how external web apps maintain those real‑time connections inside Edge?

From a best‑practice perspective, would you recommend isolating financial / trading web applications like --PII REMOVED-- in a separate Edge profile or even a separate browser, especially in environments where Microsoft 365 policies are quite strict?

I’m not asking for support on the trading platform itself, just trying to understand whether there are Microsoft‑side settings, features or documented behaviours that might explain why the --PII REMOVED-- terminal appears more restricted or less responsive in Edge with a signed‑in Microsoft 365 profile, compared to other browsers or unsynced profiles.

Any guidance, documentation links or configuration tips that could help us evaluate this would be greatly appreciated.

Thanks in advance.

0 comments

1 answer

Your answer

Answer 1

Lucus-V 10,775 Microsoft External Staff Moderator

Hi Davis Mein,

Please note that our Microsoft Q&A forum is a public platform, and we will modify your response/ question to hide your personal information in the description. Kindly ensure that you hide any personal or organizational information the next time you post an error or other details to protect personal data.

Since Microsoft Edge is built on the Chromium engine, there is generally little to no difference in performance between Edge and Google Chrome in most scenarios.

We sincerely appreciate the time and effort you have invested in troubleshooting the issue and carefully comparing the performance in your environment.

I really wish I could assist you directly on this issue. However, the behavior you're experiencing is tied to back‑end systems and service functionality, and unfortunately, we don't have the authority or access required to investigate or make changes at that level.

Please note that this is a user-to-user support forum. Moderators, contributors including external Microsoft employees cannot directly intervene in Microsoft product features or access back-end systems. Our role is limited to providing technical guidance on reported issues, requests, or ideas.

Given these limitations, the most appropriate avenue for product changes or feature requests is to:

Send feedback through Microsoft Edge: ••• > Help and feedback > Send feedback or ☰ > All menu > Help and feedback.
Send feedback to Microsoft with the Feedback Hub app.

Thank you for your understanding, and I hope the support team can resolve this for you soon.

Davis Mein 0 Reputation points

2026-07-14T13:25:14.4666667+00:00

Hi Lucus,

Thank you for your response and for removing the personal information from the post. I will make sure to avoid including any personal or organizational details in future questions.

I understand that Microsoft Q&A moderators cannot investigate the trading platform’s back-end systems or make product-level changes. However, my question is mainly about the Microsoft Edge and Microsoft 365 configuration side rather than the platform’s back end.

Since the issue appears specifically when Edge is used with a signed-in work or school profile, I am trying to determine whether managed browser policies, Microsoft Defender protections, Conditional Access, proxy inspection, or other organization-level controls could affect WebSocket connections or long-lived HTTP sessions.

Are there any Edge diagnostic tools, policy pages, logs, or Microsoft documentation that you would recommend checking to compare a managed Edge profile with an unsigned or unmanaged profile? For example, would reviewing edge://policy, DevTools network logs, or an Edge net-export capture be an appropriate next step?

Even general guidance on how to identify whether the behaviour is caused by an Edge policy, security control, or network configuration would be very helpful.

Thank you again for your time and guidance.
Lucus-V 10,775 Reputation points Microsoft External Staff Moderator

2026-07-14T15:19:13.63+00:00

Hi Davis Mein,

You may open DevTools by pressing F12, navigate to Network and Performance tab to trace.

The behavior you're experiencing is related to back-end system of the browser, rather than user configuration.