DocumentationExperience Cloud KCS

Azure Blob log forwarding doesn’t create date-partitioned folders in AEM as a Cloud Service

Last update: October 5, 2026

This article explains how Adobe Experience Manager (AEM) as a Cloud Service stores logs forwarded to Azure Blob Storage and why the documented configuration doesn’t create date-partitioned folders. To organize logs by date, use customer-managed post-processing after delivery or submit a feature request.

Description description

Environment

  • Adobe Experience Manager (AEM) as a Cloud Service
  • Log Forwarding to Azure Blob Storage

Issue/Symptoms

  • Azure Blob log forwarding stores files under log-type folders rather than in date-partitioned folders.
  • CDN log files are written under aemcdn/ with timestamps in their filenames.
  • AEM and Apache/Dispatcher log files are written under folders such as aemaccess/; a single file under each folder is appended to.
  • You need logs organized into date-based folders for querying or management.

Cause

The documented Azure Blob Storage log-forwarding configuration doesn’t provide a setting for a custom folder path or date partitioning. It writes logs under folders based on log type. Customers can process and manage the delivered files, but date-based folder organization requires downstream processing outside the AEM log-forwarding configuration.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Review your current AEM as a Cloud Service log-forwarding configuration for Azure Blob Storage.
  2. Review the Azure Blob Storage section of Adobe’s Log Forwarding documentation and the available configuration options in Cloud Manager. The documented configuration doesn’t provide a setting for date-partitioned folders.
  3. If you require date-partitioned folders, submit a feature request through the Adobe Experience League forums or discuss the request with your Adobe Support contact.
  4. As a customer-managed workaround, use post-processing scripts or Azure Data Factory pipelines to reorganize the logs after they’re written to Blob Storage. These downstream workarounds aren’t officially supported by Adobe.
recommendation-more-help
experience-cloud-kcs-help-kbarticles