This post has been republished via RSS; it originally appeared at: Microsoft Tech Community - Latest Blogs - .
Update: Thursday, 17 February 2022 04:08 UTC
Root cause has been isolated to configuration which was impacting logs ingestion. To address this issue we have redeployed service. Some customers may experience data latency for certain data types and missed alerts. and we estimate 4 hours before all backlog of data is addressed.
Root cause has been isolated to configuration which was impacting logs ingestion. To address this issue we have redeployed service. Some customers may experience data latency for certain data types and missed alerts. and we estimate 4 hours before all backlog of data is addressed.
- Work Around: <none or details>
- Next Update: Before 02/17 10:30 UTC