Microsoft said it lost weeks of security logs for its customers' cloud products
Microsoft’s admission that it lost weeks of security logs for key cloud products like Entra (Azure Active Directory), Sentinel, Defender for Cloud, and Purview has triggered concerns about the reliability and maturity of its cloud and security infrastructure. Commenters question how such a failure is even technically possible, criticize Azure’s usability and cohesion, and tie the incident to broader worries about declining software quality and Microsoft’s recurring security lapses. Others note that despite these issues, enterprise buyers often prioritize executive relationships, ecosystem lock-in, and sales support over technical excellence, which helps explain Azure’s strong market position.
Impact of Lost Logs
- Commenters see loss of Entra (Azure AD), Sentinel, Defender for Cloud, and Purview logs as extremely serious for incident response and compliance.
- SSO / identity logs are highlighted as critical for tracing breaches, especially in regulated environments.
- Some note that even organizations with limited Entra integration are still “hosed” for investigations involving internal/back‑office systems.
Why and How Could This Happen?
- One insider‑sounding comment describes a “sev 0” bug in a widely used log‑pushing agent that required manual restarts across many teams.
- Others are baffled that any serious infra lacks strong protections against widespread log loss; they describe this as something even weak organizations usually guard against.
- Speculation ranges from plain incompetence, to “foreign actor” narratives, to tongue‑in‑cheek “cover‑up” jokes.
Microsoft Security Posture
- Many comments portray Microsoft as chronically insecure, with a long history of major lapses and perceived cultural neglect of security.
- A minority argue Microsoft has significantly improved since the early 2000s and that its security tools (EDR, lateral‑movement detection, ransomware detection) are effective, especially in large enterprises.
- Others counter that recent US government criticism and recurring breaches undermine claims of improvement.
Azure Usability, Reliability, and Login
- Strong recurring complaints: confusing, fragile Azure UI; login loops; inconsistent redirects; lack of 2FA prompts after sign‑out; and general “duct‑taped” feel.
- Azure portal is mocked as an enormous, slow SPA; users report needing page refreshes after actions.
- Batch and scheduling services are called inaccurate; some say Azure is fundamentally unsuitable for serious production workloads.
Enterprise vs. Smaller Users
- Several argue Azure wins not on technical merit but on: executive‑level assurances, sales/support relationships, and being a non‑Amazon option for enterprises.
- Engineers often dislike Azure, but decision‑makers prioritize vendor backing, contracts, and competitive dynamics.
Comparisons and Alternatives
- Debates on Windows vs. Linux security: some say Microsoft’s security tooling for mixed environments outclasses open‑source; others insist Linux and BSD can be more secure with better practices.
- AWS and GCP are compared: Azure seen as worse technically but more enterprise‑friendly than Google Cloud’s perceived instability, deprecations, and weaker account management.
Cultural / Miscellaneous Themes
- Frequent frustration with Microsoft’s constant rebranding (e.g., Azure AD → Entra).
- Nostalgic side‑threads about older Microsoft products and earlier Windows versions being more focused and less encumbered than today’s ecosystem.