Stories with Tag Microsoft 365

• The Microsoft 365 Copilot launch was a disaster

  permalink

  Posted: 2025-01-26 16:33:51

  Verbose tl;dr

  ZDNet argues that the Microsoft 365 Copilot launch was a "disaster" due to its extremely limited availability. While showcasing impressive potential, the exorbitant pricing ($30 per user/month on top of existing Microsoft 365 subscriptions) and restriction to just 600 enterprise customers renders it inaccessible to the vast majority of users. This limited rollout prevents widespread testing and feedback crucial for refining a product still in its early stages, ultimately hindering its development and broader adoption. The author concludes that Microsoft missed an opportunity to gather valuable user data and generate broader excitement by opting for an exclusive, high-priced preview instead of a wider, even if less feature-complete, beta release.

  The launch of Microsoft 365 Copilot, Microsoft's ambitious AI-powered assistant integrated into its productivity suite, has been characterized by the author of the ZDNet article as a resounding failure, marred by a series of missteps and technical difficulties that significantly hampered its initial rollout. The article paints a picture of a launch riddled with problems, beginning with the confusing and restrictive access limitations. Instead of a broad release, access was initially granted to a minuscule group of only 600 enterprise customers, a stark contrast to the widespread availability that many anticipated. This highly limited access created a sense of exclusivity that fueled frustration and disappointment amongst the broader user base eager to experience the touted capabilities of the AI assistant.

  Furthermore, the article elaborates on the technical hurdles that plagued the early stages of the launch. Even for those fortunate enough to gain access, the functionality of Copilot was reportedly severely constrained by performance issues. Users encountered slow response times, rendering the tool impractical for real-time collaboration and impeding the seamless workflow integration that Copilot was designed to facilitate. These performance bottlenecks detracted significantly from the user experience, further solidifying the perception of a botched launch.

  The article also criticizes Microsoft's communication surrounding the rollout, describing it as inadequate and lacking transparency. The absence of a clear timeline for broader availability and the limited information provided regarding the ongoing technical challenges exacerbated the negative sentiment surrounding the launch. This lack of clear communication left potential users in the dark, fostering uncertainty and fueling speculation about the underlying reasons for the protracted and problematic rollout.

  In essence, the author argues that the combination of restrictive access, persistent performance issues, and insufficient communication coalesced to create a launch experience that fell far short of expectations. The article portrays a picture of a highly anticipated product launch significantly hampered by technical difficulties and strategic missteps, ultimately resulting in a perception of failure and missed opportunity for Microsoft. The author concludes that while the potential of Copilot remains undeniable, its initial introduction to the market was deeply flawed and requires significant improvement before it can live up to its promised potential.

  • Microsoft 365
  • Microsoft Copilot
  • Copilot Launch
  • Software Launch
  • Product Launch
  • Productivity Software
  • AI Tools
  • artificial intelligence
  • Software Issues
  • Tech News
  • Microsoft
  • ZDNet

  Summary of Comments ( 479 )
  https://news.ycombinator.com/item?id=42831281

  Verbose tl;dr

  HN commenters generally agree that the launch was poorly executed, citing the limited availability (only to 600 enterprise customers), high price ($30/user/month), and lack of clear value proposition beyond existing AI tools. Several suggest Microsoft rushed the launch to capitalize on the AI hype, prioritizing marketing over a polished product. Some argue the "disaster" label is overblown, pointing out that this is a controlled rollout to large customers who can provide valuable feedback. Others discuss the potential for Copilot to eventually improve productivity, but remain skeptical given the current limitations and integration challenges. A few commenters criticize the article's reliance on anecdotal evidence and suggest a more nuanced perspective is needed.

  The Hacker News thread discussing the ZDNet article "The Microsoft 365 Copilot launch was a total disaster" contains a number of comments expressing skepticism about the article's premise and the author's understanding of enterprise software rollouts.

  Several commenters argue that the slow, controlled rollout of Copilot is standard practice for enterprise software, particularly one with such deep integration into core business workflows. They point out the risks associated with a wide, immediate release, including potential instability, unforeseen bugs, and the need for extensive user training and support. They suggest that a phased rollout allows Microsoft to gather feedback, address issues, and refine the product before making it available to a broader audience. Some even argue that calling this standard practice a "disaster" is a mischaracterization and displays a lack of understanding of the enterprise software landscape.

  Some users highlight the potential legal and security complexities involved in deploying AI tools in a business context. They suggest the cautious rollout could be related to ensuring compliance with data privacy regulations, preventing data leaks, and managing the potential for misuse of the AI capabilities.

  A few commenters express a degree of agreement with the article, noting that Microsoft's marketing hype around Copilot set expectations for a more readily available product. They suggest that the perceived "disaster" stems from the disconnect between the marketing promises and the reality of a staged rollout. However, even these commenters acknowledge the practicality of a controlled release for complex enterprise software.

  One commenter draws a parallel to the rollout of Tesla's Full Self-Driving, arguing that both situations involve highly anticipated technologies with complex implementations that necessitate a cautious, iterative release strategy.

  Overall, the sentiment in the comments leans heavily towards disagreeing with the ZDNet article's characterization of the Copilot launch as a "disaster." The majority of commenters view the controlled rollout as a sensible approach for enterprise software and criticize the author's apparent lack of familiarity with standard industry practices.

• Microsoft won't support Office apps on Windows 10 after October 14th

  permalink

  Posted: 2025-01-15 16:16:58

  Verbose tl;dr

  After October 14, 2025, Microsoft 365 apps like Word, Excel, and PowerPoint will no longer receive security updates or technical support on Windows 10. While the apps will still technically function, using them on an unsupported OS poses security risks. Microsoft encourages users to upgrade to Windows 11 to continue receiving support and maintain the security and functionality of their Microsoft 365 applications.

  Microsoft has announced that it will cease providing support for Microsoft 365 applications on the Windows 10 operating system after October 14, 2025. This means that after this date, users who continue to utilize Windows 10 will no longer receive security updates, bug fixes, or technical support for their Microsoft 365 apps, which include popular productivity software like Word, Excel, PowerPoint, Outlook, and Teams. This effectively ends the functional lifespan of Microsoft 365 on Windows 10, although the applications may continue to operate for a period afterward, albeit with increasing security risks and potential compatibility issues.

  This decision aligns with Microsoft's broader strategy of encouraging users to migrate to Windows 11, the company's latest operating system. While Microsoft will continue to support Windows 10 with security updates until October 14, 2025, the lack of support for crucial productivity applications like Microsoft 365 effectively makes Windows 10 a less desirable platform for businesses and individuals who rely on these applications for their daily workflow. This move underscores the importance of staying up-to-date with software updates and operating system upgrades to ensure ongoing compatibility and security. Users who wish to continue using Microsoft 365 with full support after the October 2025 deadline will need to upgrade their systems to Windows 11. Failing to do so could expose users to potential security vulnerabilities and limit their access to the latest features and functionalities offered by Microsoft 365. This effectively deprecates Windows 10 as a viable platform for continued use of the Microsoft 365 suite, pushing users towards the newer Windows 11 ecosystem.

  • Microsoft
  • Office
  • Windows 10
  • Microsoft 365
  • Support
  • End of Support
  • Software
  • Operating System
  • Apps
  • productivity
  • Technology
  • October 14th
  • 2025
  • Office 365
  • Applications
  • October 14
  • Windows

  Summary of Comments ( 55 )
  https://news.ycombinator.com/item?id=42712807

  Verbose tl;dr

  HN commenters largely discuss the implications of Microsoft ending support for Office apps on Windows 10. Several express frustration with Microsoft's push to upgrade to Windows 11, viewing it as a forced upgrade and an attempt to increase Microsoft 365 subscriptions. Some highlight the inconvenience this poses for users with older hardware incompatible with Windows 11. Others note the potential security risks of using unsupported software and the eventual necessity of upgrading. A few commenters point out the continuing support for Office 2019, although with limited functionality updates, and discuss the alternative of using web-based Office apps or open-source office suites like LibreOffice. Some speculate this is a move to bolster Microsoft 365 subscriptions, making offline productivity increasingly dependent on the service.

  The Hacker News post titled "Microsoft won't support Office apps on Windows 10 after October 14th" has generated a number of comments discussing the implications of Microsoft's decision. Several commenters express frustration and cynicism regarding Microsoft's perceived strategy of pushing users towards newer operating systems and subscription services.

  One highly upvoted comment points out the confusion this creates for users, especially given that Windows 10 is still supported until 2025. They highlight the discrepancy between supporting the OS but not the core productivity suite on that OS, questioning the logic behind this move. The commenter suggests this is a tactic to force upgrades to Windows 11, even if users are content with their current setup.

  Another commenter echoes this sentiment, expressing annoyance at the constant pressure to upgrade, particularly when they are satisfied with the performance and stability of their existing software. They feel this is a blatant attempt by Microsoft to increase revenue through forced upgrades and subscriptions.

  The theme of planned obsolescence is also raised, with one user arguing that this is a classic example of a company artificially limiting the lifespan of perfectly functional software to drive sales. They express disappointment in this practice and the lack of consideration for users who prefer stability over constant updates.

  Some commenters discuss the technical implications, questioning the specific reasons why Office apps wouldn't function on a supported OS. They speculate about potential security concerns or underlying changes in the software architecture that necessitate the change. However, there's a general skepticism towards these explanations, with many believing it's primarily a business decision rather than a technical necessity.

  A few users offer practical advice, suggesting alternatives like LibreOffice or using older, perpetual license versions of Microsoft Office. They also discuss the possibility of using virtual machines to run Windows 11 if necessary.

  Several comments mention the security implications, with some suggesting that this move might actually improve security by forcing users onto a more modern and regularly updated platform. However, this is countered by others who argue that forced upgrades can disrupt workflows and create vulnerabilities if not handled properly.

  Overall, the comments reflect a general sentiment of frustration and skepticism towards Microsoft's decision. Many users perceive it as a manipulative tactic to drive revenue and force upgrades, rather than a move based on genuine technical necessity or user benefit. The discussion highlights the ongoing tension between software companies' desire for continuous updates and users' preference for stability and control over their systems.