We've confirmed that all systems are back to normal with no customer impact as of 11/13, 14:10 UTC. Our logs show the incident started on 11/13, 10:30 UTC and that during the 3 hours and 10 minutes that it took to resolve the issue, some customers may have experienced intermittent data latency in Log Analytics in central Australia region.
Root Cause: The failure was due to a bad configuration in a recent build.
Incident Timeline: 3 Hours & 10 minutes - 11/13, 10:30 UTC through 11/13, 14:10 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.