Microsoft Viva: Roles & Access Basics

Key insights

• Microsoft Viva overview: The video is a practical, non-technical walkthrough of Viva and how to prepare before you enable it.
  It explains Viva as a set of modular employee-experience apps inside Microsoft 365 for engagement, learning, and insights.
• Licensing model: Viva licenses are assigned per user, not per tenant, so you only buy what people need.
  Options include built-in Microsoft 365 apps, app-specific licenses, bundle plans (Communications & Communities, Analytics & Feedback), or the full Viva Suite.
• Microsoft 365 admin center as the control point: Configure Viva settings, manage plans, and assign admins from the Microsoft 365 Admin Center.
  Use the Viva admin pages to view purchased plans, open app settings, and control feature access.
• Core admin roles: Global Admin, Teams Admin, and SharePoint Admin commonly span Viva deployments.
  These roles handle tenant-level setup, Teams app installation, and SharePoint content that many Viva apps rely on.
• App-specific roles: Some Viva apps need extra permissions, such as Insights Administrator, Engage/Yammer admin, Pulse or Glint tenant admin.
  Example: Glint requires Global Admin involvement for provisioning and a minimum license threshold to activate.
• Rollout best practices: Avoid over-licensing "just in case," plan strong ownership and temporary elevated roles, and grant Global Admin only when needed.
  Follow deliberate, staged rollouts to keep deployments secure, manageable, and cost-effective.

Overview of the Video

Pragmatic Works published a concise walkthrough that explains how to prepare for deploying Microsoft Viva across an organization. The presenter focuses on practical choices rather than deep technical configuration, so viewers can decide which plans and roles they actually need. Consequently, the video serves as a strategic primer for IT leaders and project owners who want to avoid costly mistakes during rollouts.

The guidance highlights that licensing and admin roles drive most of the complexity in Viva deployments. Moreover, the presenter emphasizes that licensing is per user, not per tenant, and that not every employee must receive every Viva license. Therefore, planning who needs which capabilities up front becomes a central theme of the talk.

Licensing: Per-User Choices

The video breaks Viva licensing into several purchase paths, including Microsoft 365–included apps, app-specific licenses, grouped plans like Communications & Communities, and the full Viva Suite. Because licensing sits at user level, organizations often face tradeoffs between broad coverage and cost control, and the presenter urges deliberate targeting rather than blanket assignment. In practice, this means matching features to roles — for example, giving managers access to certain insights while reserving premium analytics for leadership teams.

Additionally, the presenter explains that some capabilities appear in basic Microsoft 365 plans while others require add-ons or a suite license. Thus, administrators should inventory which Viva modules they intend to use and then map those to license types. This approach reduces overspending and helps ensure employees get the right tools without unnecessary entitlements.

Admin Roles and Central Configuration

On the admin side, the video points viewers to the Microsoft 365 admin center as the central place to manage Viva settings, assign roles, and view plan types. Key cross-cutting roles include Global Admin, Teams Admin, and SharePoint Admin, as these accounts commonly span multiple Viva apps and underlying platforms. The presenter stresses that role assignment should follow the principle of least privilege to balance operational agility with security.

For app-specific work, the video lists additional roles such as Insights Administrator, Engage admin, Knowledge admin, Pulse admin, and Glint tenant admin. Assigning these roles carefully prevents unnecessary use of top-level admin accounts, which reduces risk and audit friction. In short, splitting responsibilities between global and app-specific administrators supports safer, more manageable deployments.

App-by-App Requirements and Settings

The presenter walks through how different Viva modules require different setup steps and role combinations, and notes that some features are managed directly in Teams while others live in portal pages. For example, Viva Engage uses Engage or Yammer admin cells and may require Teams setup policies for app pinning, whereas Viva Insights needs Exchange and Teams service administration plus privileged insights roles for advanced analytics. These variations mean IT teams must plan distinct provisioning flows for each app rather than assuming one-size-fits-all settings.

Specific provisioning constraints also come into play; the video calls out that Viva Glint requires a Global Admin during initial provisioning and a minimum license count to activate in some cases. Therefore, organizations must coordinate licensing purchases and admin availability when they schedule initial activation steps. By aligning procurement, identity, and configuration timelines, teams reduce delays and prevent incomplete rollouts.

Practical Tradeoffs and Provisioning Challenges

The video explores tradeoffs such as assigning Global Admin temporarily versus permanently, and the tension between speed and security during rollouts. Granting broad admin rights speeds setup but raises long-term security exposure, while overly restrictive role models slow adoption and make troubleshooting harder. As a result, the presenter recommends time-bound elevation and explicit ownership of each Viva app to balance those competing needs.

Another common challenge the video covers is the temptation to over-license “just in case,” which drives cost without adding value. Instead, the speaker suggests a phased approach that pilots features with targeted user groups and measures impact before broader purchases. This staged rollout reduces financial risk and produces practical evidence to support further investment decisions.

Common Rollout Mistakes and Best Practices

Finally, the video highlights frequent mistakes such as skipping ownership planning, permanently assigning Global Admin, and failing to map licenses to user personas. The presenter recommends documenting role responsibilities, assigning app owners, and defining license allocation patterns to prevent role sprawl and cost leakage. Those measures simplify governance and make ongoing administration more predictable.

In summary, Pragmatic Works delivers a pragmatic checklist for teams preparing to enable Microsoft Viva. By focusing on per-user licensing, appropriate role separation, and measured provisioning, organizations can aim for secure, manageable, and cost-effective Viva rollouts.

Keywords

Microsoft Viva setup, Viva roles and permissions, Microsoft Viva admin guide, Viva access management, Viva role-based access control, Viva configuration and deployment, Viva for IT admins, Microsoft Viva tenant setup