Native Passkey Support in Embedded Browsers for Microsoft Admin Center

Add native Passkey (WebAuthn) redirection support within the embedded browser session window (specifically for Edge/Chrome engines). This will allow MSPs and enterprise administrators to leverage the Private Mode (Tenant Isolation) feature while simultaneously adhering to Microsoft’s mandatory phishing-resistant MFA requirements (such as Entra Admin Center passkey logins).

Currently, Remote Desktop Manager (RDM) handles multi-tenant isolation beautifully via Private Mode in embedded browser entries. However, as Microsoft aggressively pushes phishing-resistant authentication—making passkeys mandatory for Entra admin center access—administrators hit a wall.
When trying to authenticate using a passkey inside an embedded browser tab, the WebAuthn API call fails or is unable to use the added passkey from the DVLS safe.
To work around this, we are forced to open sessions in an External Browser. While this fixes authentication, it completely breaks the tenant isolation benefits of Private Mode and clutters the local machine with multiple browser profiles. As an MSP, we need to open lots of Microsoft Admin Centres at the same time.. It is therefore necessary to have a central overview, with each entry opening in the embedded browser.

We need the embedded browser component in RDM to natively support integrated passkeys in the DVLS safe.

1. Seamless MFA: When a website inside an embedded tab requests a passkey, RDM should trigger the integrated passkey.
2. Best of Both Worlds: Keep the excellent session isolation provided by Private Mode and allow administrators to log in using modern passkeys securely.

Why This Matters

• Mandatory Microsoft Requirements: Microsoft is steadily rolling out mandatory phishing-resistant MFA for all admin portals. This isn't a "nice-to-have" anymore; it is becoming a hard blocker for daily administration.
• Crucial for MSPs: Managing dozens of Entra tenants requires strict isolation to prevent accidental cross-tenant data leaks or session bleeding.
• Productivity: Switching back and forth between embedded and external browsers breaks the unified "single pane of glass" workflow that makes RDM so powerful.