DocumentationExperience Cloud KCS

AEM as a Cloud Service log rotation and retention for Azure Blob Storage

Last update: October 22, 2026

✨ This content is AI generated and could be inaccurate. Generative AI Terms

This article explains how Adobe Experience Manager as a Cloud Service handles log rotation and retention for logs forwarded to Azure Blob Storage, and provides guidance for managing log lifecycle on the Azure side.

Description description

Environment

Adobe Experience Manager as a Cloud Service (all versions)

Symptoms

  • Log files forwarded to Azure Blob Storage continue to grow in size for several days, with new log entries appended to the same blob or file.
  • Multiple files may appear under the same log type, each with different pod identifiers in the filename.
  • Uncertainty exists about whether log rotation is time-based, size-based, or triggered by pod changes or restarts.
  • There is no clear indication of when a log file will stop receiving new entries or when it will be closed.
  • The timestamp in the filename does not reliably indicate the blob’s creation time.
  • No error messages are generated, but the lack of clear rotation or closure points complicates lifecycle management on the Azure side.

Cause

AEM as a Cloud Service does not enforce a fixed log rotation or retention policy for logs forwarded to Azure Blob Storage. Log files remain open and continue to receive entries as long as their source pod is active, requiring customers to manage retention and lifecycle on the Azure side.

Resolution resolution

Follow the steps below to manage log rotation and retention:

  1. Understand that AEM as a Cloud Service forwards logs to Azure Blob Storage in files specific to each pod or source, and log entries are continuously appended as long as the source remains active.
  2. Note that there is no documented time-based or size-based rotation schedule enforced by Adobe for these log files.
  3. Be aware that a new file may be created if a new pod is started or the source changes, but not necessarily on every pod restart.
  4. Recognize that Adobe does not provide customer-configurable rotation or retention settings for these logs.
  5. Use Azure Blob Storage properties and metadata for lifecycle management, rather than relying on the filename timestamp.
  6. Implement segmentation, retention, and lifecycle management policies on the Azure side to handle log file growth and retention as needed for your environment.
  7. Regularly monitor blob sizes and use Azure’s lifecycle management features to archive or delete blobs according to your requirements.
recommendation-more-help
experience-cloud-kcs-help-kbarticles