Looking forward to it. I’ve reported that issue to Microsoft almost 3y ago, it was closed as not important for immediate fixing. Persisted on the urge with several dev teams they have a kernel patch but still are reluctant to release it 😕due to uncertainty whether it could cause disruption.
February 26, 2025 at 6:28 AM
Looking forward to it. I’ve reported that issue to Microsoft almost 3y ago, it was closed as not important for immediate fixing. Persisted on the urge with several dev teams they have a kernel patch but still are reluctant to release it 😕due to uncertainty whether it could cause disruption.
I believe the stack covering westeu has longer running issues. Ingestion delays have been significantly higher there for over a year. This is also the region where they have a huge client pool so I have a gut feeling that region needs some more hardware or restructuring due to the success.
February 26, 2025 at 6:20 AM
I believe the stack covering westeu has longer running issues. Ingestion delays have been significantly higher there for over a year. This is also the region where they have a huge client pool so I have a gut feeling that region needs some more hardware or restructuring due to the success.
This also accidentally mitigates several domain fronting opportunities for adversaries that could leverage several Microsoft.com subdomains for a long time.
January 13, 2025 at 6:08 PM
This also accidentally mitigates several domain fronting opportunities for adversaries that could leverage several Microsoft.com subdomains for a long time.