Legacy SameSite Cookie deprecation - Edge version 132

Hi all,

Edge version 132 has deprecated the Legacy SameSite Cookie behaviour.  Now sites with SameSite=None must also have Secure and use https.

This has broken an on-premise application we use that does not use https.  The app supports https but the developer wants $10,000 to enable it.  I have set a GPO to hold our version of Edge back on 131.

I found that current Firefox can still be told to not require Secure when SameSite=none.  It would be a pain to move everyone to Firefox though.

Is there a way to bypass this in Edge 132+?

thanks

j