Microsoft Viva Employee Experience Deployment

The floor buys the whole engagement at baseline scope: the module-fit workshop and licensing map, Viva Connections (the SharePoint app in Teams) with dashboard, feed and pinning, a governed Viva Engage network with launch communities, Viva Insights with the privacy settings set on purpose, the governance one-pager, the communications plan, adoption goals and the 30-day review — all in one tenant. The price moves with add-on modules (Viva Learning, Amplify, Pulse, Glint), a second Connections experience, several business units wanting separate community models, and multilingual launches. After the workshop you receive one fixed quote in writing; that number is the number, and you pay after you approve delivery.

Seven: Viva Connections, Viva Engage, Viva Insights, Viva Learning, Viva Amplify, Viva Pulse and Viva Glint. Viva Topics was retired on 22 February 2025 and Viva Goals on 31 December 2025, so neither is configured here. If your OKR process lived in Goals, the honest advice is to pick a replacement tool on its own merits rather than force the process into Engage or Pulse — we will tell you what the remaining apps can and cannot carry, and keep that decision out of this quote.

Usually both. Included with Microsoft 365 plans that carry SharePoint Online and the Viva Engage Core service plan: one Viva Connections experience, the core of Viva Engage (communities, conversations, storyline and core Answers) and the personal layer of Viva Insights. That is enough for a real baseline rollout. Paid: leadership corner, AMAs, storyline announcements, delegation, campaigns and advanced analytics in Engage, Viva Amplify and any second Connections experience — in Viva Suite or the Viva Employee Communications and Communities bundle; manager, leader and advanced Insights — with Viva Insights, Viva Suite, the Viva Workplace Analytics and Employee Feedback bundle or, at the time of writing, a Microsoft 365 Copilot license; Viva Learning's premium connectors; and Viva Glint, which now includes Viva Pulse. The workshop produces a per-module map against your actual licenses, and our subscription pages show live prices.

Renamed, not retired. Microsoft renamed the Viva Connections app in Teams to the SharePoint app, with the rollout completing in June 2026, and states that existing dashboards, cards, audience targeting, app names and logos keep working. The architecture is unchanged: your SharePoint home site surfaced in Teams on desktop and mobile. Microsoft is also consolidating the management of multiple home sites into the SharePoint admin center. We configure against what your tenant shows at project time, and we use both names on this page because that is what people search for.

No. This rollout assumes a home site exists and builds the Teams, community and insights layer on top of it, whoever designed it. What we do need is a home site that is designated as such in your tenant and news that publishes from somewhere; if the intranet is really an unowned page from years ago, we will say so in the workshop and point you at our intranet design service instead of stacking Viva on sand.

Decisions written down and applied in the Engage admin center before the network opens: who may create communities and how they are named; whether storyline is on for everyone; whether external networks and guests are allowed; what leadership corner and campaigns are for and who owns them; how retention and eDiscovery apply; and who moderates what. The network then launches with a small set of communities that each have a named owner and real cover content, rather than an empty feed and a 'create a community' button. That is the difference between a network that is alive at day 30 and one that is a ghost town by day 90.

No, and we configure it so they cannot. Manager and leader views show aggregated, de-identified data only, and only for groups at or above the minimum group size — Microsoft's default is 10 and it cannot go below 5. Personal insights are visible only to the individual. We put the thresholds, the manager-insights toggle, exclusions and the opt-out path in writing for HR to sign before anyone sees a manager view, and in organizations with a works council we ask that it is consulted first. The same discipline applies to Viva Pulse, whose results only appear once a minimum number of responses is in.

Yes, as add-on modules, with the caveat that Glint is its own project in miniature. Pulse needs an HR decision on templates, who may send a pulse, the cadence and the response threshold; we configure it in a day or two. Glint needs tenant provisioning (Microsoft requires a directly assigned Global Administrator for that step), employee-attribute data exported from your HRIS in Microsoft's template — directly or as an automated SFTP feed — and an HR owner who designs the survey program; we do the provisioning, the data load and the first program's technical configuration. Since October 2025 a Viva Glint license includes Viva Pulse, so the two are usually scoped together.

Only if you have learning paths, academies or assignments that point at Microsoft's own Microsoft 365 training modules: Microsoft is removing 161 of them from the Viva Learning catalog in a retirement running through 21 September 2026, and anything referencing them shows unavailable content afterwards. Where Viva Learning is in your quote we re-point those paths to current content as part of the configuration; where it is not, we flag it in the licensing map so your learning admin can. The included Microsoft Learn and LinkedIn Learning sets and your own SharePoint content are unaffected.

With three to five measures agreed at launch and a baseline captured from Microsoft's reports before the announcement goes out — for example the share of the launch audience active in Viva Engage and posting or reacting in a community, home-site and dashboard visits from the SharePoint and Teams usage reports, and Viva Insights opt-in. The day-30 targets are yours; we help you set them at a level that means something. The review meeting is inside the fixed price and ends with a written next-steps list: which communities need an owner's attention, which cards nobody opens, whether a deferred module has earned its license.

No. Copilot licensing, deployment and adoption is its own program with its own readiness work, and we keep it separate on purpose. Two places the two meet: the Copilot Dashboard sits inside Viva Insights, and we enable it here where you are already licensed; and Copilot in Viva Engage summarizes and drafts community content for licensed users. If Copilot is on your roadmap, the Viva Insights privacy decisions you make here carry straight into it.

No — moving a Viva Engage network and its data between Microsoft 365 tenants is our Viva Engage Tenant-to-Tenant Migration, with its own tooling and timeline. The two are often run back to back: migrate the network first, then use this rollout to govern and relaunch it in the surviving tenant with the rest of the Viva layer.

Yes. We transact Microsoft licensing directly as a CSP partner, at Microsoft's list price, and our subscription pages for Viva Suite, Viva Employee Communications and Communities, Viva Insights, Viva Learning and Viva Glint show live pricing. Organizations that buy their Microsoft licensing through us also get unlimited break-fix support during business hours at no extra charge, and there is no lock-in in either direction — you can move your subscriptions to another partner, or back to Microsoft, at any time. Buying elsewhere does not change this service or its price.

Typically 3 weeks to launch for the baseline modules: workshop and decisions in week 1, configuration in week 2, champions pilot and launch in week 3, then the 30-day review about a month later. The critical path is yours: the leads in the room in week 1, Viva licenses assigned by the start of week 2, HR's signature on the Insights privacy settings, and owners named for every community. Where those slip, launch moves week for week — we say that at kickoff so the plan is honest. Add-on modules extend the plan; Glint in particular depends on your HRIS data being ready.