Edge >=150 blocks ALL extensions on *.cloud.microsoft (regression from 149) - no policy override

Hi, this is a really good write-up, especially because you already tested the usual policy routes.

If `ExtensionSettings`, force-install, and a clean profile all behave the same way, I would treat this as either an intentional Edge service-side restriction or a regression in the Edge 150 policy handling for those Microsoft 365 surfaces. I do not think this is something an admin can cleanly fix with normal extension policy if Edge is blocking the host before the extension permission model is evaluated.

The most useful next step is to file it through Edge feedback or an enterprise support case with the Edge version, extension IDs, policy export, and a simple repro on `*.cloud.microsoft`. I would also test the same repro on Beta/Dev so you can tell Microsoft whether it is already fixed in a later channel. Short term, the only practical workaround may be documenting the affected extensions and keeping sensitive workflows out of those pages until Microsoft clarifies whether this is by design.