Sign-in & Login Problems

Fix Viva Engage Embedded Feed Requiring Sign-In on External Websites

Adam Davis Sep 30, 2026 869 views

Question details

The user needs to enable seamless single sign-on (SSO) for a Viva Engage feed embedded on an external website, as visitors are persistently prompted to sign in despite already being authenticated in Microsoft 365.

Fix Viva Engage Embedded Feed Requiring Sign-In on External Websites

Product: Viva Engage
Device & OS: not provided
Scenario: Embedding a Microsoft Viva Engage (Yammer) feed into an external, non-SharePoint website using the use_sso parameter.
Observed behavior: The embedded feed ignores the use_sso parameter and forces visitors to sign in again, failing to recognize their existing Microsoft 365 session.

Before you start

Confirm whether your target website is an external domain or an internal SharePoint site, as single sign-on (SSO) support for Viva Engage varies significantly between these platforms.

Solution 1Recommended

Embed the Feed in an Authenticated SharePoint Page

Since seamless SSO is restricted on external domains, using an internal SharePoint page ensures users are automatically authenticated.

Fully seamless single sign-on for an embedded Viva Engage feed on an external website is generally unavailable by design to prevent security risks.

To achieve a seamless experience without custom development, the official recommendation is to host the feed within the Microsoft ecosystem.

Navigate to SharePoint

Open your Microsoft 365 portal and navigate to an authenticated SharePoint site where your target audience already has access.

Add the Viva Engage Web Part

Edit the SharePoint page, click the '+' icon to add a new web part, and select 'Viva Engage' (or Yammer).

Configure the Feed

Set up the web part to display the desired community or topic feed. Because the users are authenticated into SharePoint, they will experience seamless SSO without secondary sign-in prompts.

Embed the Feed in an Authenticated SharePoint Page

SSO limitation: The use_sso parameter is specifically designed for supported internal SharePoint scenarios and will not bypass authentication when used in an iframe on external websites.

Solution 2

Implement MSAL Authentication on the External Site

If the feed must remain on an external website, developers can use the Microsoft Authentication Library (MSAL) to handle Microsoft 365 authentication natively.

Solution 3

Utilize a Public Viva Engage Feed

For non-sensitive information, making the feed public removes the need for user authentication entirely.

Free Microsoft Office alternative

Simplify Your Workflow with WPS Office

While managing external web integrations and SSO for Microsoft platforms can be highly complex, handling your daily document tasks doesn't have to be. WPS Office offers a free, lightweight, and highly compatible alternative to Microsoft Office.

1. Download WPS Office: Visit the official WPS website to download the free Office suite installation file.
2. Install the software: Run the downloaded installer and follow the simple on-screen instructions.
3. Open and edit seamlessly: Launch WPS Office and open your existing Microsoft documents with perfect format compatibility.

Fully compatible with Microsoft Office formats including Word, Excel, and PowerPointFree and lightweight, bypassing the need for complex enterprise authenticationFamiliar user interface ensuring seamless migration and a zero learning curveBuilt-in robust PDF editing and cloud collaboration tools

microsoft office alternative - wps office

Frequently Asked Questions

Why doesn't the use_sso parameter work on my external website?

The use_sso parameter is intentionally designed by Microsoft to support single sign-on exclusively within authenticated internal environments like SharePoint. It cannot securely pass credentials or bypass authentication on third-party, external domains.

Can I embed a Viva Engage feed without requiring any login?

Yes, but only if the Viva Engage community or feed is configured to be public. Keep in mind that this makes the content visible to anyone on the internet, so it is strictly prohibited for sensitive internal enterprise communications.

What is the best way to share internal Viva Engage updates on an external site securely?

The most secure and seamless method is to implement the Microsoft Authentication Library (MSAL) in your external site's code. This ensures users are securely authenticated through Azure AD before the page requests the embedded feed.

Is it possible to use an iframe to embed Viva Engage on a WordPress site?

Yes, you can use an iframe to embed the feed on a WordPress site. However, unless the feed is public or your WordPress site implements MSAL for Microsoft 365 authentication, visitors will be forced to manually sign in to their Microsoft accounts to view the content.

Login & Account Issues