When attempting to log in with a federated account through the Remote Help or Quick Assist application within Windows, after selecting the Microsoft account that is federated with Okta, the Okta login page appears partially blank:

This article explains why this is happening and how to solve the issue.

• Blank Login Page
• Remote Help / Quick Assist / Microsoft Office
• Login through federation

The root cause of this issue is that the embedded browser within Remote Help/Quick Assist does not support some of the HTML standards that Okta's default login widget utilizes. 

This is a limitation of Microsoft's WebView2 embedded browser. To work around this issue, Okta's third-generation sign-in widget can be applied to the Okta tenant. This version of the widget uses simpler code that is more compatible with feature-limited browsers and screen-reader software.

NOTE: This widget generation is available with Okta Identity Engine but not in Okta Classic tenants. Other limitations may apply to the third-generation sign-in widget, so it is important to review the sign-in widget (third-generation) documentation to understand any potential impact on the organization. Implementing it is a tenant-wide change that impacts most other applications.