How to Embed Viva Engage in a PHP Web Application with SharePoint

To embed viva engage in a php web application with SharePoint, use the correct account, product, permissions, and destination. This guide explains the supported workflow and the checks that confirm the result.

Identify the Exact SharePoint Item, Permission, or Flow

Confirm the owning account, required permissions, affected files or services, and the exact outcome you need. Keep a backup when the task changes local content or removes access.

Quick SharePoint or Flow Check

First, use Embed Feed for Engage (recommended). Next, open the file or template in the PHP app where the feed should appear, and verify the final state before changing any backup or secondary account.

How to Embed Viva Engage in a PHP Web Application with SharePoint

1. Use Embed Feed for Engage (recommended)
2. Open the file or template in the PHP app where the feed should appear
3. Go to the Embed widget configuration site in Viva Engage
4. Choose the feed type (Home feed, Community feed, Topic feed, User feed, or Web link feed)
5. Select Get code and then Copy to copy the generated iFrame code
6. Open the file that contains the classic embed feed

After the final step, reopen the affected app, portal, file, or account page and confirm the exact status or behavior described in the title.

WPS Office: A Free, AI-Powered Microsoft Office Alternative

WPS Office cannot directly change Microsoft-side account, billing, subscription, activation, tenant, OneDrive service, or SharePoint permission state. Those changes must be completed in the appropriate Microsoft portal.

WPS Office is a free Microsoft Office-compatible suite that brings Writer, Spreadsheets, Presentation, and PDF into one familiar workspace for common DOCX, XLSX, PPTX, and PDF files. Its built-in WPS AI can help draft and polish text, analyze spreadsheet data, create editable slides, and summarize or answer questions about documents and PDFs. AI availability and usage limits can vary by plan, platform, region, and app version.

Test advanced macros, add-ins, external connections, sensitivity controls, and Microsoft-only cloud integrations on a copy before moving a critical workflow.

Use Word, Excel, and PPT for FREE

Free Download

Practical Checks That Prevent a Repeat

• Record which account, app, and file owns the workflow
• Keep a verified backup before removing access, changing ownership, or replacing a local file
• Apply high-impact changes to one test item or user before expanding the scope
• Save confirmation numbers, dates, and screenshots of the final settings when they affect billing, security, or permissions

Frequently Asked Questions

What should I verify before I use Embed Feed for Engage (recommended)?

Use Embed Feed for Engage (recommended). File and folder sharing can differ because of inheritance, site sharing policy, sensitivity settings, or the user’s permission level. Check Manage access on the exact folder.

Why is it important to open the file or template in the PHP app where the feed should appear?

It keeps a copy of current permissions and can then be edited independently. Document the change so future site membership changes do not create unexpected access. Confirm the account type, product version, ownership, and permissions before assuming the control is unavailable.

Can I safely test the step to go to the Embed widget configuration site in Viva Engage on a limited scope?

Open the associated Power Automate flow and inspect Run history. The failed trigger or action shows the connection, permission, expression, or data issue to correct. Keep the relevant backup or confirmation until you have checked the result.

What final check proves I was able to embed viva engage in a php web application with SharePoint?

Open the file that contains the classic embed feed. Reopen the affected app or portal and confirm that the expected status persists.