An Azure service that provides a cloud content delivery network with threat protection.
Hi Ben Koth,
Thanks for reaching out in Microsoft Q&A forum,
After a few hours I noticed that the front door tables are not showing up in the workspace. So then I created a storage account and added another diagnostic setting to send it to the storage account and I did see logs show up there. Why is it not working to send to the workspace?
The logs are appearing in your storage account that confirms Front Door is generating them properly. The delay or absence in Log Analytics is a common point of confusion, and it usually comes down to how the two destinations process data differently.
Quick breakdown:
- Storage Account: Receives raw JSON blobs immediately no schema or indexing needed, so logs show up fast.
- Log Analytics Workspace: Ingests into the shared
AzureDiagnosticstable (not dedicated tables like FrontDoorAccessLog). You filter by Category (e.g., "FrontdoorAccessLog"). Tables aren't pre-created; they populate after the first events are processed, which can take 15-30 minutes normally, or up to a few hours initially.
Most likely causes and fixes:
- No recent traffic: Generate some test requests to your Front Door endpoint, then wait 15-30 minutes.
- Log categories: Double-check Diagnostic Settings has "FrontdoorAccessLog", "FrontdoorHealthProbeLog", etc., enabled (not just metrics).
- Query the right place: In Logs, run:
Or start broad:AzureDiagnostics | where | where TimeGenerated > ago(1h) | take 10search * | where TimeGenerated > ago(1h)
Your Global Front Door to East US workspace is fully supported no region issues here. If nothing shows after traffic and 1-2 hours, try recreating the diagnostic setting or verifying workspace permissions (e.g., Log Analytics Contributor).
Reference:
Kindly let us know if the above helps or you need further assistance on this issue.
PPlease do not forget to
and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.