Viva Connections home sites are moving to a new admin center, and SharePoint teams should prepare. Microsoft 365 Roadmap item 567887, updated July 29, says Viva Connections multi-home site management is moving from the Microsoft 365 admin center to the SharePoint admin center. General availability was planned for August 2026, so check whether the change has reached your tenant.
It looks like a small UI shuffle, but it is a real governance change for intranet admins. Home site creation, audience targeting, priority order and removal are being consolidated into the SharePoint admin center. Meanwhile, the old Microsoft 365 admin center entry points redirect there.
Home site management moves
Admins manage multiple Viva Connections home sites from the SharePoint admin center instead of the Microsoft 365 admin center.
Audience and priority
A good moment to clean up audience targeting, site ownership, naming and home site priority rules.
SharePoint becomes the hub
Admin work lands closer to the SharePoint sites, permissions and intranet architecture that power the experience.
What’s changing for Viva Connections home sites
According to the roadmap, admins will be able to do the following from the SharePoint admin center:
- Create and manage multiple home sites.
- Configure audience targeting for home sites.
- Manage home site priority order.
- Remove home sites.
- Follow redirects from the old Microsoft 365 admin center entry points.
The roadmap item also says legacy Viva Connections instances and the older draft/enabled management concepts are being deprecated. Existing Viva Connections experiences will be upgraded to full home sites.
Why SharePoint admins should care
Microsoft Learn describes a SharePoint home site as a customized landing experience that reflects the organization’s brand, voice and priorities. It is also a gateway to other intranet portals. Viva Connections, in turn, brings relevant news, conversations, resources and tools into Teams and the web.
Moving multi-home site administration into the SharePoint admin center puts control next to the assets that matter: communication sites, hub architecture, permissions, branding, news, global navigation and audience targeting. Home sites often represent regions, departments, business units, frontline populations or acquired companies. If priority order or targeting is messy, employees land in the wrong experience.
Viva Connections home sites prep checklist
- Inventory current experiences. List every Viva Connections experience with its SharePoint site, audience, owner and intended population.
- Confirm which are real home sites. Separate active home sites from old pilots and departmental experiments.
- Review audience targeting. Make sure regional, frontline, department and acquisition audiences are current and don’t overlap unexpectedly.
- Decide priority order. If a user matches several home site audiences, document which should win before changing anything.
- Validate ownership and permissions. Agree who can request changes and who approves them across home site owners, SharePoint admins, Teams admins and communications.
- Document the redirect in internal runbooks.
- Tell intranet stakeholders where management moved, even if users won’t notice a change.
Permissions and licensing
Microsoft’s setup guidance still applies. You need Enterprise, Frontline or Academic licensing to create a Viva Connections experience. Running two or more experiences (up to 50) requires every user in the tenant to have Microsoft Viva Suite or Viva Communications and Communities licensing. You also need SharePoint admin permissions for the admin center and Teams administrator permissions to pin the Viva Connections app in Teams.
Use the move to split responsibilities properly if one global admin currently does everything. SharePoint admins own home site configuration, Teams admins handle app pinning and Teams policy, and communications owners focus on content.
Suggested operating model
| Area | Owner | Governance question |
|---|---|---|
| Home site creation | SharePoint admins + intranet governance board | Who can request a new home site, and what business case is required? |
| Audience targeting | SharePoint admins + identity and audience owners | Are the groups accurate, maintained and reviewed? |
| Priority order | Intranet owner | What should users see when they match several experiences? |
| App pinning in Teams | Teams admins | Which users see Viva Connections pinned, under which policy? |
| Content quality | Communications teams | Is the home site useful, current and accessible? |
Bottom line
Moving Viva Connections home sites into the SharePoint admin center is a sensible consolidation and a good reason to review home site sprawl. Inventory current experiences, clean up audience targeting, agree on priority order, update runbooks, and make sure the right people have the right permissions. While you’re reviewing intranet governance, see also SharePoint file-level archiving and Restricted Content Discovery.
Last reviewed: October 2026
Sources
- Microsoft 365 Roadmap ID 567887: Viva Connections multi-home site management moving to SharePoint admin center
- Plan, build and launch a SharePoint home site (Microsoft Learn)
- Set up Viva Connections in the Microsoft 365 admin center (Microsoft Learn)
- Overview of Viva Connections (Microsoft Learn)
Discover more from Cloud Osprey
Subscribe to get the latest posts sent to your email.
