Microsoft is preparing to bring Viva Amplify campaign management directly into SharePoint sites, creating a lighter-weight way for corporate communications teams to organize related news posts, distribute messages, and review campaign performance without leaving the place where much of that content is authored.
The new capability, described as Campaigns in SharePoint or site campaigns, is currently listed as in development for Microsoft Viva. General availability is expected in August 2026 for commercial worldwide multi-tenant Microsoft 365 environments, with availability through both Targeted Release and General Availability release rings. The feature is initially limited to users licensed for Viva Amplify.
For organizations that already rely on SharePoint news as the backbone of employee communications, this could prove to be a consequential usability improvement. Rather than treating a news site as the publishing destination and Viva Amplify as a separate campaign workspace, Microsoft is moving campaign-level organization and reporting closer to the SharePoint news experience itself.
That distinction matters. Corporate communications is rarely about publishing one isolated post. It is about coordinating a sequence of announcements, updates, executive messages, deadlines, policy reminders, and follow-up content around one business objective. Site campaigns aim to make that process more manageable inside the SharePoint environment communications teams already use every day.
Campaigns in SharePoint are positioned as a complementary option to the established Viva Amplify campaign experience. They are not described as a wholesale replacement for full Viva Amplify campaigns, nor are they simply another label for SharePoint news.
Instead, site campaigns are intended to help communicators:
A typical use case could include a benefits enrollment period, an office relocation, a cybersecurity awareness month, a companywide technology rollout, a leadership communications series, or a change-management initiative. Each program may involve multiple news posts, but the business wants to assess the performance of the entire initiative rather than judge every article in isolation.
In practical terms, site campaigns could turn a collection of related SharePoint news articles into a measurable communications program.
Yet campaign management has historically introduced a separation between where content lives and where campaign work is organized. Viva Amplify addressed the broader communications challenge by offering coordinated publishing and reporting across channels such as SharePoint, Outlook, Teams, and Viva Engage. That remains valuable for broad, multi-channel campaigns.
The issue is that many campaigns begin and end in SharePoint.
A communications team might publish five news posts over several weeks, promote selected articles elsewhere, and then attempt to combine the resulting performance data manually. Without a campaign container at the site level, the relationship among those posts can be obvious to the communications team but less visible in the tooling.
Site campaigns bring campaign context into the SharePoint workflow.
Without an explicit campaign framework, each post may be measured separately through page views, readership signals, reactions, and link activity. That information is useful, but it can obscure the larger question: Did the complete communication program reach its intended audience and move them toward the intended action?
Campaigns in SharePoint are designed to close some of that gap by giving associated news posts a shared organizational and analytical context.
Communications professionals already spend significant time moving among:
That is especially relevant for lean communications teams. A large enterprise may have dedicated campaign managers and specialists who can operate a separate communications platform. Smaller teams often have the same SharePoint owners serving as writers, designers, publishers, analysts, and intranet administrators.
For those teams, the appeal of SharePoint campaign analytics is likely to be immediate.
Viva Amplify has been built around coordinated employee communications. Its full campaign experience supports planning through campaign briefs, collaboration with campaign members, publication creation, distribution across communication channels, and centralized reporting.
That more comprehensive model remains appropriate where communications teams need to reach employees across multiple endpoints with tailored versions of the same message.
Likely examples include:
A communications department should treat the two approaches as different levels of operational maturity:
The important operational question is not whether site campaigns are “better” than Viva Amplify campaigns. It is whether the additional planning and distribution features of a full campaign are necessary for the communications objective at hand.
SharePoint already provides analytics around individual pages and news posts. Viva Amplify extends campaign reporting with signals that can help communications teams evaluate reach, engagement, promotions, time spent, audience behavior, and channel performance.
The new site campaigns capability is expected to provide campaign analytics directly from SharePoint, allowing teams to evaluate a connected news initiative without treating reporting as a separate afterthought.
Consider an employee enrollment campaign. The announcement article may generate strong initial readership because it introduces the topic. The later “how to complete your enrollment” article may have fewer readers, but those readers could be more valuable because they are closer to taking action.
Campaign-level analysis helps communicators look at the program as a whole rather than rewarding the loudest or earliest post.
Potential campaign measures may help teams understand:
For example, a benefits campaign should be measured not only through readership but also through enrollment completion. A security campaign should be considered alongside phishing-reporting rates, training completion, or incident trends. A change-management campaign should be assessed against adoption, support tickets, and feedback.
High page views may reflect a compelling headline, executive visibility, or even employee confusion. Long time spent could indicate deep reading, but it could also indicate that a page was difficult to understand. Reactions may show interest, but they are not necessarily evidence of action.
A mature SharePoint communications strategy should define success before publishing. That means deciding which signals matter for each campaign:
A SharePoint communications team should not assume that every site owner, page editor, or news author will automatically receive access merely because they use SharePoint Online. Eligibility is expected to depend on Viva Amplify licensing and the organization’s Microsoft 365 configuration.
Feature scope, timing, licensing conditions, regional availability, and interface details can change before rollout. Organizations should avoid designing mandatory business processes around site campaigns until the feature appears in their tenant and Microsoft publishes final operational documentation.
The inclusion of both Targeted Release and General Availability suggests that selected organizations may see the capability earlier. However, early exposure should be used for validation rather than immediate enterprise-wide standardization.
Not every collection of related news deserves to become a formal campaign. A site campaign should represent a deliberate communications effort with a shared objective, a defined audience, and a meaningful measurement plan.
If every monthly newsletter, project update, or routine announcement becomes a campaign, the SharePoint experience may become cluttered. Analytics may become less meaningful, reporting becomes harder to compare, and communications teams can lose sight of truly strategic initiatives.
A SharePoint site campaign should generally include most of the following:
For example, weekly department updates may be better managed through normal SharePoint news and editorial tagging. A multi-week initiative to explain a major restructuring, however, may warrant campaign treatment because it has higher stakes, multiple messages, and a need for aggregated performance analysis.
Communications teams should decide whether a campaign is primarily an editorial grouping, a reporting grouping, a navigation experience, or a combination of all three. If the organization tries to use the feature as the answer to every information architecture problem, the result could be confusing.
While the new feature is focused on campaign organization and analytics, it should still be evaluated through the same governance lens applied to SharePoint and Viva Amplify more broadly.
Each campaign should have:
Aggregated campaign performance is generally most useful when it identifies where content needs improvement. For instance, low engagement from a region might suggest a localization issue, poor timing, insufficient manager reinforcement, or limited relevance.
It should not be used casually to make assumptions about individual employees’ commitment, awareness, or productivity.
The feature’s initial applicability to Amplify users means licensing and permissions will affect adoption from day one. A centralized communications team may already be covered, while regional or departmental authors may not be.
Good candidates often include:
For each recurring program, document:
A predictable convention might include a business area, campaign purpose, and time period. For example, a communications team could standardize on formats such as:
A pilot should test:
Rather than requiring communications teams to think of SharePoint, Viva, Teams, Outlook, and employee communities as entirely separate silos, Microsoft continues to connect them through common authoring, publishing, engagement, and measurement experiences.
SharePoint increasingly operates as more than a document management platform or intranet page builder. It is becoming a communications foundation that can support publishing workflows, organizational news, audience targeting, content promotion, branded experiences, and increasingly sophisticated analysis.
Viva Amplify, meanwhile, remains the layer for communications orchestration. By bringing a portion of that orchestration into SharePoint through site campaigns, Microsoft is acknowledging that not every communications program requires the same complexity.
That is a sensible product direction. The best internal communications tools do not force every message into an enterprise-scale campaign model. They let teams choose the right level of structure for the importance, duration, audience, and distribution needs of the communication.
Its greatest strength is likely to be workflow simplification. Communications teams may be able to group related news posts, retain a campaign perspective, and analyze performance without leaving the SharePoint context where their content lives. That could make campaign discipline more accessible to teams that need better organization and reporting but do not require a full multi-channel communications operation for every initiative.
The limitations are equally clear. The feature is initially tied to Viva Amplify users, it remains in development, and its lighter-weight positioning means it should not be expected to replace complete Amplify campaigns. Organizations will also need disciplined governance to prevent campaign sprawl, misleading analytics, and unnecessary duplication of existing SharePoint content structures.
For Microsoft 365 administrators, intranet owners, and corporate communications leaders, the most practical next step is to identify the SharePoint news programs that would benefit from campaign-level organization and define success measures in advance. If the final rollout delivers the promised native SharePoint experience and meaningful campaign analytics, site campaigns could become a valuable middle ground between a standalone news post and a fully orchestrated Viva Amplify communications campaign.
The new capability, described as Campaigns in SharePoint or site campaigns, is currently listed as in development for Microsoft Viva. General availability is expected in August 2026 for commercial worldwide multi-tenant Microsoft 365 environments, with availability through both Targeted Release and General Availability release rings. The feature is initially limited to users licensed for Viva Amplify.
For organizations that already rely on SharePoint news as the backbone of employee communications, this could prove to be a consequential usability improvement. Rather than treating a news site as the publishing destination and Viva Amplify as a separate campaign workspace, Microsoft is moving campaign-level organization and reporting closer to the SharePoint news experience itself.
That distinction matters. Corporate communications is rarely about publishing one isolated post. It is about coordinating a sequence of announcements, updates, executive messages, deadlines, policy reminders, and follow-up content around one business objective. Site campaigns aim to make that process more manageable inside the SharePoint environment communications teams already use every day.
Overview: What Campaigns in SharePoint Are Intended to Do
Campaigns in SharePoint are positioned as a complementary option to the established Viva Amplify campaign experience. They are not described as a wholesale replacement for full Viva Amplify campaigns, nor are they simply another label for SharePoint news.Instead, site campaigns are intended to help communicators:
- Group related SharePoint news posts under a common campaign
- Create and manage campaigns directly from a SharePoint site
- Maintain the existing SharePoint-centric content authoring workflow
- Access campaign-oriented analytics from within SharePoint
- Reduce the administrative friction of organizing a multi-post communication initiative
- Keep communications planning and performance tracking near the news content itself
A typical use case could include a benefits enrollment period, an office relocation, a cybersecurity awareness month, a companywide technology rollout, a leadership communications series, or a change-management initiative. Each program may involve multiple news posts, but the business wants to assess the performance of the entire initiative rather than judge every article in isolation.
In practical terms, site campaigns could turn a collection of related SharePoint news articles into a measurable communications program.
Why the SharePoint Integration Matters
SharePoint has long been central to Microsoft 365 intranet and employee communications strategies. It hosts modern sites, organizational news, page libraries, hubs, document repositories, and often the editorial home for internal communications teams.Yet campaign management has historically introduced a separation between where content lives and where campaign work is organized. Viva Amplify addressed the broader communications challenge by offering coordinated publishing and reporting across channels such as SharePoint, Outlook, Teams, and Viva Engage. That remains valuable for broad, multi-channel campaigns.
The issue is that many campaigns begin and end in SharePoint.
A communications team might publish five news posts over several weeks, promote selected articles elsewhere, and then attempt to combine the resulting performance data manually. Without a campaign container at the site level, the relationship among those posts can be obvious to the communications team but less visible in the tooling.
Site campaigns bring campaign context into the SharePoint workflow.
From individual posts to a connected communications narrative
A news post can explain a single announcement effectively. But large internal initiatives normally unfold in stages:- An initial announcement establishes awareness.
- A follow-up article explains what is changing.
- A leadership message adds urgency or context.
- A how-to guide helps employees take action.
- A deadline reminder reinforces participation.
- A final update closes the loop and reports outcomes.
Without an explicit campaign framework, each post may be measured separately through page views, readership signals, reactions, and link activity. That information is useful, but it can obscure the larger question: Did the complete communication program reach its intended audience and move them toward the intended action?
Campaigns in SharePoint are designed to close some of that gap by giving associated news posts a shared organizational and analytical context.
Less context switching for communications teams
The strongest argument for this feature is not that it introduces an entirely new communications model. It is that it may remove unnecessary transitions between tools.Communications professionals already spend significant time moving among:
- SharePoint news authoring
- Editorial calendars
- Approval processes
- Brand and asset libraries
- Microsoft Teams discussions
- Email distribution planning
- Analytics dashboards
- Reporting presentations
That is especially relevant for lean communications teams. A large enterprise may have dedicated campaign managers and specialists who can operate a separate communications platform. Smaller teams often have the same SharePoint owners serving as writers, designers, publishers, analysts, and intranet administrators.
For those teams, the appeal of SharePoint campaign analytics is likely to be immediate.
How Site Campaigns Fit Alongside Viva Amplify
The key to understanding this roadmap item is recognizing that Microsoft is extending, rather than discarding, the Viva Amplify model.Viva Amplify has been built around coordinated employee communications. Its full campaign experience supports planning through campaign briefs, collaboration with campaign members, publication creation, distribution across communication channels, and centralized reporting.
That more comprehensive model remains appropriate where communications teams need to reach employees across multiple endpoints with tailored versions of the same message.
The full Viva Amplify scenario
A traditional Viva Amplify campaign remains the better fit when an organization needs:- Multi-channel publishing to SharePoint, Outlook, Teams, and Viva Engage
- A structured campaign brief with goals and key messages
- Multiple coordinated publications across several formats
- Cross-channel audience targeting
- Centralized campaign collaboration
- A broader campaign planning environment
- Detailed reporting across communication endpoints
The site campaign scenario
A SharePoint site campaign appears better suited to communications that are centered on a particular SharePoint site and built primarily around SharePoint news.Likely examples include:
- A departmental transformation initiative
- A site-specific editorial series
- A recurring executive communications program
- A product or service launch for internal audiences
- A policy awareness series
- A regional business update campaign
- A security or compliance education effort
- A short-term employee action campaign
Complementary, not interchangeable
Organizations should avoid assuming that site campaigns will replicate every Viva Amplify capability. Microsoft’s roadmap description specifically frames them as a complementary, lighter-weight option. That language should set expectations.A communications department should treat the two approaches as different levels of operational maturity:
| Communications need | Most suitable approach |
|---|---|
| One standalone internal article | SharePoint news post |
| A group of related SharePoint news posts | SharePoint site campaign |
| A coordinated campaign across email, Teams, SharePoint, and Viva Engage | Full Viva Amplify campaign |
| A high-priority news article needing greater visibility in Viva Connections | SharePoint news boosting |
| A published news post that needs expanded distribution to other channels | Amplify promotion from SharePoint |
Campaign Analytics Move Closer to the Newsroom
Campaign analytics may become the most compelling element of this rollout for intranet owners and internal communicators.SharePoint already provides analytics around individual pages and news posts. Viva Amplify extends campaign reporting with signals that can help communications teams evaluate reach, engagement, promotions, time spent, audience behavior, and channel performance.
The new site campaigns capability is expected to provide campaign analytics directly from SharePoint, allowing teams to evaluate a connected news initiative without treating reporting as a separate afterthought.
Why campaign-level reporting is more useful than page views alone
A single high-performing news post does not necessarily mean a campaign succeeded. Conversely, a post with modest traffic may still play an essential role in a longer communications sequence.Consider an employee enrollment campaign. The announcement article may generate strong initial readership because it introduces the topic. The later “how to complete your enrollment” article may have fewer readers, but those readers could be more valuable because they are closer to taking action.
Campaign-level analysis helps communicators look at the program as a whole rather than rewarding the loudest or earliest post.
Potential campaign measures may help teams understand:
- Overall readership across related news posts
- Engagement trends over the life of the campaign
- Whether attention increased after follow-up content
- Which topics or formats generated more interaction
- Whether later posts sustained awareness or lost momentum
- Which communications deserve additional promotion
- Whether a campaign reached the intended audience before a key deadline
For example, a benefits campaign should be measured not only through readership but also through enrollment completion. A security campaign should be considered alongside phishing-reporting rates, training completion, or incident trends. A change-management campaign should be assessed against adoption, support tickets, and feedback.
Analytics should guide decisions, not create vanity metrics
The risk of campaign dashboards is that they can lead teams to optimize for activity rather than outcomes.High page views may reflect a compelling headline, executive visibility, or even employee confusion. Long time spent could indicate deep reading, but it could also indicate that a page was difficult to understand. Reactions may show interest, but they are not necessarily evidence of action.
A mature SharePoint communications strategy should define success before publishing. That means deciding which signals matter for each campaign:
- Awareness campaigns: Reach, unique viewers, readership across target groups
- Education campaigns: Time spent, repeat visits, downloads, video completion, feedback
- Action campaigns: Link clicks, form completions, registrations, enrollments, training completion
- Change campaigns: Engagement plus adoption metrics from the affected service or process
- Leadership campaigns: Readership, reactions, comments, and qualitative employee sentiment
Licensing and Availability Limitations
The roadmap indicates that Campaigns in SharePoint will initially apply only to Viva Amplify users. This is a significant constraint and should shape early rollout planning.A SharePoint communications team should not assume that every site owner, page editor, or news author will automatically receive access merely because they use SharePoint Online. Eligibility is expected to depend on Viva Amplify licensing and the organization’s Microsoft 365 configuration.
What this means for administrators
Microsoft 365 administrators and Viva administrators should prepare to answer several practical questions:- Which employees currently have Viva Amplify licenses?
- Which users should be permitted to create site campaigns?
- Will campaign creation be limited to central communications teams?
- Can departmental communicators create campaigns independently?
- Which SharePoint sites should support formal campaigns?
- How will campaign ownership be handled when employees change roles?
- What governance applies to naming, branding, retention, and reporting?
- How will leaders distinguish official campaigns from ad hoc editorial groupings?
Release timing should be treated as a target, not a guarantee
The roadmap currently lists the feature as in development with a planned general availability timeframe of August 2026. Microsoft 365 roadmap dates are useful planning signals, but they are not contractual release commitments.Feature scope, timing, licensing conditions, regional availability, and interface details can change before rollout. Organizations should avoid designing mandatory business processes around site campaigns until the feature appears in their tenant and Microsoft publishes final operational documentation.
The inclusion of both Targeted Release and General Availability suggests that selected organizations may see the capability earlier. However, early exposure should be used for validation rather than immediate enterprise-wide standardization.
Governance: The Risk of Turning Every News Series Into a Campaign
The main risk in making campaign management easier is that organizations may use it too broadly.Not every collection of related news deserves to become a formal campaign. A site campaign should represent a deliberate communications effort with a shared objective, a defined audience, and a meaningful measurement plan.
If every monthly newsletter, project update, or routine announcement becomes a campaign, the SharePoint experience may become cluttered. Analytics may become less meaningful, reporting becomes harder to compare, and communications teams can lose sight of truly strategic initiatives.
Establish a clear campaign threshold
A simple governance framework can help distinguish campaigns from routine publishing.A SharePoint site campaign should generally include most of the following:
- A defined business or communications objective
- A named owner accountable for performance
- Two or more related SharePoint news posts
- A target audience or employee segment
- A planned publishing sequence
- A clear start and end point
- A measurement approach
- A decision about what happens after the campaign closes
For example, weekly department updates may be better managed through normal SharePoint news and editorial tagging. A multi-week initiative to explain a major restructuring, however, may warrant campaign treatment because it has higher stakes, multiple messages, and a need for aggregated performance analysis.
Avoid duplicate content structures
SharePoint already provides several methods to organize content, including:- Site navigation
- News web parts
- Page metadata
- Managed properties
- Hub sites
- Highlighted content web parts
- Editorial calendars
- Topic pages
- Document libraries
- Viva Connections experiences
Communications teams should decide whether a campaign is primarily an editorial grouping, a reporting grouping, a navigation experience, or a combination of all three. If the organization tries to use the feature as the answer to every information architecture problem, the result could be confusing.
Security, Compliance, and Content Lifecycle Considerations
Campaigns in SharePoint will sit inside an environment that can contain highly sensitive employee communications. Leadership announcements, policy changes, labor-related updates, benefits details, restructuring information, and security guidance all require careful handling.While the new feature is focused on campaign organization and analytics, it should still be evaluated through the same governance lens applied to SharePoint and Viva Amplify more broadly.
Campaign ownership needs a lifecycle plan
Campaigns can outlive the people who create them. An employee may leave the organization, change departments, or lose the context required to manage future follow-up communications.Each campaign should have:
- A primary owner
- At least one backup owner
- Defined editing permissions
- A retention expectation
- A closeout process
- A decision on whether content should remain prominently discoverable
- A process for archiving or updating outdated guidance
Analytics introduce privacy and interpretation questions
Communications analytics can be valuable, but organizations should be transparent about how data is used. The goal should be to understand the effectiveness of messages, not to turn internal communications into employee surveillance.Aggregated campaign performance is generally most useful when it identifies where content needs improvement. For instance, low engagement from a region might suggest a localization issue, poor timing, insufficient manager reinforcement, or limited relevance.
It should not be used casually to make assumptions about individual employees’ commitment, awareness, or productivity.
Recommended Preparation for IT and Communications Teams
Although the feature is not yet generally available, organizations can prepare without overcommitting to an unreleased workflow.Review Viva Amplify entitlement and ownership
Start by identifying current Viva Amplify users and understanding whether they align with the people who own SharePoint news publishing.The feature’s initial applicability to Amplify users means licensing and permissions will affect adoption from day one. A centralized communications team may already be covered, while regional or departmental authors may not be.
Inventory recurring communications programs
Identify communications initiatives that already depend on several related SharePoint news posts.Good candidates often include:
- Annual benefits and enrollment communications
- Seasonal business updates
- Employee experience initiatives
- Transformation programs
- Corporate responsibility campaigns
- Change-management communications
- Security awareness series
- Major IT service rollouts
- Leadership communications cycles
Define success measures before implementation
Do not wait for a dashboard to decide what a successful campaign looks like.For each recurring program, document:
- The intended audience.
- The desired employee outcome.
- The SharePoint content sequence.
- The relevant engagement signals.
- The operational metric that validates real-world impact.
- The cadence for reviewing results.
- The person responsible for making changes based on findings.
Build a naming and metadata convention
Consistency will matter as campaigns accumulate.A predictable convention might include a business area, campaign purpose, and time period. For example, a communications team could standardize on formats such as:
HR - Benefits Enrollment - FY27IT - Device Refresh - Wave 1Security - Passwordless Adoption - Employee CampaignOperations - Safety Week - North America
Pilot before standardizing
Once the feature is available, begin with a small number of campaigns that have clear objectives and active owners.A pilot should test:
- Campaign creation experience
- News-post association workflow
- Permissions behavior
- Analytics usefulness
- Reporting clarity for leadership
- Accessibility and employee discoverability
- Interaction with existing SharePoint news processes
- Administrative burden
- Suitability for departmental versus enterprise-wide communications
The Broader Direction of Microsoft 365 Communications
Campaigns in SharePoint reflect a broader Microsoft 365 trend: bringing specialized capabilities into the places where employees already work.Rather than requiring communications teams to think of SharePoint, Viva, Teams, Outlook, and employee communities as entirely separate silos, Microsoft continues to connect them through common authoring, publishing, engagement, and measurement experiences.
SharePoint increasingly operates as more than a document management platform or intranet page builder. It is becoming a communications foundation that can support publishing workflows, organizational news, audience targeting, content promotion, branded experiences, and increasingly sophisticated analysis.
Viva Amplify, meanwhile, remains the layer for communications orchestration. By bringing a portion of that orchestration into SharePoint through site campaigns, Microsoft is acknowledging that not every communications program requires the same complexity.
That is a sensible product direction. The best internal communications tools do not force every message into an enterprise-scale campaign model. They let teams choose the right level of structure for the importance, duration, audience, and distribution needs of the communication.
Final Assessment
Campaigns in SharePoint has the potential to be a meaningful enhancement for organizations that use SharePoint news heavily and already invest in Viva Amplify.Its greatest strength is likely to be workflow simplification. Communications teams may be able to group related news posts, retain a campaign perspective, and analyze performance without leaving the SharePoint context where their content lives. That could make campaign discipline more accessible to teams that need better organization and reporting but do not require a full multi-channel communications operation for every initiative.
The limitations are equally clear. The feature is initially tied to Viva Amplify users, it remains in development, and its lighter-weight positioning means it should not be expected to replace complete Amplify campaigns. Organizations will also need disciplined governance to prevent campaign sprawl, misleading analytics, and unnecessary duplication of existing SharePoint content structures.
For Microsoft 365 administrators, intranet owners, and corporate communications leaders, the most practical next step is to identify the SharePoint news programs that would benefit from campaign-level organization and define success measures in advance. If the final rollout delivers the promised native SharePoint experience and meaningful campaign analytics, site campaigns could become a valuable middle ground between a standalone news post and a fully orchestrated Viva Amplify communications campaign.