$5,040: Microsoft Publisher shut off after Project Online died
A 10-person team pays $5,040 for Microsoft 365 Business Standard over 36 months. Publisher left the bundle anyway, with no price cut.
Tim Neunzig
$5,040 is what a 10-person team pays over 36 months for Microsoft 365 Business Standard at $14 per user per month. Publisher was inside that bundle. On October 1, 2026, Microsoft 365 subscribers lost Publisher.
You did not lose email. You did not lose Word. You did lose the app that opened the working files for your flyers, menus, newsletters and postcards.
One day earlier, Project Online retired. Project Web App sites and data became unavailable, with no read-only mode and no archive according to Microsoft and migration partners. Different product. Same rented floor.
What happened
Microsoft Publisher was a desktop publishing app for brochures, flyers, newsletters, postcards, business cards, calendars and other print material. Small businesses, clubs, agencies and Microsoft 365 subscribers used it for recurring documents. Not abstract content operations. Flyers. Menus. Local newsletters. Business cards. The work that gets reopened every season because last year’s version is the fastest starting point.
Microsoft said Publisher would no longer be supported after October 2026. University notices repeated the retirement path. University of Washington used the title Microsoft Publisher retires October 2026. University of Michigan used the title Microsoft 365 Publisher No Longer Supported After October 2026.
The practical shutoff date was October 1, 2026 for Microsoft 365 subscribers. After that, subscribers could no longer rely on Publisher to open or edit .pub files in the Publisher app. Microsoft pointed users toward converting .pub files to PDF or Word, and toward moving common scenarios to Word or PowerPoint.
That advice preserves something. It does not preserve everything. A .pub file is not only an output file. It is the editable working file. It carries the page layout, placed images, text boxes, crop choices, paper size, typography, and the small ugly fixes that made the print job work. A PDF is useful. It is stable. It is good for viewing, printing and archiving. It is not the same as keeping the original workflow alive.
Windows Latest framed the countdown in its headline: Microsoft said it was committed to improving Microsoft 365 by shutting Publisher down, and you had 2 months to save your files. That is the rented software bargain in plain language. You pay every month. Then the app becomes a deadline.
The bundle got more expensive before the removal. Microsoft 365 Business Standard moved from $12.50 to $14 per user per month on July 1, 2026. That is a 12 percent increase. For 10 users over 36 months, the old price was $4,500. The new price is $5,040. That is $540 more over the same term. Publisher then disappeared from the subscriber workflow. The Business Standard price did not drop.
Do not twist the math. The Business Standard seat also pays for Outlook, Teams, Word and Excel. Replacing Publisher does not cancel the seat if your team still needs those apps. The point is narrower and uglier. The bundle charged more, then one app in the bundle went away, and your old publication files became your cleanup job.
One day before Publisher went dark, Project Online retired on September 30, 2026. Microsoft’s Planner blog carried the retirement notice under the title Microsoft Project Online is retiring: what you need to know. The retirement left Project Web App sites and data unavailable, with no read-only mode and no archive according to Microsoft and migration partners. That matters here because it shows the same pattern. Subscription access is not custody. If the vendor removes the door, your work is still trapped behind it.
For Publisher users, the operational result was simple. Inventory your .pub files. Export what you can to PDF. Convert to Word or PowerPoint only where the damage is acceptable. Rebuild recurring templates in tools you control. Stop pretending a bundled app is a records system.
What it actually did for you
Publisher did a narrow job. That was the useful part.
You used desktop page layout. You placed text and images on a designed page. Flyers, brochures, newsletters, menus, postcards and business cards do not need a giant platform. They need boxes, images, alignment, paper sizes and print output.
You used templates and reusable design elements. The local menu had the same shape every month. The club newsletter reused a masthead. The agency postcard reused logos and disclaimers. Starting from a blank page every time is how small teams burn afternoons.
You used text and image formatting. You moved copy around. You dropped in photos. You changed type. You fixed a logo. You made the thing fit without turning it into a corporate design system.
You used print-ready output and PDF export. That was the actual deliverable. A file you could send to a printer, attach to an email, archive for later, or use as proof that last year’s version existed.
Then .pub file triage became a real feature, not because Microsoft sold it that way, but because the app had an end date. Old source files turned into inventory work. You had to know which files mattered, which could be flattened to PDF, and which recurring designs had to be rebuilt somewhere else.
There is no serious list of exotic Publisher features padding the bill here. The padding was the bundle. Publisher was not the standalone line item for these subscribers. The Microsoft 365 Business Standard seat paid for Outlook, Teams, Word, Excel and the rest of the bundle. Publisher was one piece inside it. When that piece went away, the seat still cost $14 per user per month.
That is the trap with bundled software. The tool you depend on is treated like furniture in a rented office. Useful while it is there. Removed when the landlord changes the floor plan.
The math
| Tier | Price per user per month | Team size | 36 months | Total |
|---|---|---|---|---|
| Microsoft 365 Business Standard before July 1, 2026 | $12.50 | 10 users | $12.50 × 10 × 36 | $4,500 |
| Microsoft 365 Business Standard after July 1, 2026 | $14 | 10 users | $14 × 10 × 36 | $5,040 |
| Owned Publisher-style workflow, starter build | Not per user | 10-user workflow | One build, 1 to 2 weeks | $750 to $2,500 |
You keep custody of your templates, publication files, PDFs and archive on your own server. There is no honest payback month here, because replacing Publisher does not cancel Outlook, Teams, Word or Excel. The $750 to $2,500 build is the cost of not depending on a bundled app for your publishing workflow again.
What you would build instead
You do not rebuild Microsoft 365. That would be stupid. You replace the part that died.
Build a template library. Store approved flyer, newsletter, menu, postcard and business-card templates in one place. Keep names, owners, dates and publication types. Put source files and exported PDFs next to the metadata.
Build a publication archive. Finished PDFs, source files and migrated assets live on the client server. Search by title, date, owner and document type. The team stops hunting through old desktops and shared folders named final, final2 and really-final.
Add a .pub rescue workflow. Inventory existing .pub files. Export important documents to PDF where possible. Import editable candidates with LibreOffice Draw where possible. Rebuild recurring designs in Scribus.
Make PDF the stable handoff. PDF becomes the viewing, print and archive format. Source files stay editable in the owned workflow. The handoff file is boring. Boring survives.
Use a small owned stack. Scribus handles desktop publishing and new page-layout work. LibreOffice Draw handles .pub import and rescue work where it can. A plain self-hosted web UI stores the template and publication archive. Postgres stores metadata. File storage stays on the client server. Desktop tools run on user machines.
Use open-source building blocks with plain licenses. Scribus is GPL-2.0-or-later. LibreOffice Draw is MPL-2.0. The custom archive UI is MIT licensed. It stores templates, exported PDFs, metadata and publication history. No per-seat archive. No vendor account needed to open your own filing cabinet.
Migrate only the workflow. Inventory .pub files. Export important files to PDF. Import candidates with LibreOffice Draw where possible. Rebuild recurring templates in Scribus. Do not pretend this replaces Outlook, Word, Excel, Teams or the whole Microsoft 365 suite. It does not.
You lose the original Microsoft Publisher application inside Microsoft 365. You lose exact Publisher behavior and full-fidelity editing for every .pub file. You lose Microsoft’s built-in Publisher templates and design elements. You lose the tight Word and PowerPoint handoff Microsoft recommends. You also lose the habit of letting a subscription bundle decide whether your publishing workflow opens tomorrow. That part is useful.
Who should do this
Do this if you are a small business with recurring print material. Menus, flyers, postcards, seasonal notices, local ads and customer PDFs. You do not need an enterprise publishing suite. You need your templates to open next quarter.
Do this if you are a club, nonprofit, school office or local agency with years of .pub files. Your risk is not fancy design. Your risk is that the editable file for the annual fundraiser, sponsor flyer or membership newsletter becomes a museum artifact.
Do this if you already pay for Microsoft 365 but used Publisher only for narrow print jobs. Keep Microsoft 365 if you need Outlook, Teams, Word and Excel. Kill the dependency on Publisher for publishing work.
Keep renting if your team lives inside Word and PowerPoint and you are happy rebuilding everything there. Keep renting if you have no .pub archive, no recurring templates and no need for owned publication storage. Keep renting if every file is disposable after export. Some work is not worth rescuing.
The SaaSKiller Take If you used Publisher for flyers, newsletters and menus, you paid for a bundle that rose from $12.50 to $14 per user per month, then lost Publisher anyway. For a 10-person team, Business Standard costs $5,040 over 36 months. Build the publishing workflow you actually use: rescue the .pub files, keep PDFs, rebuild templates in owned tools, and stop depending on whether Microsoft keeps an app in the bundle.
Sources
- https://support.microsoft.com/nl-nl/publisher/microsoft-publisher-will-no-longer-be-supported-after-october-2026
- https://www.windowslatest.com/2026/08/10/microsoft-says-its-committed-to-improving-microsoft-365-by-shutting-publisher-down-and-you-have-2-months-to-save-your-files/
- https://learn.microsoft.com/en-us/answers/questions/5910437/when-publisher-expires-what-do-i-use
- https://www.odu.edu/announcements/2026/2026-09/2026-09-21/microsoft-publisher-retirement
- https://www.microsoft.com/en-us/copilot/blog/2025/12/04/advancing-microsoft-365-new-capabilities-and-pricing-update/
- https://ifeeltech.com/blog/microsoft-365-business-plan-comparison-copilot-2026
- https://www.tso.de/en/news/news/microsoft-announces-price-updates-for-microsoft-365-licensing-effective-july-2026/
- https://teamdynamix.umich.edu/TDClient/30/Portal/KB/Article/14451/Microsoft-365-Publisher-No-Longer-Supported-After-October-2026
- https://it.uw.edu/microsoft-publisher-retires-october-2026/
- https://www.computerworld.com/article/4224008/microsoft-is-pulling-the-plug-on-publisher-what-now.html
- https://learn.microsoft.com/en-us/answers/questions/5276971/announcement-microsoft-publisher-to-be-discontinue
- https://techcommunity.microsoft.com/blog/plannerblog/microsoft-project-online-is-retiring-what-you-need-to-know/4450558
- https://easi.its.utoronto.ca/project-online-retiring-september-30-2026/
- https://systemforce.co.uk/blog/2026/09/24/microsoft-project-online-retirement-september-2026-migration/
- https://agolution.com/en/microsoft/licenses/price-increase-microsoft-365-july-2026/
- https://www.swktech.com/microsoft-365-price-increases-will-take-effect-july-2026/
- https://techcommunity.microsoft.com/blog/microsoft-copilot-blog/act-now-lock-in-current-pricing-on-microsoft-365-copilot-business-bundles/4502628
- https://learn.microsoft.com/en-us/answers/questions/5812595/publisher-wont-be-supported-by-microsoft-after-the
- https://www.mun.ca/cio/news-articles/microsoft-publisher-end-of-life-in-october-2026-preparing-your-files-and-choosing-alternatives.php
- https://learn.microsoft.com/en-us/answers/questions/5960182/using-publisher-after-october-1-2026
AI-generated