This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(44.800000000000004, 3%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EB%3C/text%3E%3C/svg%3E)
We have an on-premises only implementation of Windows Hello for Business (no hybrid or cloud involvement at all). This works great with our ADFS 2019 infrastructure both internally and externally with the legacy Edge browser to provide seamless login to resources. However, when testing the new Chromium Edge, users are always prompted for authentication. Using the developer screen in the browser you can see the error logged is "window.navigator.msLaunchUri is not available"
Is there a group policy setting that will enable the missing "msLaunchUri" API in new Edge? Some other setting in ADFS that I need to tweak?