Microsoft Viva Amplify for internal communications

Internal communications in Microsoft 365 has always been a workflow problem more than a tool problem. The message has to go out as an email, a Teams post, a SharePoint news article, and a Viva Engage post; each is written and formatted separately; someone needs to approve it; and nobody can say afterwards who actually read it. Viva Amplify exists to fix precisely that: write once, get it approved, publish to all four channels from one place, and measure reach. This guide explains what it does, who it's for, what it costs, and where it falls short of the enterprise comms platforms it's compared to.

What Amplify is

Amplify is a campaign tool for communicators. A campaign is a workspace — backed by a SharePoint site, as Viva things tend to be — with an objective, a set of publications, collaborators, and approvers. Each publication is a piece of content written once in Amplify's editor and then adapted for its destinations:

• Outlook — an email to a distribution list or Microsoft 365 group, sent from the comms author or a shared address.
• Teams — a post in one or more channels.
• SharePoint — a news post on a chosen site, with the normal news roll-up to hubs and Viva Connections.
• Viva Engage — a post in a community or a storyline.

Amplify shows a per-channel preview and lets the author tweak each version — a shorter Teams post, a longer email — while keeping one source. Approvals are built in: a publication can be routed to named approvers before it can be published. Scheduling is per channel. After publishing, the analytics view reports reach and engagement per channel: opens and views, reactions, and a campaign-level picture across publications.

That is the whole product, and for a lot of comms teams it's enough: the four-channel-copy-paste problem goes away, approvals stop being email threads, and there's finally one reach number.

Who it's for

Corporate communications, HR comms, change and adoption leads, and anyone who runs a recurring internal campaign — benefits enrolment, a system rollout, a values refresh, quarterly results. It's less relevant for team-level communication (a manager updating their team doesn't need a campaign) and it isn't a replacement for SharePoint news authoring by site owners across the intranet.

Licensing

Amplify is part of the Viva Suite and the Viva Employee Communications and Communities bundle (which pairs it with Viva Engage premium and Viva Connections). It's licensed per author, in effect: the people creating campaigns need the licence; the audience doesn't. That makes it cheap to try for a comms team of five and expensive to imagine as a general tool — which is fine, because it isn't one. Check the current bundle composition; Viva's packaging has shifted more than once and the Goals retirement changed what the Suite contains.

What works well

• The write-once model. The per-channel adaptation is genuinely good: it's not a naive copy, and the previews match what people will see.
• Approvals with a record. Who approved what, when, is visible in the campaign. For regulated internal comms (financial results, safety notices) that's a real control.
• SharePoint news as a first-class destination. News posts published through Amplify are ordinary SharePoint news, so they roll up to Connections and the intranet home like anything else.
• Reach metrics in one place. Comparing email opens to Teams views to news views across a campaign answers the "does anyone read the newsletter" question with data.
• Distribution groups as audiences. Amplify reuses Microsoft 365 groups and distribution lists rather than inventing another audience system.

Where it's thin

Audience targeting. Amplify addresses groups and channels; it doesn't do dynamic segmentation, per-person personalisation, or "everyone in Sweden who hasn't read this" without you building the group. Enterprise comms platforms do; Amplify assumes your groups are already good.

Analytics depth. Reach and engagement per channel, yes. Read-time, click-through inside content, cohort comparisons, and longitudinal dashboards — limited. Exporting to Power BI is the workaround.

Email design. The Outlook output is a clean, responsive email, but the design controls are modest. Comms teams used to a drag-and-drop email builder with brand templates will find it plain. Amplify is not a newsletter design tool.

Rich media and localisation. Video embeds and images work; multilingual campaigns with per-language versions are manual. SharePoint's multilingual news features aren't surfaced through Amplify's authoring.

Reaching people outside Microsoft 365. Frontline staff without mailboxes, contractors on other systems, and SMS or digital-signage channels are out of scope. If your audience isn't in Teams, Outlook, or SharePoint, Amplify doesn't reach them.

It's still maturing. Features arrive steadily and the interface has changed since launch; check the current state before writing a runbook. Copilot assistance in the editor (drafting, tone, summarising for each channel) has been arriving and is useful when it's there.

The decision

If your comms team's pain is publishing to four places and not knowing what landed, Amplify solves that pain directly, cheaply, and inside the tenant you already govern. If the pain is segmenting a complex workforce and designing beautiful newsletters with deep analytics, it's not the tool, and the honest comparison is with a dedicated internal-comms platform — most of which now integrate with Teams and SharePoint anyway.

A good pilot: one campaign, one comms author, approvals turned on, the Viva Engage community included. Four weeks tells you whether the write-once model fits how your team works. It usually does; whether the analytics are enough is the question that decides it.