Submitted the consumerrights.wiki page documenting the scheduled remote degradation of perpetually-licensed Office 2019/2021 for Mac. Frames the move as Microsoft unilaterally converting paid-for, indefinitely-usable software into view-only mode, which violates the basic premise of a perpetual license.
Argues the legal debate is a distraction because Microsoft's lawyers will prevail regardless. The right response is moral outrage and public pressure — customers should simply be told 'this is wrong' rather than getting lost in statutory interpretation.
Points out that the deprecation timeline aligns with a quieter Microsoft policy shift treating each AI-agent instance invoking Office as a separately licensable seat. The perpetual license is a legal escape hatch that lets agent startups spawn headless Office processes without paying per invocation — killing it forces OpenAI, Anthropic, and others into a metered B2B contract.
Argues the consumer-facing outrage is collateral damage in a B2B repricing exercise. Microsoft has no meaningful revenue to gain from individual Office 2021 holdouts, but it has enormous upside in establishing a contractual hook to charge per-invocation when foundation-model agents fire up Word, Excel, or PowerPoint in headless mode.
Cite specific statutory protections: Section 54 of the Australian Consumer Law (undisturbed possession of purchased goods), the EU Digital Content Directive, and the US Magnuson-Moss Warranty Act. Argue that a remote kill-switch on a perpetual license is precisely the kind of post-sale degradation these laws were written to prevent.
Microsoft has scheduled a remote degradation of Office 2019 and Office 2021 for Mac — perpetual-license products customers paid for outright — converting them to view-only mode in 2026. The mechanism is a forced update check: binaries that previously ran indefinitely will refuse to save, edit, or create documents unless tied to an active Microsoft 365 subscription. The change is documented on consumerrights.wiki and confirmed by Microsoft's own support pages.
The 909-point Hacker News thread reads like a consumer-rights pile-on. Australian users cite Section 54 of the ACL, which guarantees "undisturbed possession" of purchased goods. EU users invoke the Digital Content Directive. American users invoke the Magnuson-Moss Warranty Act. The top comment, from jmward01, captures the mood: "Forget the 'is it legal or not' arguments, their lawyers will win. Just get mad and tell them this is wrong."
But buried 200 comments deep, a different theory surfaces — one that explains the otherwise inexplicable urgency of the timeline. User nikcub points out that the deprecation schedule lines up with a quieter Microsoft policy shift: the company has begun treating each AI-agent instance that invokes Office as a separate licensable seat. If that's the actual driver, the consumer-facing story is collateral damage in a B2B repricing exercise aimed squarely at OpenAI, Anthropic, and the dozens of agent startups that have quietly been spawning headless Office processes to process documents.
Follow the incentives. Microsoft does not need the residual revenue from a perpetual Office 2021 license-holder who never upgrades — that customer is already economically irrelevant and has been since 2022. What Microsoft *does* need is a contractual hook to charge per-invocation when a foundation-model agent fires up Word in headless mode to parse a .docx, regenerate a .pptx, or fill a .xlsx template. The perpetual license is the legal escape hatch agent builders have been using to avoid Microsoft 365's anti-automation clauses, which explicitly prohibit "automated or scripted access" by non-human users.
This matters because document processing is the workhorse task of every enterprise agent shipping in 2026. Box, Dropbox, every legal-tech startup, every contracts AI, every Series A pitch deck involves "agents that read your Office files." Until now, the cheapest production path was: spin up a sandboxed VM, install perpetual Office, run COM automation or AppleScript bridges, charge customers. Microsoft just made that architecture illegal by remote update — without filing a lawsuit, without changing a EULA you signed, without giving you opt-out.
Compare this to Adobe's 2013 Creative Cloud transition, which was at least announced as a forward-looking model change for new purchases. Microsoft is doing something more aggressive: retroactively converting already-sold goods. The legal exposure in Australia and the EU is real — DomenicoMazza's ACCC citation is not theoretical, and the ACCC has historically been the most aggressive regulator on exactly this fact pattern. But Microsoft's lawyers have presumably modeled the worst case (a class-action settlement, a regional injunction) against the upside (per-agent-instance licensing across the entire LLM industry) and concluded it pencils.
The community reaction conflates two distinct issues: the consumer-rights violation (real, but slow-moving in court) and the agent-licensing land grab (immediate, and the actual reason for the timeline). Conflating them is how Microsoft wins. A class-action over $149 perpetual licenses will settle for coupons in 2029. By then, every agent shipping enterprise document workflows will already be paying Microsoft 365 Copilot SKUs per-instance.
If you ship anything that programmatically touches Office formats, the next 60 days are a license-architecture sprint. Three concrete actions:
Audit your document pipeline today. If you have a worker spawning Office processes — even one — you have a 2026 deadline. The replacements: LibreOffice headless mode (UNO API, AGPL-friendly), OnlyOffice Docs (AGPL, runs in Docker, has REST API), or pure-library extraction via python-docx, openpyxl, and Apache POI. For PDF and PPTX rendering fidelity, Aspose and Syncfusion are the established commercial alternatives — both have per-server (not per-invocation) licensing.
Read your customers' Microsoft 365 tenant agreements. If your agent operates inside a customer's tenant using their credentials, you're shifting the licensing problem to them — but you're also creating an expensive surprise when their CFO sees the per-agent Copilot bill. The honest disclosure is that your product now triggers Microsoft 365 entitlement requirements your customer didn't anticipate.
Stop assuming "perpetual" means perpetual. Every piece of software you depend on can now be remotely degraded; treat your dependency graph the way you'd treat a SaaS vendor with no SLA. This includes the Mac App Store version of every productivity tool you bought, JetBrains perpetual fallback licenses (still safe — JetBrains has explicitly committed to non-degradation), and any "buy once" plugin from a vendor with a subscription product. The defensible posture is air-gapped builds of LibreOffice, OnlyOffice, or genuinely open-source equivalents, mirrored to your own artifact store.
The LibreOffice recommendation is not nostalgia. LibreOffice's headless UNO interface processes .docx and .xlsx with sufficient fidelity for 95% of agent workloads, and the AGPL means your competitors can't quietly fork it into a closed product the way they did with MongoDB and Elastic. The remaining 5% — pixel-perfect PowerPoint rendering, complex Excel macro chains — is the long tail where Aspose's per-server pricing has been the answer for a decade.
The ACCC will probably act. The EU will probably act. Class actions will probably settle. None of that will arrive in time to change your 2026 roadmap. The story to watch is not the consumer-rights litigation; it's the first Microsoft enforcement letter to an AI lab citing automated-access violations and demanding back-licenses. That letter is already drafted somewhere on the Microsoft legal team's drive. The only question is which agent startup gets named first, and whether that startup has the runway to fight or the cap-table pressure to settle. Either outcome sets the price for the rest of the industry — and the price is per-instance.
Been using LibreOffice for years. Everyone should. If we don't vote with our choices companies like Microsoft will keep pushing the envelope until you have to pay a monthly fee to turn on your own computer.https://www.libreoffice.org/
I believe the urgent deprecation timeline here may be related to ai labs using offline licensed Office in agents as part of workflows and Office integration. Microsoft wants _each_ agent instance to be a separate license[0]There was always a probability that Microsoft were going to funnel offline us
This shouldn't be legal. The software was clearly marketed as a classic fixed-in-time release, like the old CD releases, that would not be updated but would work indefinitely. Now they're going to boldly revoke the licenses???
When the pirated version is truer to the original contract than the official version. What a time to be alive.
Top 10 dev stories every morning at 8am UTC. AI-curated. Retro terminal HTML email.
This change would go against multiple consumer guarantees in Australia where it's 1) a right to have undisturbed possession of a product 2) products must be fit for the advertised purpose https://www.accc.gov.au/consumers/buying-products-and-servic... Microsoft would be brea