Microsoft VivaProductivity and Collaboration
Internal Video Where Employees Already Are
Viva is the employee experience layer in Microsoft 365, covering the intranet, internal communications, learning and knowledge. Its advantage is simply that people are already there, and internal video that requires a second destination is internal video most people never see. Players and library views from Nexus embed into Viva through the embed code and the JavaScript widget, which ship and need no Viva-specific module, alongside the platform's Microsoft 365 integration. Viva's own structure stays as it is.
What you can do together
- Deliver internal video inside Viva Connections and Viva Learning rather than at a second destination.
- Publish a page broadly while a restricted video inside it stays visible only to those entitled.
- Embed a browsable library view, not only a single player.
- Decide which system is the governed library before two of them exist.
- Keep a copied link from becoming a lasting route to the file, since content URLs are signed and expire.
How it connects
Players and library views embed into Viva Connections and Viva Learning, so video is delivered where employees already work, under the platform's own access control and with engagement measured centrally. The documented widget set covers video, audio, image, document, collection and playlist players, library gallery and detail views, and a mashup filter, so a Viva surface can carry a single announcement video or a browsable view of a whole library.
The embed resolves against the viewer's identity, which is the part that matters inside an intranet. A video restricted in the library renders for those entitled and is simply absent for everyone else, so a Viva page can be published broadly without the video becoming broadly visible. Embedding is restricted to the domains the portal names, and content URLs are signed and expire, with the player refreshing its token so a long briefing plays through. Embed analytics report which sites carry an item, with the view count and the last playback from each.
Files take a different route from the embed. The embed places library content in Viva, and Viva's own content stays in Viva. Where files are involved they come through SharePoint and OneDrive, which serve as sources and export destinations, and Teams recordings ingest automatically. Microsoft 365 also stores and plays video, so where the boundary sits with Microsoft's own video handling is worth deciding early: an organization running both needs to know which is the governed library and which is incidental, and answering that late is how two libraries end up existing.
Microsoft VivaProductivity and Collaboration
A scenario
- PlanningThe communications and IT teams name the Viva surfaces that carry video and settle that Nexus is the governed library, with Microsoft's own video handling kept incidental.
- SetupAn administrator adds the intranet's domain to the portal's embed allowlist, and the widget is placed in the agreed Viva surfaces.
- An announcementA leadership video plays inside Viva Connections, with engagement measured centrally.
- A restricted briefingThe same page carries a video limited to one division, absent for everyone else.
- LearningA library view is embedded in Viva Learning so training video is browsable in place.
- Reading itThe announcement's embed analytics list the intranet among the sites carrying it, with its views and the last playback.
What stays where
Viva remains the employee experience layer
Its intranet, learning and knowledge surfaces are unchanged.
The embed resolves against the viewer
A restricted video is absent rather than refused, so a page can publish broadly.
Which system is the governed library is decided early
Microsoft 365 also stores and plays video, and answering late produces two libraries.
Processing runs where you deploy the platform
Shared or dedicated SaaS, your own cloud subscription, or on premises. Employees reach the player over the network, so the deployment has to be reachable from wherever they open Viva.
Products and solutions
Next step
See it on your own Microsoft Viva instance.
We will show the connection made, the data moving and the output, then size it for your deployment.
Contact VIDIZMO
sales@vidizmo.ai
+1 571-969-2180
vidizmo.ai