Viva Connections: Home Sites Changes

Key insights

• Demo video summary: This is a clear walkthrough from the Microsoft 365 & Power Platform Community call (May 19, 2026) showing the latest SharePoint intranet updates.
  It focuses on how Teams and browser experiences now connect through the same intranet tools.
• SharePoint app replaces Viva Connections: Microsoft renamed and rebranded the Viva Connections experience in Teams as the SharePoint app, simplifying the product names and default user experience.
  Existing dashboards and content continue to work under the new name.
• SharePoint home site as the intranet hub: A designated home site now serves as the front door for company news, search, navigation, and links to other portals.
  Home sites deliver prioritized organizational news, branded navigation, and personalized content across devices.
• Administration moves to SharePoint admin center: Admin controls for home sites, audience targeting, and app configuration are now managed in the SharePoint admin center, consolidating settings in one place.
  This change removes older Viva-specific admin paths and simplifies operations for IT teams.
• Updated web parts and dashboards: The demo highlights refreshed web parts for announcements, news, resources, and dashboards that work the same in Teams and browser views.
  Content, permissions, and audience targeting remain compatible with existing deployments.
• Branding and deployment impact: Organizations keep custom app names and logos when already configured, while new deployments default to the SharePoint naming and iconography.
  Licensing and core technology stay largely unchanged, so migration focuses on branding and admin updates rather than reauthoring content.

Microsoft released a demo video that explains recent intranet updates and how they affect everyday users and administrators. The presentation, given by DC Padur during a Microsoft 365 & Power Platform community call, focuses on the shift from Viva Connections toward a unified SharePoint experience in Teams. Consequently, the demo highlights changes to naming, admin tools, home-site management, and updated intranet web parts. For editors and IT teams, the video offers a practical walkthrough rather than a marketing pitch.

Video highlights and scope

The demo shows how a designated SharePoint Home site now acts as the central point for intranet experiences across browser and Teams clients. In particular, the video walks through new resources, announcements, improved news handling, and dashboard improvements that tie into the Home site. Additionally, the presentation notes that the Teams app previously called Viva Connections will now appear by default as the SharePoint app, aligning naming and icons. This change is largely about clearer product alignment while keeping core capabilities intact.

What changed: branding and platform alignment

First, Microsoft replaced the default Teams name and icon for Connections with the SharePoint app, which reduces confusion between Teams features and SharePoint-managed content. However, existing custom app names and logos remain unaffected, so organizations that already customized branding will not lose their settings. Moreover, the underlying content model — news, audience targeting, permissions, and dashboards — continues to work as before, which eases the transition for content authors. As a result, the change emphasizes consistent user experience without forcing immediate content rework.

Technical direction and web part updates

The demo also covers updated intranet web parts and dashboard elements that enhance how organizations surface information and tools from a Home site. For instance, news published on the Home site receives priority and appears across the SharePoint start page and Teams, improving visibility for official communications. Meanwhile, the Home site remains a communication site with organization-wide search, branded navigation, and integration points to other corporate portals. Therefore, the technical direction favors a single, extensible Home site model to power both browser and Teams access.

Administration and governance shifts

Notably, Microsoft is consolidating management tasks into the SharePoint admin center, moving away from separate Viva Connections admin consoles. Consequently, administrators will create, designate, and manage multiple Home sites, audience targeting, and app settings from one place, which can streamline governance. However, this consolidation also requires admins to update their workflows and retrain staff who previously managed Home site settings elsewhere. Thus, while administration becomes more centralized, organizations must plan for the operational transition.

User experience and Teams integration

From a user perspective, the shift makes intranet content more consistently reachable inside Teams and in the browser, since the Home site now underpins the Teams app experience. The demo shows that dashboards, announcements, and resources are accessible in Teams without an extra step, which simplifies daily tasks for employees. Yet, Teams app configuration and licensing considerations may still affect how widely organizations deploy the feature across many teams and devices. Consequently, IT teams must balance ease of access with app rollout policies and support needs.

Tradeoffs and practical challenges

Balancing the benefits of a unified Home site against the need for customization creates tradeoffs that organizations must weigh carefully. On one hand, centralization improves search, governance, and the reach of corporate news; on the other, it can limit alternative intranet architectures that some groups prefer for autonomy. Furthermore, migrating legacy Viva configurations into the new consolidated model will require testing and may surface custom web parts or scripts that need updates. Therefore, the recommended approach is phased adoption with clear testing, documentation, and communication plans.

Next steps for IT teams

Administrators should review Home site settings in the SharePoint admin center, verify custom branding, and plan a communications timeline for end users who will see the Teams app label change. Additionally, testing dashboards and targeted news publishing in a pilot group will help uncover compatibility issues before broad rollout. Finally, training site owners and help desk staff reduces disruption and improves adoption as the new default behavior spreads across the tenant. In short, careful planning will turn these product changes into a smoother experience for both administrators and employees.

In conclusion, the demo offers a clear view of Microsoft’s intent to align intranet experiences under SharePoint while keeping key capabilities stable. Although the changes simplify naming and centralize admin controls, they also bring practical tradeoffs around customization and migration effort. For organizations, the path forward involves measured testing, clear governance, and user training to capture the benefits while managing risks. Overall, the update aims to make organizational content easier to find and manage across browser and Teams environments.

Keywords

Viva Connections changes, SharePoint Home Sites update, Viva Connections vs SharePoint Home Sites, SharePoint Home Site migration guide, Viva Connections features 2026, Viva Connections governance best practices, SharePoint Home Sites customization tips, Microsoft Viva Connections admin guide