Current Release Notes for Adobe Experience Manager as a Cloud Service release-notes

The following section outlines the feature release notes for the current (latest) version of Experience Manager as a Cloud Service.

NOTE
From here, you can navigate to release notes of previous versions such as 2023 or 2024.
Have a look at the Experience Manager Releases Roadmap to learn about the upcoming feature activations for Experience Manager as a Cloud Service.
NOTE
To receive a monthly email notification about updates to Experience Cloud release notes, subscribe to the Adobe Priority Product Update.

Release Date release-date

The release date of Adobe Experience Manager as a Cloud Service current feature release (2025.10.0) is October 30, 2025. The next feature release (2025.11.0) is planned for November 20, 2025.

Maintenance Release Notes maintenance

You can find the latest maintenance release notes here.

Experience Manager Sites as a Cloud Service sites

New features in Experience Manager Sites new-sites

  • The Content Model Editor for AEM Content Fragments has been modernized to align with other React Spectrum–based interfaces in AEM. Its user interface implementation and extensibility model are now consistent with the Content Fragment Editor and Universal Editor. The new Model Editor is now default when opened from the new Content Model Admin UI. Opening a content model in Touch UI opens the Touch UI editor and offers to try out the new editor.

  • Launches for Content Fragments: The Launches tab of the Content Fragments console allows you to create launches, list all existing launches, see key properties, and take actions on them.

Experience Manager Forms as a Cloud Service forms

New features in Experience Manager Forms new-features-forms

Universal Editor for Adaptive Forms and Form Fragments

The Universal Editor now delivers a unified authoring experience for creating Adaptive Forms and reusable Form Fragments. Authors can visually design forms, configure submit actions, and integrate reCAPTCHA validation within an intuitive WYSIWYG environment.

New Early Access Features in AEM Forms forms-new-early-access-features

The AEM Forms Early Access Program offers a unique opportunity for you to get exclusive access to cutting-edge innovations and help shape their development.

These release notes list the innovations delivered in the current release. For the complete list of innovations available under the Early Access Program, see AEM Forms Early Access Program documentation.

Interactive Communication Enhancements

Template Locking

Lock content and layout elements within templates to maintain brand integrity and prevent unauthorised modifications. This ensures design consistency across all communications.

Content Overflow Support

Introducing the “Allow page breaks within content” option for flowed layouts. This enhancement enables smooth multi-page editing and better text management for complex documents.

XDP File Editing

The Interactive Communication editor now supports XDP editing, including fragment integration. You can now edit XDP files in a browser instead of Forms Designer that runs only on Microsoft Windows desktop.

Dynamic Page Numbering

Automatically display “Page # of ##” on master pages for clear, consistent pagination across multi-page documents.

Experience Manager as a Cloud Service Foundation foundation

New Features in Release Management new-features-release-management

Pause Automatic Maintenance Updates

Go‑live days, live events, peak sales—these moments can’t break. Our new self‑service features stop automatic mainteanance updates when it matters, so your teams stay focused.

  • Quiet Hours: Block automatic maintenance during set times each day. Ideal for working hours, nightly runs or morning cutovers.
  • Update‑Free Period: Block automatic maintenance for a full week. Use it for launches, promos, or yearly freezes.
NOTE
Available as a Limited Availability feature on September 25th.
Email aemcs-update-free@adobe.com to get it activated on your programs.

AEM Log-Forwarding to More Destinations log-forwarding

It is now possible to forward AEM logs to Amazon S3, Sumo Logic, Dynatrace, and your own New Relic account (not the Adobe-provided account). Note that AEM logs (including Apache/Dispatcher) are supported for these logging destinations, but not CDN logs.

See the full set of supported log forwarding destinations.

Config Pipeline for Edge Delivery Services config-pipeline-eds

Config Pipelines are now supported for sites built with Edge Delivery Services, expanding this capability beyond just AEM Author and AEM publish delivery. You can use Config Pipelines to manage settings such as CDN configuration, including traffic filter rules and origin selectors. See Supported Configurations.

Edge Delivery config pipelines also support secrets through Cloud Manager pipeline variables.

See Add Edge Delivery Pipeline.

Upcoming Java API Deprecations java-api-deprecation

Several deprecated APIs were marked for removal on August 31st and thus should no longer be referenced. You will receive Actions Center notifications if deprecated API usage is detected in your code, and after Nov 13th, notices will appear during Cloud Manager builds to reinforce the importance of removing usage. See the deprecation article for full details, but for convenience, these APIs are listed below:

Expand to see the Java API deprecations
  • org.apache.sling.commons.auth
  • org.apache.felix.webconsole
  • org.eclipse.jetty
  • com.mongodb
  • org.apache.abdera
  • org.apache.felix.http.whiteboard
  • org.apache.cocoon.xml
  • ch.qos.logback
  • org.slf4j.spi
  • org.slf4j.event
  • org.apache.log4j
  • com.google.common
  • com.drew
  • org.bson
  • org.apache.jackrabbit.oak.plugins.blob
  • org.apache.jackrabbit.oak.plugins.memory

Java 11 Runtime Deprecation java11-runtime-deprecation

Adobe upgraded Stage and Production environments to the higher-performance Java 21 runtime on October 14th, 2025. Starting late January, neither the AEM Cloud Service SDK nor any cloud environments will work with Java 11 runtime.

NOTE
To take advantage of the latest performance optimizations and language enhancements, it is recommended to build with Java 17 or Java 21 (preferred). Building with Java 8 and Java 11 remains supported for now but will be deprecated in an upcoming release. A separate communication will be issued prior to deprecation. See the build time requirements section of this article.

Enforcement of AEM Java Logs Configuration Policy logconfig-policy

As noted in the April release notes, AEM Java logs must follow a standard format to ensure reliable monitoring across all customer environments. Custom log configurations—such as changes to log formatting, output files, or default log levels—are no longer supported. Logs must remain directed to the default files, and default log levels for AEM product code must be preserved. See full details in the Logging article.

Starting on November 20th, any unsupported custom logging overrides will be ignored. Based on our analysis, most customers will not be impacted and Adobe has contacted customers whose current configuration may be affected.

Please review and update any downstream processes that rely on custom logging behavior. For example:

  • If your log forwarding system expects a custom log format, you may need to adjust your ingestion rules.
  • If you’ve previously reduced log verbosity by changing log levels, please note that reverting to default levels may increase log volume.

Edge Computing (Beta Program) edge-computing

Edge computing allows you to execute JavaScript at the CDN layer, bringing data processing closer to the end user. This reduces latency and enables responsive, dynamic experiences at the edge.

Common use cases include:

  • Personalizing content based on geolocation, device type, or user attributes
  • Acting as middleware between the CDN and your origin
  • Reformatting responses from third-party APIs (and perhaps aggregating multiple API responses) before delivering them to the browser
  • Composing and serving server-rendered HTML at the edge using content stitched from various backends
  • Exposing an MCP server for LLMs like ChatGPT and Claude to access custom tools

We have a limited number of opportunities available for either AEM Publish Delivery or Edge Delivery Services projects for live production sites. If you’re interested in participating or want to learn more, please email aemcs-edgecompute-feedback@adobe.com with a brief description of your use case.

Edge Authentication for Edge Delivery Services (Beta Program) edge-authentication

Edge Authentication lets you restrict access to Edge Delivery Services pages to only those who have authenticated with your identity provider (IdP). This is achieved by deploying an OpenID Connect (OIDC) configuration YAML file.

If interested, please email aemcs-edgecompute-feedback@adobe.com with a brief description of your use case and any questions you may have.

Canary Production Deployments to Test Code Before Accepting Live Traffic (Beta Program) canary-beta

Validate a production build with internal-only test traffic before exposing it to end users. Ship to production, route only canary traffic (using a special header), monitor behavior, then either promote to live traffic or roll back—without impacting customers.

Deploy your code releases to production, but restrict it to only internal test traffic before deciding whether to accept live traffic versus rolling back.

Email aemcs-canary-deployments-beta@adobe.com to request access and share feedback.

AI Answers - Smarter, Context-Aware Responses for AEM Sites (Beta Program) ai-answers-beta

AI Answers introduces a new way for your visitors to interact with your content. Powered by Retrieval-Augmented Generation (RAG) technology, it uses your AEM-managed data to deliver accurate, brand-consistent answers directly within your digital experiences.

As part of this beta, you can safely explore AI Answers in your AEM Cloud Service environment. This approach lets you validate performance, accuracy, and overall experience before making it available to your live audience. Once validated, you can promote your AI Answers experience to full production.

To request beta access or share your feedback, please contact feedback-ai-answers@adobe.com.

Snapshots for RDEs (Alpha Program) rde-snapshot-program

In alpha, Rapid Development Environments (RDEs) now support a feature to take a snapshot of the current state of code and content, which can be restored at a later time. This can be useful when syncing code that may need to be reverted, or when switching between development of different features. It’s also possible to restore just the mutable content as a known starting point for testing.

Please email aemcs-rde-support@adobe.com if there’s interest in providing feedback on this feature.

Expanded Application Performance Monitoring (APM) (Alpha program) apm-alpha

For observability, AEM Cloud Service currently supports Adobe-provided New Relic One and customer-managed Dynatrace. As we explore support for additional APM options, please email us at aemcs-apm-beta@adobe.com with your preferred vendor or technology, along with use cases.

Experience Manager Guides guides

You can find a complete list of new and enhanced features of the latest release of Adobe Experience Manager Guides here.

Cloud Manager cloud-manager

You can find a complete list of Cloud Manager monthly releases here.

Migration Tools migration-tools

You can find a complete list of Migration Tools releases here.

Universal Editor universal-editor

You can find a complete list of Universal Editor releases here.

Generate Variations generate-variations

You can find a complete list of Generate Variations releases here.

Experience Cloud Release Notes experience-cloud

You can find information about releases of other Experience Cloud applications here.

recommendation-more-help
fbcff2a9-b6fe-4574-b04a-21e75df764ab