you are viewing a single comment's thread
view the rest of the comments
[–] 28 points 15 hours ago (3 children)

Where did they say it was a client side bug?

  • source
  • parent
  • hideshow 3 child comments
  • [–] 1 point 3 hours ago

    I guess I misunderstood it.

    Inside an internal Windows process, competing tasks were waiting for access to shared resources, a problem called lock contention. Under certain traffic conditions, this exhausted processor and memory capacity.

    I read this as the behavior that precipitated the issue on the gateway was caused by how Windows sent traffic to exchange servers. So by Windows they mean whatever is running on the gateway?

  • source
  • parent
  • [–] 41 points 15 hours ago (1 child)

    It says multiple times that the issue was with Microsoft's internal cloud server software, not Windows.

    The defect came from a fix prepared specifically for Microsoft 365 networking gateway servers.

    The failure was within Microsoft’s cloud infrastructure, not customer Windows systems

  • source
  • parent
  • hideshow 1 child comment