An internal communications team reviewing a multi-channel campaign plan in the Viva Amplify app, with publication cards for email, SharePoint news, Teams and Viva Engage

By · Published November 2026 · 8 min read

In short

Viva Amplify gives Microsoft 365 comms teams one hub to plan campaigns, write a shared brief and publish to email, SharePoint news, Teams and Viva Engage. We break down how campaigns, roles and prerequisites actually work, and when the tool is more than your team needs.

Key takeaways

  • A Viva Amplify campaign groups publications (emails, SharePoint news, Teams and Viva Engage posts) around one goal, with a shared brief.
  • Only Owners manage campaign settings; Approvers sign off publications; Editors write them, and approvals run through the Teams Approvals app.
  • Before a pilot, confirm Viva suite or Viva Employee Communications and Communities licences, plus OneDrive for Business and Exchange mailboxes.
  • Amplify pays off for recurring multi-channel campaigns; a one-off SharePoint news post or email does not need a campaign structure.
  • Amplify reports per campaign; comparing reach by department and country over time needs a cross-channel measurement layer.

What a campaign means in Viva Amplify

Viva Amplify is Microsoft's campaign workspace for corporate communicators: one place where your team plans, drafts and publishes a set of messages that all serve a single goal. Microsoft defines a campaign as a set of communication materials, called publications, that support one goal, such as raising awareness for a charity event, announcing a product launch or driving enrolment in an employee learning event[1]. If you have been evaluating it as a newsletter editor, reset that expectation: the campaign is the planning container, and the publications inside it are what employees actually receive.

The three building blocks

  • Campaign: the container for one communication goal. Your team works on it together, and you manage every campaign from a central hub rather than from separate tools.
  • Brief: the short document that captures the campaign's objectives and key messages before anyone drafts a publication. Both of Amplify's pre-built campaigns ship with a pre-drafted brief, which shows where Microsoft expects the planning to start[1].
  • Publications: the emails, SharePoint news posts, Teams posts and Viva Engage posts that carry the campaign message. Because campaigns are collaborative, your team can create, edit and approve publications together[1].

You do not have to start from a blank page. Amplify includes two pre-built campaigns you can customise and publish: the Copilot Deployment Kit, which contains eight publications on how to use Microsoft Copilot, and the Viva for AI Transformation campaign, which contains ten pre-drafted publications for leaders communicating their organisation's AI transformation[1]. Both are useful templates for the campaign structure itself, not just the copy.

Two limits matter when you scope your first campaign. Microsoft states that Viva Amplify is not intended for emergency communications, and that it does not support subsites, including publishing to subsites[1]. Plan your crisis comms and any subsite-based publishing elsewhere.

Owners, approvers and editors: who signs off

Every campaign carries its own roles, and the campaign creator assigns them. The three user roles map cleanly onto a typical comms team, so decide who holds each one before you build the campaign rather than after the first approval gets stuck[2].

Role What they do Key permission
Owner Oversees and manages the entire campaign Full control; only owners can manage campaign settings, all campaign members and all roles
Approver Signs off campaign publications and can edit and approve Amplify content, list items and documents Approvers can manage other approvers as needed
Editor Creates and edits campaign publications and can manage lists and campaign materials Editors can view campaign members

In practice, you as the IC manager usually hold the Owner role, because only owners can change campaign settings and membership. Approvers are the people your sign-off path actually runs through: a comms director, a brand or legal reviewer, or a country lead. Editors are the writers producing each channel version. If your approval path today is a thread of email replies, this structure replaces it with something auditable.

One dependency is easy to miss: Amplify approvals are supported by the Approvals app in Teams, so that app needs to be set up before your first approval workflow runs[3]. Separately, a SharePoint admin configures the Amplify admin experience, but that role is only needed for admin-centre settings, not for the day-to-day campaign work your team does[2].

What you need before the first campaign

Most stalled Amplify pilots fail on prerequisites, not on the campaign idea. Run through this checklist before you invite your first editors, so nobody loses a day to a missing mailbox[3].

  1. Licence: users who create or receive campaigns need a Viva suite or Viva Employee Communications and Communities licence. Check this for every pilot participant, not only for you[4].
  2. OneDrive for Business: campaigns are stored in the associated users' OneDrive for Business, so every campaign creator needs it provisioned and working[3].
  3. Exchange mailbox: campaigns require an Exchange mailbox, so confirm Exchange is set up for your campaign creators[3].
  4. Teams Approvals: set up the Approvals app in Teams, because Amplify approvals run through it[3].
  5. SharePoint admin role: only the admin-centre settings need it. Your writers and approvers do not need it, so do not block the pilot waiting for one[3].

Governance settings worth deciding early

Campaigns are private by default, because Microsoft designed them as a private collaborative space for the campaign team, and changing that setting is not recommended[3]. By default, everyone in your organisation can create campaigns, which suits project managers running regular stakeholder updates as much as comms teams. If you want control, an admin can restrict campaign creation to specific people or security groups. Note one technical condition: admins should make sure that users who get campaign-creation access do not have the limited-access user permission lockdown mode enabled for the root site, and in some cases need an additional UseRemoteAPIs permission[3].

Publish once, adapt your message per channel

The publishing model is draft the message once in the campaign, then adapt it per channel. Current Microsoft support documentation confirms the four publication channels: emails, SharePoint news posts, Teams posts and Viva Engage posts, so Viva Engage is a supported channel today, not a promised one[1]. The pre-built campaigns only include the main draft for each publication, and you customise it for each distribution channel to fit your organisation's needs[1].

  • Email reaches employees who live in Outlook, including colleagues who rarely visit the intranet.
  • SharePoint news puts the story on your intranet home, where it stays findable after the send.
  • Teams posts meet people in the flow of their daily operational work.
  • Viva Engage posts open the conversation, when you want comments and questions rather than one-way reach.

Choosing which channel carries which message is its own discipline; our guide to matching each message to the right internal communication channels walks through that decision. For employees, nothing changes in a bad way: they keep seeing relevant messages in their existing preferred channels, because Amplify adapts the delivery rather than forcing everyone into one app[3].

How Microsoft's own comms team runs Amplify campaigns

Microsoft's own internal communicators are the largest user of the tool, and their account of the Microsoft 365 Copilot communications is a useful worked example. They plan their Copilot communications in Viva Amplify and publish across channels that include Viva Engage, running the campaign from one hub instead of coordinating sends tool by tool[5].

  1. Build the brief before the publications. The campaign brief fixes the objectives and key messages first, so every channel version serves the same goal instead of drifting.
  2. Reuse a proven campaign structure instead of starting from a blank page. A campaign that worked, like a deployment kit with a defined set of publications, becomes the template for the next one.

Neither practice depends on Microsoft's scale. Both transfer to any comms team running a recurring programme, which is exactly the situation where Amplify earns its setup cost.

When Amplify is more than you need

Here is the honest decision rule we apply when advising comms teams. Viva Amplify pays off for recurring, multi-channel campaigns that need one brief and one sign-off path: a benefits enrolment drive, a product launch, a Copilot rollout, anything you will run again with several channel versions and named approvers. A one-off single-channel SharePoint news post or a single email does not need that structure around it: in our experience, publishing it directly in SharePoint or Outlook is faster and adds no overhead.

  • Missing prerequisites: without the required licences, OneDrive for Business, an Exchange mailbox or the Teams Approvals app, your team hits setup friction before the first publication is even drafted[3].

If your publishing calendar is mostly occasional news, treat that as a signal rather than a failure. The overhead of roles, briefs and approvals only converts into value when the campaign repeats and the sign-off path gets reused. Match the tool to the cadence, and you will not spend your budget maintaining process for its own sake.

How do campaigns compare across departments?

Amplify's reporting shows you how a campaign and its individual publications are being received, and importing your organisational data enriches those reports with further insight into use and impact[3]. That answers the question each campaign raises while it runs. The question that follows, comparing cross-channel reach by department, country and language across many campaigns over time, is a measurement problem rather than a publishing one, and it is where campaign reports stop. We look at what Amplify's own reports show and where their limits sit in our article on Viva Amplify analytics.

Closing that gap means connecting every channel the campaign touched into one view, which is what our guide to measuring internal communications in Microsoft Viva covers channel by channel. Communication Insights is Tryane's all-in-one cross-channel analytics platform that connects email newsletters, SharePoint, Viva Connections and Viva Engage into one central dashboard, so you can compare reach and engagement segmented by department, country and language, and track how it moves over time instead of campaign by campaign. If that is the comparison your leadership keeps asking for, see what Tryane's Communication Insights does for cross-channel internal communication analytics.

Book a 30-minute call[6] with Hatim to see how Communication Insights measures campaign reach across channels.

Frequently asked questions

What is Viva Amplify?

Viva Amplify is a Microsoft Viva app for organisational communication teams. It centralises campaign planning, multi-channel publishing and reporting in one place: you build a campaign around one goal, draft a brief, adapt publications per channel, and publish from a central hub. It is a planning and publishing layer, not a channel itself: employees keep seeing messages in the channels they already use.

Which channels can Viva Amplify publish to?

Publications can go out as Outlook emails, SharePoint news posts, Teams posts and Viva Engage posts. You draft one message in the campaign and adapt it to fit each channel rather than recreating it from scratch. Microsoft's current support documentation lists all four as supported publication types.

What licence do I need for Viva Amplify?

To create campaigns or receive communications through Viva Amplify, users need either a Microsoft Viva suite licence or a Viva Employee Communications and Communities licence. Teams-integrated features also require a Teams licence, though the web experience works without it. Check licence coverage before a pilot, because the app is only enabled for users with the required licensing.

What are the roles in a Viva Amplify campaign?

Three campaign roles exist. Owners oversee and manage the entire campaign, hold full control, and are the only ones who can manage campaign settings and members. Approvers approve campaign publications and can manage other approvers. Editors create and edit publications and can view campaign members. The campaign creator assigns these roles, and a SharePoint admin configures the Amplify experience.

What should I check before creating our first campaign?

Three prerequisites: users need OneDrive for Business because campaigns are stored in the associated users' OneDrive, an Exchange mailbox is required to create campaigns, and the Approvals app in Teams must be set up if you want approval workflows. Also decide who may create campaigns: by default everyone in the organisation can, and admins can restrict creation to specific people or security groups.

Is Viva Amplify suitable for every internal message?

No. Microsoft states that Viva Amplify is not intended for emergency communications, and it does not support subsites. As a rule of thumb, use it for recurring multi-channel campaigns that need one brief and one sign-off path; for a one-off single-channel news post or email, publishing directly in SharePoint or Outlook is faster and adds no overhead.

Does Viva Amplify replace our intranet or newsletter tool?

No. Amplify is a campaign planning and publishing layer on top of the channels you already run. Employees continue to see messages in their existing preferred channels, such as Outlook, Teams, SharePoint and Viva Engage. Amplify changes how you plan, approve and publish, not where employees read.

Can Viva Amplify report reach by department or country?

Amplify's reporting shows the reach and impact of a campaign and its individual publications, and importing organisational data can enrich those reports. But comparing cross-channel reach by department, country or language across many campaigns over time goes beyond a single campaign's report; that longitudinal, segmented view is what dedicated cross-channel analytics such as Communication Insights provide.

Sources

• support.microsoft.com

• learn.microsoft.com

• learn.microsoft.com

• microsoft.com

• microsoft.com

• calendly.com

Further reading

• Viva Amplify analytics: what reports show and their limits

• Microsoft 365 usage analytics: what it tells comms teams

• Viva Engage: what it is and how comms teams use it

• Teams vs Viva Engage: Which One for Internal Comms?

If you want to see what cross-channel reporting looks like against your real data, Tryane runs a 15-minute walkthrough with no slides. Book a slot with Jérémy.