Setting Up Viva Connections: Dashboard, Feed and the Intranet Entry Point

Setting up an intranet entry point inside Teams with a SharePoint home site and Viva Connections: dashboard cards, audiences, global navigation, mobile testing and measurement.
Technical summary
Technology
Microsoft Viva Connections, SharePoint Online home site, Microsoft Teams, SharePoint Framework (SPFx), SharePoint Online Management Shell
Topic
Setting up an intranet entry point inside Teams
Level
Intermediate
Prerequisites
  • SharePoint administrator rights
  • A published SharePoint communication site
  • Access to the Teams admin center
In this article7 sections

If employees stay in Teams all day, even a well-designed SharePoint intranet becomes an address nobody opens. News is published and not read; links are updated and nobody notices. Viva Connections brings the intranet’s news, the most-used tools and personal tasks together in a single entry point inside Teams, on desktop and on mobile. Below, we explain the relationship between the SharePoint home site and Viva Connections, the setup steps, the mistakes most often made in dashboard design in the field and how to measure usage.

Viva Connections and the SharePoint home site

Viva Connections isn’t a separate content store. It reads content from SharePoint, Viva Engage and connected apps. It has three components:

  • Dashboard: A tool area made of cards, personalized by audience. Pending approvals, shifts, quick links and cards that open a Teams app sit here.
  • Feed: A news feed made of SharePoint news posts and Viva Engage posts, with content the user follows and is targeted by.
  • Resources: Links coming from global navigation; the Teams counterpart of the intranet’s main menu.

The SharePoint home site is a communication site marked as the landing page of the intranet in the tenant. When a home site is set, the Viva Connections experience is associated with this site; the dashboard is managed on this site, and global navigation in the SharePoint app bar is configured from here too. Microsoft also offers an experience where Viva Connections can be used with just the dashboard and feed, without a home site. But if you have an intranet, setting it up with a home site gives a more cohesive result in terms of navigation and brand consistency.

The home site sits at the top of the site topology. First clarify how department sites are grouped under hubs and the relationship between the home site and hubs using the structure in the SharePoint hub site architecture guide. Viva Connections is an access layer added on top of this structure. It doesn’t fix the structure.

Prerequisites and setting the home site

Before starting the setup, verify these conditions; most problems on launch day come from an item skipped on this list:

  • The site that will be the home site is a communication site, has a published home page, and the entire target audience (usually “Everyone except external users”) has at least read permission.
  • The tenant’s subscriptions include the basic features of Viva Connections. The basic experience is included in most Microsoft 365 and Office 365 commercial subscriptions; advanced features such as multiple experiences may require an additional Viva license. Verify the scope in Microsoft’s current Viva licensing documentation.
  • The sites publishing news have been identified, and one or more organizational news sites have been defined for corporate news.
  • The groups to be used in dashboard cards are ready in Entra ID (Microsoft 365 groups or security groups).

The home site is set from the SharePoint admin center or with SharePoint Online Management Shell. We prefer the PowerShell method because it’s repeatable and documentable; the command itself goes into the change record.

# SharePoint Online Management Shell
Connect-SPOService -Url https://contoso-admin.sharepoint.com

# Mark as the home site
Set-SPOHomeSite -HomeSiteUrl https://contoso.sharepoint.com/sites/intranet

# Verify
Get-SPOHomeSite

# Define the organizational news site
Set-SPOOrgNewsSite -OrgNewsSiteUrl https://contoso.sharepoint.com/sites/intranet

Setting the home site has effects users can see: the site’s news can be highlighted as corporate news, and the search scope widens to the whole tenant. That’s why you should make the change after the intranet home page is ready in terms of content. A half-finished home page is visible to everyone.

Dashboard cards and audiences

The dashboard is edited from the Viva Connections management link in the home site’s settings menu or from the Viva Connections settings in the Microsoft 365 admin center; since Microsoft changes this management surface from time to time, verify the menu location in the current documentation. Cards run as Adaptive Card Extensions (ACEs). Some come ready-made from Microsoft; organization-specific cards are developed with the SharePoint Framework (SPFx).

Card type Use Note
Web link Opening a web page or application The simplest card; needs no maintenance
Teams app Opening an internal Teams app The app must be permitted for the user
Approvals, assigned tasks Showing a person’s pending work Personal data; no audience needed
Card designer A custom card without writing code For simple views
Custom card with SPFx Live data from a business system Development and lifecycle load

The dashboard’s real strength is audience targeting. Each card can be targeted at one or more Entra ID groups: production staff see shift and OHS cards, the sales team sees CRM and quote approval cards. A card with no audience defined is visible to everyone. That’s the default.

The mistakes we see most often in dashboard design in the field:

  • Putting everything on the dashboard: As the number of cards grows, users can’t find what they’re looking for. Limit the dashboard to “tasks done every day”; leave other links in global navigation.
  • Assigning audiences to individuals: Selecting individual users instead of groups breaks the dashboard at the first staff change. The person who left keeps seeing the card, the newcomer can’t.
  • Publishing without previewing: The preview in the dashboard editor shows how different audiences and the mobile/desktop views look. Check each audience separately.
  • Ownerless custom cards: SPFx cards live as a package in the app catalog; who will update them and which API permissions they use should be recorded. If the card breaks after the developer leaves, there’s nobody to fix it.

Dashboard cards also open a door to reporting content; when bringing management reports to the intranet, apply the permission and RLS checks in the embedding Power BI reports in the intranet guide. The card doesn’t change the report’s permissions.

Publishing as a Teams app

Viva Connections comes as an app published by Microsoft in Microsoft Teams. The admin finds the Viva Connections app under Teams apps > Manage apps in the Teams admin center and proceeds in this order:

  1. Verifies that the app is available in the organization (not blocked).
  2. Customizes the app: the short name (for example the company’s intranet name), icons and color. Users see the intranet name they know in Teams instead of “Viva Connections”; a small but effective step for adoption.
  3. With app setup policies, pins the app to the target users’ app bar and preinstalls it. In the pilot phase, do this with a separate policy assigned only to the pilot group.

If you also plan to offer team-specific business apps in Teams, see the adding a business app to Teams guide for surface choice and deployment policies; the Teams app card on the dashboard provides direct access to these apps.

Mobile experience and navigation

Viva Connections really pays off on mobile. When opened in the Teams mobile app, the dashboard, feed and resources appear as separate tabs. For staff who don’t work at a desk (production, field, retail), this is effectively the only way to access the intranet. This audience doesn’t turn on a computer.

To improve the mobile experience:

  • Evaluate the card order separately for mobile; put the most-used cards in the first two rows.
  • Global navigation supports up to three levels, but on mobile every level means an extra tap. Keep frequently used destinations in the first two levels.
  • Test the pages and apps the cards open one by one on mobile. A card linking to an internal web application that isn’t mobile-friendly undermines trust in the whole dashboard.
  • Check how the title and first image of news posts are cropped in the mobile feed.

The resources section shows the same menu as global navigation in the SharePoint app bar. Don’t keep a separate list of links for Teams; the two lists drift apart after a while. Manage the menu from a single place in the global navigation settings on the home site. The division of roles between global, hub and site navigation is explained in the hub architecture guide.

Adoption and measurement

Viva Connections becomes useful not on the day it’s set up, but when people open it every morning. Plan adoption as part of the technical setup:

  1. Pilot: Two to four weeks with a small group from different roles (office, field, managers). Observe which cards are opened and which links are searched for.
  2. Content ownership: Assign an owner for every card and every navigation link. An ownerless link soon becomes a broken link.
  3. Launch: Widen the pinning policy gradually; in the first weeks, publish a short usage guide as news in the feed.
  4. Measurement: SharePoint site usage reports and page analytics show visits to the home site, and Viva Connections usage analytics show dashboard and card interaction. Remove cards that are never clicked from the dashboard every three months.

Before setup, the SharePoint intranet checklist is a good start for reviewing the intranet’s general planning items (ownership, content lifecycle, search). For intranet design and bringing it into Teams with Viva Connections, you can review our SharePoint intranet and employee portal service. For the product’s current features and license coverage, the Microsoft Viva Connections documentation should be the reference.

Frequently asked questions

Does Viva Connections require a separate license?

The basic Viva Connections experience is included in most Microsoft 365 and Office 365 commercial subscriptions. Advanced features such as multiple experiences may require an additional Viva license. Since license coverage can change, check the subscriptions in your tenant and Microsoft’s current licensing documentation.

Can Viva Connections be used without a home site?

Microsoft offers an experience that works with just the dashboard and feed, without a home site. But if you have an existing SharePoint intranet, setting it up with a home site keeps global navigation and brand elements consistent between Teams and SharePoint.

Can I show dashboard cards differently by department?

Yes. Each card can be targeted at Microsoft 365 or security groups in Entra ID. A card with no audience defined is visible to everyone. Use groups instead of selecting people one by one; maintenance drops when staff change.

Does Viva Connections solve problems in the intranet’s site structure?

No. Viva Connections adds an access layer to existing SharePoint content through Teams. If the site structure is messy, navigation inconsistent or content ownerless, these problems show up in Viva Connections too. Fix the hub and navigation structure first.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Web

We build and maintain corporate websites, WordPress and CMS platforms, intranet and SharePoint portals, document management, and form and approval workflows, and keep them secure and up to date.

Knowledge Center

Other articles