'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
Fix Viva Engage Images Missing from SharePoint Conversations Web Part
Question details
Images posted in Viva Engage discussions are not displaying when viewed through the SharePoint Online Conversations web part.
- Product
- SharePoint Online / Viva Engage
- Device & OS
- not provided
- Scenario
- Displaying Viva Engage (Yammer) discussion threads containing images on a SharePoint modern page.
- Observed behavior
- Images render correctly within the native Viva Engage app, but appear missing or broken inside the SharePoint Conversations web part.
Ensure you have edit permissions for the SharePoint page hosting the web part, and verify that the images are still actively hosted and visible in the native Viva Engage application.
Change Web Part Display Format from Highlights to Feed
Switching the Conversations web part layout forces a different rendering method, bypassing the image display bug associated with the Highlights view.
The missing image issue is primarily isolated to the 'Highlights' display format of the web part. By switching the view to 'Feed', the web part utilizes a more direct embedding method that correctly loads image assets, albeit with a slightly different visual layout on your site.
Navigate to the SharePoint page containing the broken web part and click the 'Edit' button in the top right corner.
Click on the Viva Engage Conversations web part to select it, then click the pencil icon (Edit web part) on the left side to open the property pane.
In the property pane, locate the layout options and change the selection from 'Highlights' to 'Feed'.
Review the changes to ensure the images now load, then click 'Republish' to make the fix live for all users.
Use an Embedded Viva Engage Feed
If the native Conversations web part continues to fail, manually embedding the Viva Engage feed acts as a reliable fallback alternative.
Looking for a Reliable and Free Office Suite? Try WPS Office
While you troubleshoot Microsoft 365 and SharePoint integrations, you might also need a fast, reliable desktop application for handling your daily documents. WPS Office is a highly compatible, lightweight, and completely free alternative to Microsoft Office, offering everything you need to create Word, Excel, and PowerPoint files without expensive subscription fees.
Frequently Asked Questions
Why do images show in Viva Engage but fail to load in SharePoint?
This is typically caused by a rendering bug specific to the 'Highlights' layout of the SharePoint Conversations web part, where the authentication or pathing for image assets fails to pass correctly between the two platforms.
Is there a Microsoft incident ticket for this missing image issue?
Often, regional or specific tenant bugs like this do not immediately appear on the Microsoft 365 Service Health dashboard. If layout changes do not fix it, administrators should open a direct support ticket with Microsoft.
Will the 'Feed' layout look exactly like the 'Highlights' layout?
No. The Feed layout displays a vertical, continuous scroll of recent threads, whereas Highlights shows a more curated, space-efficient grid of top conversations. However, changing to Feed is currently the most effective native way to restore image visibility.
