Outlook Newsletters: Features, Limitations & Enterprise Alternative

Internal Communication

Microsoft has released Outlook Newsletters, a native tool for internal updates, reports, and announcements. It went generally available in August 2025 and is enabled by default for most Microsoft 365 tenants.

It deserves a serious look. Internal newsletters have been assembled out of blank emails and distribution lists for years. Evaluating this costs nothing: no new vendor, no procurement, and no extra purchase for tenants already running Exchange Online and SharePoint.

Drafts live in SharePoint Embedded containers inside your own tenant, so Purview retention, sensitivity labels, and eDiscovery apply as they do to any SharePoint file. Published editions are ordinary emails.

So the question is not whether Outlook Newsletters works. It is where it stops.

How to create an Outlook newsletter

Eight steps, from Microsoft’s documentation. Six are shown below.

Step 1. Check access

An admin sets OutlookNewslettersAccessLevel to ReadWrite on your OWA mailbox policy. The module appears 15 to 30 minutes later, and only in the new Outlook for Windows or Outlook on the web. Classic Outlook does not show it.

Step 2. Create the series

Go to Newsletters, then Create newsletter. The series is the container your editions publish into. Set a title, a header image, and up to 100 owners, who all get analytics, subscribers, and data export. Subscriptions are on by default.

Visibility has three levels, not two:

• My organization. Anyone in the tenant can find and subscribe.
• Unlisted. Direct link only.
• Private. Invited users only, and no subscriptions.

Set up once. Editions publish into it over time.

Step 3. Create an edition

Select Create edition and pick a blank layout, a preset, or a custom template. Name it on save, and choose whether you are saving an edition or a template.

Watch for. Templates cannot be published and cannot take contributors. Each one belongs to a single series, so a layout built by HR is unavailable to Finance.

Custom templates appear after the presets, inside the series that created them.

Step 4. Format it

Four areas are editable: title, header image, table of contents, and sections. Sections are the unit of both layout and collaboration.

Add components from the Edition tab: Text and Image, Images, Styled Quote, or People. Sensitivity labels and an Accessibility Checker are available here.

Watch for. Images are the only embedded content. No video, no documents.

Sections are the unit of both layout and collaboration.

Step 5. Assign contributors

Give each section its own contributors. Their names and avatars appear on the section they own.

Watch for. There is no real-time editing and no version history. If two people work in one section, the second to save either overrides the other’s work or discards their own.

Step 6. Preview

Select Preview, toggle dark mode, and send yourself an email copy. Microsoft’s own tip is to check Outlook Mobile and Outlook Classic if colleagues still use them.

Dark mode is a toggle, not a separate design. Check it before every send.

Step 7. Publish

Select Next, then review the publish settings.

• Sender. Nominate an alternate sender if you hold Send As. If not, use Ask to Send and they publish it themselves. The primary author stays whoever created the edition.
• Recipients. You fill To. CC arrives pre-filled with every owner plus you. BCC arrives pre-filled with every subscriber.
• Visibility. An edition can be more restricted than its series, but never less.

Watch for. External addresses are removed on send. A distribution list counts as one recipient against your sending limits. Publishing from a Group or distribution list requires an alternate sender with Send As.

Published editions appear with views, comments, and reactions.

Step 8. Read the analytics

Open the edition and select Analytics. You get recipients sent to, total views, email views, Newsletter app views, reactions, and comments.

Watch for. No link clicks. No per-recipient data.

Every metric Outlook Newsletters reports. No row for clicks, no row for who did what.

Where Outlook Newsletters stops

The walkthrough above flags the constraints you meet while building one edition. Four more surface only at scale.

The licences are backwards. Authoring needs Entra ID, an Exchange Online mailbox, and SharePoint access. Government cloud is unsupported. And because drafts sit in SharePoint Embedded, authoring depends on SharePoint Plan 1 or 2: the Kiosk plan bundled into Frontline licences such as F1 and F3 does not qualify. The tool is least available in exactly the frontline-heavy organisations that, as the research below shows, are hardest to reach.

External recipients need a workaround that does not scale. Microsoft removes external addresses on send. The real rule, as Tony Redmond demonstrated, is that only recipients known to Exchange Online can receive an edition, so a mail contact per person does work. Do it at volume and you hit external recipient rate limits. Contractors, franchisees, board members, and partners are part of most organisations’ real internal audience.

Comms teams cannot author from their own mailbox. Most publish from a shared internal-comms@ address. Shared mailboxes do not behave like user mailboxes for apps, so Microsoft’s guidance is to author from a personal mailbox and send via Send As. Ownership then lives with an individual employee.

SharePoint storage is not SharePoint news reuse. Storing drafts in SharePoint Embedded is good governance. It does not pull the intranet news you already publish into an email people actually open.

And the measurement gap is the one that decides procurement. Independent testing confirms what the analytics tab shows: recipients, views, reactions, comments. No link clicks. No per-recipient data. Enough for a departmental update. Not enough for a compliance notice, a benefits deadline, or a safety bulletin, where the only question that matters is whether the people who needed to act actually acted.

What the research says

It would be easy to conclude the answer is a tool with more metrics. The evidence says something more uncomfortable.

Gallagher’s Employee Communications Report 2026 surveyed more than 1,300 communications and HR professionals across 40 countries. It found that 70% of internal communications teams measure only basic outputs: opens, clicks, page views. Just 16% measure outcomes such as sentiment. Only 12% connect their work to business impact.

Outlook Newsletters does not even reach the left-hand bar. Without link tracking, it measures views rather than clicks.

But the more important finding is the trap. Among low-maturity teams, the metric leadership most often requests is activity and reach. So teams optimise for clicks, which reinforces clicks as the definition of success. Gallagher’s own advice is blunt: stop counting clicks; start counting who you are not reaching.

That reframes the category. Targeting is usually sold as a way to make messages more relevant. The research says it is primarily a way to make them fewer. Organisations communicating at high volume see a 30% jump in rating leadership trust as a significant risk.

One further finding matters for anyone with a distributed workforce. Organisations with a primarily frontline workforce are 1.3x as likely to perceive high risk to their communication goals, and frontline teams are, in Gallagher’s phrase, “strategically underserved”. Set that beside the Frontline licensing constraint above.

Where JungleMail extends Microsoft 365

The goal is not to replace Outlook. It is to build employee newsletters properly and deliver them to Outlook inboxes, with the targeting, control, and measurement comms teams need.

Build without a designer, and keep the brand

The drag-and-drop builder assembles editions from sections, blocks, and reusable elements. Saved sections carry across editions, so nobody rebuilds the leadership note each month.

Global admins hold the brand. Branding settings apply logos, fonts, and colours across every site, and Template Lock restricts authors to approved templates with only the permitted parts editable. The “start from scratch” button can be disabled entirely.

AI Writer and AI Artist draft subject lines, refine copy, check grammar and tone, and generate on-brand images. Administrators choose which assistants are enabled, or switch them off.

Attachments are supported, and video clips embed from YouTube or any URL as a thumbnail that links out. Outlook Newsletters accepts images only.

Pull SharePoint news into the inbox

JungleMail’s SharePoint News Embed pulls news posts, pages, and list items straight into the newsletter canvas. Set a filter, such as news from the last seven days, and the block populates itself. If there is no new news, the send is skipped.

Dynamic sections go further, assembling content per recipient from SharePoint lists using placeholders and conditions. Sent editions archive back to SharePoint for an auditable history.

Personalise in order to send less

Dynamic segments build from Entra ID, SharePoint lists, or uploaded files. Section-level visibility means each person sees only what is meant for them, inside one newsletter. Employees can self-select topics, frequency, and language through a SharePoint subscription form.

A shared Communication Calendar keeps teams from stacking sends on the same morning. Given the research above, this is not decoration. It is how a team stops broadcasting everything to everyone.

Speak every employee’s language

Build a primary newsletter, add language versions, and translate manually or with DeepL, Gemini, or OpenAI. The DeepL integration covers 39 languages.

Each version routes to its audience by delivery condition: country, office, job code, or any custom Entra ID attribute. The app interface itself is multilingual, so authors and approvers work in their own language.

Outlook Newsletters offers no translation and no language routing. The alternative is a separate newsletter per language, maintained by hand.

Measure what leadership can act on

Opens, clicks, read time, top links, click maps, clickstream, device and location breakdowns, and embedded survey results, in real time. Results slice by role, department, office, or custom segment, with longitudinal trends, and export to CSV, Word, or Power BI.

The click map answers what Outlook Newsletters cannot: not how many opened it, but what they did.

Directory-profile analytics break engagement down by role, department, and location. That is the “who are we not reaching” view Gallagher argues low-maturity teams should be building.

Tracking respects privacy. Tenants can switch on pseudonymisation, set retention windows, collect survey responses anonymously, and apply unsubscribe controls. Individual drill-down is available only when an administrator enables it.

Collaborate in real time, and approve before sending

Co-Authoring brings live collaboration to templates and newsletters, with inline chat in the editor. No conflict dialogs. Nobody’s work gets discarded.

Approval workflows route an edition through communications, legal, or leadership in Power Automate before anything leaves the tenant. Outlook Newsletters has no approval step.

Reach beyond one tenant, and send from your own

External subscribers live in a central hub, with web forms, welcome emails, and preference tracking, and no mail-contact-per-person workaround.

JungleMail sends through the Microsoft Graph API using your tenant, so sender reputation, throttling, and organisational policies apply by default. Shared mailboxes and Send As are supported. Time Zone Sending delivers during each region’s working hours rather than one fixed time for everyone. Azure hosting is available across the UK, EU, US, Canada, Australia, and the UAE for data residency.

One honest caveat. Graph API integration is not a trick to erase Exchange Online sending limits, and any vendor implying otherwise is overselling. The value is the governance, targeting, and operational control around the send.

Side by side

● Supported  ·  ◐ Partial, with a workaround  ·  ○ Not supported

Scroll the table sideways to see the JungleMail column.

Read it this way: the last three rows are why Outlook Newsletters is worth using at all. The first four are why teams outgrow it.

Frequently asked questions