How fast can you respond to a SharePoint production outage?

Support-plan customers get a 15-minute acknowledgement on severity-1 outages through the on-call rotation, with an engineer actively troubleshooting inside 60 minutes twenty-four hours a day. Severity-1 is reserved for tenant-wide inaccessibility, authentication failure, data loss, or search index corruption affecting production business processes. Severity-2 (feature broken for a specific department) is acknowledged inside one business hour. For ad-hoc emergency engagements without an existing contract, an engineer can typically be on a bridge within two hours during US business hours after the engagement agreement is signed. Every incident produces a written root-cause analysis within five business days, including the Microsoft 365 Service Health correlation ID where applicable, change-management entries reviewed, and a hardening recommendation so the same issue does not recur.

What does a tenant-to-tenant SharePoint migration look like?

Tenant-to-tenant migrations run in four phases. Discovery inventories every site collection, OneDrive, Teams, Planner plan, group calendar, and permission assignment, and maps source-to-target identities. Pre-migration remediation fixes unsupported items — external sharing links, orphaned permissions, oversize files, legacy InfoPath forms, and classic workflows — before the first byte moves. Migration executes in waves grouped by business unit, using a combination of ShareGate, Quest On Demand, or native Microsoft cross-tenant tooling depending on scope, content types, and identity model. Cutover runs on a weekend window with delta-sync passes on Friday evening and Sunday morning. Post-migration includes URL mapping for internal links, email communication to end users, guest-access re-invites, and a 30-day hypercare period where an engineer triages every reported issue inside the same day.

How is a SharePoint consulting engagement priced?

Three models fit most organizations. Fixed-fee project pricing works for scoped deliverables — a migration, an intranet rebuild, a branding refresh, or a governance rollout — where requirements can be documented up front. Time-and-materials applies to exploratory work and long-tail enhancements where the backlog changes monthly. Retainer support (priced in hours-per-month tiers from 20 to 200 hours) covers ongoing administration, ticket handling, minor customizations, user training, and emergency response with a guaranteed SLA. Migration scope is typically priced per seat or per gigabyte depending on complexity. Every proposal itemizes what is and is not included, so procurement teams can baseline the quote against competing bids. Microsoft 365 license costs are quoted separately and are not marked up.

Do you support SharePoint Framework (SPFx) custom development?

Yes. SPFx work includes web parts, extensions, field customizers, application customizers, and adaptive card extensions targeting the modern Viva Connections surface. Build pipelines run on Node LTS aligned to the current SPFx generator, with solution packaging, CDN hosting on SharePoint Online or Azure Front Door, and automated deployment through the App Catalog. Every solution ships with accessibility testing (WCAG 2.1 AA), localization hooks, and logging to Application Insights so production issues are traceable. Legacy full-trust or sandbox solutions are refactored onto SPFx using a documented migration pattern rather than a rewrite-from-scratch assumption. Where modern features cannot fully replace a legacy customization, the delta is surfaced early in discovery so stakeholders can decide between a Power Platform alternative, a Graph API solution, or a redesigned business process.

How do you design SharePoint information architecture at scale?

Modern SharePoint is a flat architecture built from hub sites, not nested site collections. Design starts with a persona-driven inventory of content audiences and the tasks they perform, not an org-chart mirror. Hub sites group content by business capability (HR, Finance, Project Delivery, Customer) with a consistent navigation pattern, shared theme, and associated audience targeting. Managed metadata and site columns enforce tagging where taxonomy matters — retention, records, regulated content — while labels in Microsoft Purview drive compliance automation. Search is tuned with promoted results, refiners, and result sources so users find content in fewer clicks. Every site template is published as a site design with a PnP provisioning template, so new sites inherit branding, security, and structure automatically rather than drifting from the standard within three months.

How do you secure SharePoint and enforce Microsoft 365 governance?

Governance is written, published, and enforced by tenant policy — not by tribal knowledge. External sharing is restricted at the tenant and per-site level, with sensitivity labels controlling which sites accept guest access and which block it. Conditional access policies require compliant devices for privileged roles, and risky sign-ins trigger step-up authentication. Microsoft Purview delivers DLP for content in motion, retention labels for records management, and Communication Compliance for regulated industries. SharePoint Advanced Management surfaces oversharing reports, inactive site detection, and restricted-access control for high-value sites. Every tenant gets a written governance charter covering provisioning workflow, naming standards, site lifecycle, backup and restore responsibilities, and the audit cadence. Quarterly governance reviews track policy drift and adjust controls against emerging Microsoft 365 features.

What are the options for migrating from SharePoint on-premises?

SharePoint 2013, 2016, and 2019 all move to SharePoint Online, but the migration path depends on starting version, customization footprint, and data volume. Native Microsoft migration tools cover the majority of document libraries, lists, and permissions. SharePoint Migration Tool handles straightforward farms; the Migration Manager agent model suits large distributed environments. Third-party platforms (ShareGate, Quest, AvePoint) are preferred for complex permission remapping, nested content types, or large metadata hierarchies. InfoPath forms, classic workflows, and full-trust code are evaluated case by case and converted to Power Apps, Power Automate, or SPFx. 2013 workflow is retired from Microsoft 365, so migration plans explicitly schedule workflow replacement. Content older than a retention threshold is archived to Microsoft 365 Archive or Azure Storage rather than moved, reducing target footprint by 20–40 percent on average.

Can you integrate Microsoft 365 Copilot with SharePoint content?

Yes, with governance preceding enablement. Copilot surfaces any content a user can already access through SharePoint, OneDrive, and Teams, so permission hygiene and sensitivity labeling have to be completed before enablement — not afterwards. Integration work covers three tracks. First, SharePoint cleanup: oversharing detection, broken-inheritance remediation, restricted SharePoint search for sites still in flight. Second, content enrichment: sensitivity labels applied at scale, retention policies aligned to record classes, and managed metadata reintroduced for high-value libraries so Copilot has better retrieval signals. Third, operational control: DSPM for AI in Microsoft Purview, Copilot audit log review, and ongoing monitoring of AI-generated activity. Each track produces a before-and-after evidence pack so executive sponsors can see that enablement was controlled, not opportunistic.

What qualifications and experience do your consultants have?

Engineers assigned to client engagements hold current Microsoft 365 certifications (Modern Desktop Administrator, Teams Administrator, Identity and Access Administrator, Security Administrator) plus SharePoint-specific depth — multiple people on the bench have supported SharePoint since the 2007 product cycle. The team includes former Microsoft Most Valuable Professionals, community conference speakers, and active contributors to the PnP community initiative. Every consultant rotates through a quarterly internal lab to rehearse outage scenarios, new Microsoft 365 feature rollouts, and hands-on migration drills. Staffing decisions match the engagement profile: compliance-regulated clients are staffed with engineers who have delivered in that exact vertical before, not generalists. Every project has a named technical lead and a named delivery lead so escalation paths are obvious from day one.

Is the support service offered in multiple languages or time zones?

Support coverage spans US Eastern, US Pacific, UK, and Asia-Pacific time zones through a follow-the-sun rotation for retainer clients on the 24/7 tier. Primary support language is English, with working proficiency in Spanish and French available on a best-effort basis. For clients with strict language requirements, a named engineer can be matched for the duration of the engagement. Ticket submission is available through email, a web portal, and a Teams-integrated bot; severity-1 issues additionally escalate to an on-call phone bridge. All tickets are tracked in a shared ITSM platform with visibility for the client, and monthly service reviews report on SLA attainment, ticket volume trends, and any patterns that justify a proactive hardening project rather than repeated break/fix work.

What is Microsoft Viva Connections?

Viva Connections is the Viva component that surfaces SharePoint content inside Microsoft Teams as a unified employee experience. Employees access a dashboard of action cards, a feed of curated news, and a resource navigation structure, all without leaving Teams. The experience is powered by a designated SharePoint home site and a configured dashboard.

Do we need a SharePoint home site for Viva Connections?

Yes. Viva Connections requires a designated SharePoint home site in the tenant. The home site is a communication site that has been marked as the home site through Set-SPOHomeSite. The home site provides the global navigation, content sources, and landing experience that Viva Connections surfaces inside Teams.

What types of cards work best on the Viva Connections dashboard?

The most effective cards are those that help employees complete tasks rather than just consume content. Approvals cards, Viva Learning cards, Shifts cards (for frontline), assigned tasks cards, and IT service cards drive the strongest engagement. Content-only cards perform less well. Limit total cards per audience to 6 to 10 for best effect.

How do we target Viva Connections content to different audiences?

Use audience targeting on navigation links, dashboard cards, and news articles. Create Microsoft 365 groups or Azure AD security groups that represent the relevant audiences (by role, department, region, or employee type) and apply audience targeting to each content element. Well-targeted content feels personalized even though the underlying system is shared.

Can Viva Connections work for frontline workers?

Yes, and frontline workers are often the highest-value audience for Viva Connections. Design the mobile experience with frontline scenarios in mind: shift display, safety checklists, policy access, and quick task completion. Many organizations provide frontline workers with limited Microsoft 365 licenses that include Viva Connections, which extends the value of the employee experience platform across the workforce.

How do we build custom cards for Viva Connections?

Custom dashboard cards are built using the SharePoint Framework (SPFx) Adaptive Card Extensions (ACE) model. Developers define the card template, the quick view, and the card view using TypeScript and adaptive card schema. Simple cards take 1 to 2 weeks to build; complex cards with external system integration can take 4 to 8 weeks. Cards are deployed through the tenant app catalog.

What is the difference between the Viva Connections feed and SharePoint News?

The Viva Connections feed aggregates content from multiple sources including SharePoint news, organization-wide announcements, and Viva Engage posts. SharePoint News is one of the source types. The feed applies audience targeting, boosting rules, and editorial curation to produce a unified stream. SharePoint News can also be consumed directly through communication sites for users who prefer the SharePoint interface.

How do we measure Viva Connections adoption?

Track monthly active users, weekly active users, dashboard card interactions per user per week, feed engagement rate, and mobile usage share. Healthy enterprise deployments see 50 percent or higher weekly active users within 90 days of launch. Track time-to-action for key tasks surfaced through cards. Review metrics monthly and use the insights to adjust dashboard configuration and feed content.

Viva Connections and SharePoint Home Site Strategy for 2026

The Employee Experience Platform Question

Microsoft Viva Connections is the component of Viva that surfaces SharePoint content inside Microsoft Teams as a unified employee experience. In 2026 it is the primary way that most enterprises intend to modernize the intranet experience. The promise is an employee experience that employees actually use because it lives inside the tool (Teams) where they already spend their workday.

SharePoint architecture diagram showing hub sites, team sites, and content structure — Enterprise SharePoint architecture with hub sites and connected team sites

The promise is real, but the execution is where most implementations stumble. Viva Connections depends on a well-designed SharePoint home site, a carefully curated dashboard, and a feed strategy that delivers value in the first 30 seconds of use. When those pieces are right, Viva Connections produces adoption rates of 60 to 80 percent of active Teams users within 90 days. When they are wrong, it produces a feature that leadership invested in and employees ignore.

This guide walks through the home site architecture that supports Viva Connections, the dashboard design patterns that drive adoption, the feed strategy that keeps content fresh, and the governance model for ongoing operation.

The Home Site Foundation

Viva Connections requires a SharePoint home site. The home site is the top-level landing page for the entire intranet and is the source of the Viva Connections experience inside Teams.

Home Site Technical Requirements

A home site is a communication site that has been designated as the tenant's home site using Set-SPOHomeSite. The designation unlocks several capabilities including enhanced analytics, global navigation integration, and the Viva Connections experience.

```powershell

# Designate a communication site as the home site

Connect-SPOService -Url "https://contoso-admin.sharepoint.com"

Set-SPOHomeSite -HomeSiteUrl "https://contoso.sharepoint.com/sites/home"

# Verify the home site designation

Get-SPOHomeSite

```

Home Site Design Principles

The home site is not just another SharePoint page. It is the gateway to the entire digital workplace. The design principles that matter:

Load in under 2 seconds. Slow home sites destroy adoption. Minimize web parts, use CDN for images, and test performance under realistic conditions.
Personalize without overwhelming. Audience targeting for navigation, news, and content rollups makes the home site feel relevant to each employee without requiring per-employee configuration.
Design for three audiences simultaneously. Executives who visit monthly need different content than operational employees who visit daily. A well-designed home site serves both.
Integrate global navigation. The home site's megamenu becomes the global navigation inside Viva Connections. Invest in the megamenu design.

The Dashboard

The Viva Connections dashboard is the collection of cards that employees see when they open Viva Connections inside Teams. The dashboard is the single most important element of the employee experience because it is what employees see first and most often.

Dashboard Design Principles

Good dashboards follow four principles.

Principle 1: Dashboard-as-a-tool, not dashboard-as-a-newsfeed. Cards should help employees complete tasks, not just consume content. Clock-in cards, benefits enrollment cards, approval action cards, and expense submission cards are the patterns that drive engagement.

Principle 2: Audience targeting on every card. Different employee populations need different cards. A frontline worker needs shift information, safety checklists, and policy access. A corporate knowledge worker needs benefits, learning, and project tools. Use audience targeting to deliver the right cards to the right people.

Principle 3: Limit card count. A dashboard with 20 cards is a dashboard no one reads. Keep the card count to 6 to 10 per audience. Prioritize cards that are actionable and timely.

Principle 4: Prefer high-value cards over novel cards. The card catalog has many options, but the cards that drive engagement are the ones that integrate with systems employees already use. HR systems, IT service desks, approval workflows, and learning platforms all produce high-value cards.

Card Types That Actually Work

The most commonly used cards in enterprise deployments:

Approvals Card: Shows pending approvals from Power Platform, SharePoint, and integrated systems. Drives engagement because it contains actionable work items.
Viva Learning Card: Surfaces relevant learning content for the employee. Works particularly well for role-based learning paths.
Shifts Card (for frontline): Displays the employee's schedule, shift swaps, and clock-in/out actions. Essential for frontline audiences.
Assigned Tasks Card: Pulls tasks from Planner, To Do, and integrated project tools.
ServiceNow or Custom IT Service Card: Lets employees submit tickets and check status without leaving Viva Connections.
Third-Party Integration Cards: Custom cards integrated with business systems like Workday, SAP, or Salesforce drive adoption in the populations that use those systems daily.

Custom Card Development

Custom dashboard cards can be built using the SharePoint Framework (SPFx) Adaptive Card Extensions (ACE) model. Custom cards are appropriate when no prebuilt card meets the need and the use case justifies the development investment. Simple cards take 1 to 2 weeks to build; complex cards with external system integration can take 4 to 8 weeks.

The Feed Strategy

The Viva Connections feed is the stream of news and announcements that employees see below the dashboard. The feed's quality determines whether employees scroll past the dashboard to read more, or leave Viva Connections after completing their dashboard actions.

Content Sources

The feed pulls from multiple sources: SharePoint news from the home site and its associated sites, organization-wide announcements, Yammer (Viva Engage) posts if configured, and custom content through the feed API.

Audience Targeting for Feed

Audience-target every news article. An enterprise-wide announcement goes to everyone. A department announcement goes to the department. A role-specific announcement goes to that role. Without audience targeting, the feed becomes a firehose that nobody reads in detail.

Editorial Cadence

The feed quality depends on editorial cadence. Enterprises that publish 3 to 5 high-quality news items per week sustain engagement. Enterprises that publish 20 items per day burn out their audience. The right cadence depends on the organization size and communication culture, but most large enterprises land in the 3-to-10 items per week range for enterprise-wide content.

Boosted Posts

The feed supports boosted posts that appear at the top of the feed for a specified period. Use boosting sparingly; boosting too many posts erodes the signal. Reserve boosting for truly enterprise-critical announcements.

The Mobile Experience

Viva Connections has a distinct mobile experience inside the Teams mobile app. The mobile experience is particularly important for frontline workers who may only interact with the intranet through mobile.

Mobile-Specific Design

The mobile experience renders the dashboard cards and the feed, but with different sizing and interaction patterns. Design cards with mobile in mind: tap targets should be large, text should be readable at mobile sizes, and card content should work without relying on hover states.

Offline Behavior

Teams has offline support for some content. Viva Connections dashboard cards that work offline (such as schedule display for Shifts) provide value even when the employee is in a low-connectivity environment. Cards that require real-time data should display clear offline states.

Governance Model

Viva Connections requires governance across three dimensions.

Home Site Governance

The home site is the tenant's most-visited page, and it requires active ownership. Assign a dedicated home site owner (typically from internal communications), establish a publication schedule, implement a quarterly review of navigation accuracy, and monitor home site performance with real user metrics.

Dashboard Governance

Dashboard configuration should be managed through a defined change process. Proposed card additions require justification, audience mapping, and performance impact assessment. Cards should be retired when they stop providing value, measured by interaction rates and feedback.

Feed Governance

The feed requires editorial governance to maintain content quality. The pattern that works has a small editorial team (internal communications, HR, IT leadership) that reviews and approves enterprise-wide posts, while departmental contributors can publish within their audience without central approval.

Measurement and Continuous Improvement

The metrics that matter for Viva Connections.

Monthly active users. Percentage of Teams users who opened Viva Connections at least once in the month.
Weekly active users. Percentage who opened it at least once per week. Healthy is 50 percent or higher.
Dashboard card interactions per user per week. Measures whether the dashboard is delivering value.
Feed engagement rate. Percentage of feed items that receive a click, like, or comment.
Mobile usage share. Percentage of usage coming from mobile, particularly important for frontline audiences.
Time to action for key tasks. For actions surfaced through dashboard cards, measure the time from card interaction to task completion.

Review these metrics monthly and use the insights to adjust card configuration, feed content, and home site design.

Common Failure Modes

Three patterns consistently cause Viva Connections rollouts to underperform.

Failure 1: Launching without frontline audience consideration. Viva Connections is most impactful for frontline populations who historically have had limited intranet access. Launching without specific consideration for frontline needs (shift information, safety, compliance tasks) leaves the highest-value audience unengaged.

Failure 2: Copying the old intranet into Viva Connections. Migrating the old intranet's structure into Viva Connections without redesigning for the experience produces a worse version of the old intranet. The opportunity is to redesign the experience around dashboard cards and targeted feeds, not to port the old design.

Failure 3: No ongoing investment. Viva Connections launches well and then stagnates because no one owns continuous improvement. The dashboard ages, the feed becomes stale, and adoption declines over time. The fix is assigning dedicated ownership with a mandate for continuous improvement.

Getting Started

A structured Viva Connections deployment follows a 90-day pattern. Phase 1 (Days 1-30) establishes the home site, designs the initial dashboard, and runs usability tests with representative users. Phase 2 (Days 31-60) deploys to a pilot population of 500 to 2,000 users, iterates based on feedback, and validates the mobile experience. Phase 3 (Days 61-90) rolls out to the full organization with communication, training, and governance structures in place.

Our SharePoint specialists design and deploy Viva Connections across enterprises with internal communications, HR, and IT leadership stakeholders. Contact our team to scope a Viva Connections engagement, or review our SharePoint consulting services for the full methodology.