A SharePoint news post displayed across surfaces: the SharePoint start page on a laptop, a News web part on an intranet page, and the SharePoint app in Microsoft Teams on a mobile phone

By · Published November 2026 · 11 min read

In short

A SharePoint news post only reaches the employees whose surfaces pick it up. Decide where your post must appear first, then choose the site, the boost and the News web part settings that get it there, and check who actually read it.

Key takeaways

  • Posts from organization news sites get special treatment and appear on the SharePoint start page; administrators can designate up to 100 of them.
  • A communication site set as the home site is automatically configured as an organization news site.
  • The SharePoint app in Teams (formerly Viva Connections) News reader shows organizational news, boosted news and followed-site news.
  • Boost works from organization news sites only: prominent display for up to 4 days, with a maximum of 10 boosted posts per site.
  • Page analytics splits viewers across Outlook, SharePoint, Teams and Engage, but the channel breakdown requires a Viva Suite or Viva Communications and Communities licence.
  • Native analytics does not break news readership down by department, country or role, which is the gap IC managers need to close.

Why where your news post lands decides who reads it

You publish a news post, the headline is clear, the image is right, and the views still stay low. In most cases the content is not the problem. The problem is that the surfaces your employees actually open never picked the post up. A SharePoint news post does not broadcast itself: it appears only where a surface is configured to show it, and each surface has its own conditions. If you decide placement after you write the post, you have already limited who can read it.

We see this pattern regularly in Microsoft 365 organisations: the post lands on a site few employees follow, no News web part is configured to pull it in, and the SharePoint app in Teams never surfaces it. The result looks like disinterest, but it is a distribution gap. If you recognise it, our analysis of why SharePoint communications go unread breaks the aggregate view count into the distinct failures behind it why SharePoint news goes unread.

The way out is to work backwards through a fixed sequence. Decide each step before you publish, and the post reaches the people it was written for:

  1. Pick the surface where the post must appear first: the SharePoint start page, a News web part, or the SharePoint app in Teams.
  2. Choose the site to publish from, because the site determines which surfaces can carry the post.
  3. Boost the post if it is a priority, within the limits Microsoft sets.
  4. Configure the News web part settings that decide who sees what.
  5. Measure who actually read it, per post and per channel, and adapt your strategy.

One surface deserves special attention: the SharePoint app in Teams, formerly Viva Connections. Its News reader aggregates SharePoint news from across your organizational sites, boosted news, the user's followed sites, frequent sites, and people the user works with[1]. That list is your checklist: a post from an unmarked site, unboosted and on no followed site, appears in none of those streams.

Where does a news post actually show up?

Before you write the next post, map every surface it can appear on and what each one needs to pick it up. The surfaces are few, but their conditions differ, and a post that satisfies none of them is effectively invisible.

Surface What it needs to pick up your post
SharePoint start page The post must come from an organization news site; these posts get special visual treatment and appear on the start page[2]
News web part on a site The web part's news source must include the publishing site: this site, all sites in the hub, selected sites, or recommended for current user[3]
SharePoint app in Teams (formerly Viva Connections) The News reader shows organizational news, boosted news, followed sites, frequent sites and people the user works with[1]
Email You send the post manually from the post itself; there is no automatic push to inboxes for a single post

The SharePoint app in Teams is built on SharePoint home site technology and is accessible through Microsoft Teams or the web from desktop, mobile and tablet devices, which makes it the surface your frontline and mobile employees actually live in[1]. Its four primary components are News, dashboard, announcements and resources, and News is the one that carries your posts[1].

Now the uncomfortable part: publish a post on an ordinary team site that nobody follows, with no web part configured to show it and no boost, and it may appear on none of these surfaces. It exists, it has a URL, and it will not reach anyone who does not already visit that exact site. That is why the publishing site, the next decision, matters more than anything you write in the post.

Which site should you publish news from?

The site you publish from is not an administrative detail. It determines which surfaces can carry the post at all, so make the decision deliberately. If you are unsure how the site types differ in day-to-day use, our comparison of a SharePoint communication site vs team site walks through the decision test.

  • Team sites: for working groups. News here serves collaboration around a project or a department, not broad broadcast.
  • Communication sites: for broad broadcast. Use them when the audience is wider than the team that writes the posts.
  • Hub sites: to roll news up. A News web part set to all sites in the hub pulls posts from every site connected to the hub, so hub membership extends your reach[3].
  • Organization news sites: for company-wide, authoritative news. SharePoint Administrators can designate up to 100 of them, and their posts get special visual treatment and appear on the SharePoint start page[2].

There is a shortcut worth knowing: if you set a communication site as the home site for your organization, it is automatically configured as an organization news site[2]. If your home site already publishes the company-wide news, that post stream is already on the start page without extra configuration.

A practical rule for your editorial plan: company-wide announcements belong on an organization news site, departmental news belongs on the department's communication site connected to the right hub, and working-group updates stay on team sites. Match each message to one channel and one site, and the surfaces above can do their job.

How do you make a priority post stand out?

Even on the right site, a priority post competes with everything else published that day. Boost is the only native mechanism that pushes a post above that noise, and it comes with hard limits you should plan around before publishing day[4].

  • Boosted news displays prominently for up to 4 days and carries a lightning bolt icon[4].
  • A maximum of 10 news posts can be boosted for each organization news site[4].
  • You can boost news posts from organization news sites only, and you need edit permissions on the site[4].
  • Boosted news appears in the Viva Connections experiences, in auto news digests and in the News web part[4].

Two of those limits shape your editorial calendar directly. First, the 10-post cap per organization news site means boost is a rationed resource: if everything is a priority, nothing is, so reserve it for the posts that genuinely must be seen. Second, Microsoft notes that news boost is most effective when applied close to the time of publishing, because newer posts from organization news sites take precedence over older boosted news that has not yet expired[4]. Boost at publication, not days later.

You can also control order manually. Boosted news can be ordered to determine which shows first, and in the News web part you can pin posts into numbered positions so the most important story appears at the top, with remaining positions following publish date[4]. Use pinning for posts that are not restricted to a small group, because pinned titles and thumbnails are visible to all site users regardless of permissions[3].

Which News web part settings change who sees what?

Publishing from the right site gets the post into the system; the News web part settings decide which employees actually see it on the pages they visit. Two people can visit the same intranet page and see entirely different news, depending on how the web parts on it are configured.

  • This site: shows only posts from the site the page belongs to. Safe, but narrow.
  • All sites in the hub: pulls posts from every site in the hub, ideal for a hub page that aggregates a business area.
  • Select sites: pulls posts from one or more sites you name, useful for a curated leadership news panel.
  • Recommended for current user: shows posts from people the user works with, their management chain, their top 20 followed sites and frequently visited sites, so every employee sees a personalised feed[3].
  • Boosted posts: displays only posts boosted from your organization news sites, the setting to use on your home page for priority news[4].

Layout choices change engagement as well: team sites default to Top story, communication sites to Side-by-side, hub sites to Hub news, and Carousel, Tiles, List and Filmstrip layouts each present a different number of stories with different visual weight[3]. Audience targeting on the web part narrows visibility further, showing news content only to the groups you specify.

Finally, for employees who never open the intranet, you can send a single news post by email directly from the post itself. That covers one post; the automatic weekly digest that emails intranet news on a schedule is a separate mechanism, and we cover its setup and limits in our guide to the SharePoint news digest. Audience targeting setup likewise deserves its own walkthrough, and we keep it out of this article for that reason.

How can you tell which employees read your news?

Once placement, site, boost and web part settings are right, measurement tells you whether it worked. SharePoint's native page analytics is the first stop, and it is genuinely useful at post level. Open a news post and select Analytics at the top of the page, and you get a usage report for that specific post[5].

  • Unique viewers: the number of individual visitors to the post, however often they returned[5].
  • Total views: page views with repeat refreshes filtered out[5].
  • Average time spent reading and page traffic by time, filterable across periods from 24 hours to the lifetime of the post[5].
  • Audience view rate: the percentage of the shared audience who saw the news, calculated only for news posts created after September 2025[5].
  • Channel breakdown: usage split across the four distribution channels the post was amplified to, Outlook, SharePoint, Teams and Engage[5].

Check what your tenant actually shows before you rely on the deeper metrics. The channel breakdown, hourly trends, reactions, promotions and data export require a Microsoft Viva Suite or Viva Communications and Communities licence, and guest and anonymous users are not counted even with those licences[5].

Then note the gap that matters most to you as an IC manager. Native analytics splits views by channel, but it does not tell you whether the post reached the departments, countries or roles it was written for; SharePoint's native reporting does not segment readership by HRIS attributes without external tooling. Tryane's Digital Workplace Benchmark 2026 rates SharePoint's Analytics / Insights capability 2 out of 5 on exactly this dimension, based on demos, expert interviews and public data. Download the full Digital Workplace Benchmark 2026 to compare platforms across all sixteen criteria. For what native reporting does cover and where to find it, our guide to SharePoint native analytics is the practical companion.

Close the gap: see who reads each post, by department and country

Everything above gets your post in front of the right surfaces: the organization news site that feeds the start page, the boost that lifts it for four days, the web part settings that place it on the pages employees visit. That is distribution, and you can now control it deliberately. Proving that the post reached the audiences it was meant for is a different problem, and view counts alone cannot answer it.

This is where Analytics for SharePoint fits the situation this article describes. It tracks and measures employee engagement, views and activity on your SharePoint intranet and Viva Connections, and shows readership by department, country and role, so you can see whether the message landed in the parts of the organisation it was written for and make data-driven decisions about your next post. See what the page shows for a news post like yours.

Book a 15-minute call[6] with Hatim to see how Analytics for SharePoint shows who reads each SharePoint news post.

Frequently asked questions

Where does a SharePoint news post actually appear?

A post can surface on the SharePoint start page, in News web parts placed on team and communication sites, and in the News reader of the SharePoint app in Teams (formerly Viva Connections), which aggregates news from organizational sites, boosted news, followed sites, frequent sites and people the user works with. A post published on a site none of these surfaces pull from will appear almost nowhere, however good the content is.

What is an organization news site in SharePoint?

It is a site a SharePoint Administrator marks as official or authoritative for news. Its posts get special visual treatment and appear on the SharePoint start page. Administrators can designate up to 100 organization news sites, and if you set a communication site as your home site, it is automatically configured as an organization news site.

How long can you boost a SharePoint news post?

A boosted post displays prominently for up to 4 days, showing a lightning bolt icon in most surfaces. You can boost news posts from organization news sites only, with a maximum of 10 boosted posts per organization news site, and you need edit permissions on that site. Boosting is most effective when applied close to the time of publishing.

Can you send a SharePoint news post by email?

Yes. You can send an individual post as an email directly from the post, which reaches employees who never open the intranet. Separately, SharePoint can send automatic news digests by email; that mechanism and audience targeting setup are covered in their own dedicated articles.

Does SharePoint news analytics show which channel views came from?

Yes. Page analytics breaks usage down by distribution channel: Outlook, SharePoint, Teams and Engage. However, the channel breakdown, hourly trends, reactions and data export to Excel or PowerPoint require a Microsoft Viva Suite or Viva Communications and Communities licence.

What is audience view rate in SharePoint news analytics?

It is the percentage of users who viewed the news post compared with the total audience it was shared with, calculated from the Microsoft Entra ID users who have permissions to the post, with users in multiple groups counted only once. It is available only for news posts created after September 2025.

Can SharePoint analytics show who read a news post by department or country?

No. Native page analytics reports unique viewers, total views, reading time and channel split, but it does not segment readership by department, country or role. That segmentation is exactly the gap dedicated SharePoint analytics tooling such as Analytics for SharePoint is built to close.

Sources

• learn.microsoft.com

• learn.microsoft.com

• support.microsoft.com

• support.microsoft.com

• support.microsoft.com

• calendly.com

Further reading

• SharePoint news digest: how to email your intranet news

• Why SharePoint News Goes Unread, and What the Data Actually Shows

• SharePoint communication site vs team site: which to use

• Internal newsletter: how to create one employees read

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.