Documentation AEM as a Cloud Service User Guide

Current Release Notes for Adobe Experience Manager as a Cloud Service

Last update: May 15, 2025

Applies to:
Experience Manager as a Cloud Service

Topics:
Release Information

CREATED FOR:

Admin

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

The release date of Adobe Experience Manager as a Cloud Service current feature release (2025.4.0) is April 24, 2025. The next feature release (2025.5.0) is planned for June 5, 2025.

Maintenance Release Notes

You can find the latest maintenance release notes here.

Experience Manager Sites as a Cloud Service

New features in Experience Manager Sites

New Content Fragment Model Admin UI

Further completing the list of new client-side user interfaces when working with AEM Content Fragments, a new admin UI is now available for content fragment models. The new UI provides a clean and modern list view that allows searching models with filters, and that shows model tags and which content fragments exist that are based on a certain model. Documentation can be found here.

Experience Manager Assets as a Cloud Service

Dynamic Media (Scene7)

Dynamic Media (Scene7) not supported in Enhanced Security environments

Dynamic Media (Scene7) on AEM as a Cloud Service is not HIPAA-ready and cannot be used in AEM environments where Enhanced Security is enabled.

Starting with the April 2025 AEM as a Cloud Service release, a technical restriction prevents Dynamic Media (Scene7) from being configured in environments with Enhanced Security. As a result, the Dynamic Media Configuration card under Tools > Cloud Services is no longer visible in these environments.

Additionally, customers using AEM 6.5 should be aware that the Dynamic Media (Scene7) stack is not HIPAA-ready.

Dynamic Media Classic

Reporting

The Bandwidth tab in the Dynamic Media Classic reporting dashboard is no longer supported as of April 2025.

See Bandwidth and Storage, Types of reports.

New features in Assets View

Asset relations

The Assets View now supports viewing and editing asset relations in a simplified asset Details panel. Easily add relationships like Source and Derivative to content so that users can more effectively find relevant hero content.

Assets relation example

Compare versions of an asset

You can now quickly select and compare any version of an asset with its latest version using the Assets view.

compare versions of asset

Experience Manager Forms as a Cloud Service

Pre-release Features

Universal Editor - Form Fragments: The Universal Editor now allows you to create and reuse Form Fragments for Adaptive Forms. These fragments are reusable form sections (e.g., contact details, consent fields) that can be built once and applied across multiple forms. This feature streamlines form creation, ensures consistency, and improves authoring efficiency.
SharePoint Document Library - Save Attachments with Original Filenames: You now have the option to save form attachments using their original filenames when storing them in a SharePoint Document Library. This enhancement simplifies the identification and management of uploaded files.
Rule Editor:
- Binary Condition with Click Event in “When” Clause: The Rule Editor now allows combining a button click event (Is Clicked) with other conditions within the “When” clause. This enables more precise control over rule execution based on user interaction and other factors. Note: When using multiple conditions, the click event must be the first condition listed.
- Validation Conditions for Fields and Panels: The Rule Editor now includes IsValid and IsNotValid conditions. These allow you to check the validation status of specific fields or entire panels (including layouts like Horizontal Tabs, Vertical Tabs, Accordions, and Wizards), facilitating improved form navigation and user experience based on validation results.
Improved Scope Management for SharePoint Lists: SharePoint sites now support all managed paths, for example, /sites and /teams. This enhancement enables broader integration across various SharePoint site structures, offering greater flexibility in connecting to organizational content.
Support for Saving Document of Record to SharePoint List: Forms created using a SharePoint List–based Form Data Model (FDM) can now save the Document of Record (DoR) to SharePoint Lists by configuring the Document of Record Bind Reference field property. This enhancement enables seamless integration of supported form data and documents with SharePoint storage.

Early Access Features in AEM Forms

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

This release notes lists 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.

Adobe Experience Platform (AEP) Integration with Forms

Integration capabilities between Forms and AEP are now available for early adopters.

CIF Add-on

Enhancements

Adding product variant selection for CIF product reference data type
[Experimental]: JSON+LD in CIF Core Components in PDPs
[Experimental]: CIF ability to clear cache

Bug fixes

Fix search issue in product field
Product url format not working as expected for #variant_sku
Unable to Add More Than 20 SKUs to Product List Component

Experience Manager as a Cloud Service Foundation

OpenAPI-based APIs

Developers can deeply integrate AEM as Cloud Service features into their own applications and tools. New AEM as a Cloud Service APIs follow the OpenAPI specification, with a goal of being consistent, well-documented, and user-friendly. Credentials for endpoints requiring authentication are generated by creating Adobe Developer Console projects and support OAuth Server-to-Server, Web App, and Single Page App (SPA).

See the full list of OpenAPI-based APIs, learn more, and try out an end-to-end tutorial illustrating configuration and usage.

Watch this video to learn how to configure an authenticated API for later usage:

video poster

https://video.tv.adobe.com/v/3457510?quality=12&learn=on

Domain Mapping-related Enhancements

The Adobe-Managed CDN offers flexible configuration options, as described in the Config Pipeline article. Here are a few recent features:

Include Additional Properties in CDN Logs

Useful for scenarios including debugging and data analysis, you can include more information in your CDN logs beyond the default properties by setting the logProperty action in request and response transformations.

Region, Continent, and Organization Properties as Matching Conditions

CDN rules can now match based on region, continent, and organization for use cases including blocking traffic and redirects. clientRegion and clientContinent augment the already-supported clientCountry to match based on geography, while clientAsName and clientAsNumber match Autonomous Systems to identify large ISPs, companies, or cloud providers. Learn more about these newly exposed request properties.

You can set cookie attributes in response tranformations.

Java 21 Support

As of the January release, you can build code with Java 21 and Java 17. You gain access to new features like pattern matching, sealed classes, and various performance improvements. For configuration steps, including updating your Maven project and library versions, see the Build Environment article.

The more performant Java 21 runtime is automatically deployed when a Java 17 or 21 build is detected. However, Adobe also recommends opting into the Java 21 runtime for environments built with Java 11, by emailing aemcs-java-adopter@adobe.com. Learn about Java 21 runtime requirements.

IMPORTANT

The Java 21 runtime was deployed to your dev/RDE environments in February; it will be applied to your stage/production environments on April 28 and 29. Note that building code with Java 21 (or Java 17) is independent of the Java 21 runtime – you must explicitly take steps to build code with Java 21 (or Java 17).

Enforcement of AEM’s Logging Configuration Policy

To ensure effective monitoring of customer environments, AEM Java logs must maintain a consistent format and should not be overridden by custom configurations. Log output must remain directed to the default files. For AEM product code, default log levels must be preserved. However, it is acceptable to adjust log levels for customer-developed code.

To that end, changes should not be made to the following OSGi properties:

Apache Sling Log Configuration (PID: org.apache.sling.commons.log.LogManager) — all properties
Apache Sling Logging Logger Configuration (Factory PID: org.apache.sling.commons.log.LogManager.factory.config):
- org.apache.sling.commons.log.file
- org.apache.sling.commons.log.pattern

In mid-May, AEM will enforce a policy where any custom modifications to these properties will be ignored. Please review and adjust your downstream processes accordingly. For example, if you use the log forwarding feature:

If your logging destination expects a custom (non-default) log format, you may need to update your ingestion rules.
If changes to log levels reduced log verbosity, be aware that the default log levels may result in a significant increase in log volume.

AEM Log-Forwarding to More Destinations - Beta Program

Now in beta, you can forward AEM logs to New Relic (using HTTPS), Amazon S3, and Sumo Logic. Note that AEM logs (including Apache/Dispatcher) are supported, but not CDN logs. Email aemcs-logforwarding-beta@adobe.com for access.

While logs can be downloaded from Cloud Manager, many organizations find it beneficial to stream those logs to a preferred logging destination. AEM already supports (GA) AEM and CDN log forwarding to Azure Blob Storage, Datadog, HTTPS, Elasticsearch (and OpenSearch), and Splunk. This feature is configured in a self-serve manner, and deployed using the Config Pipeline.

Learn more in the log forwarding documentation.

Edge Computing - Request for Feedback!

Edge computing brings data processing closer to the browser, which has benefits including reduced latency. Adobe would like to hear if you find this technology useful for AEM Publish Delivery and Edge Delivery Services projects. Additionally, let us know what you envision using it for as input into the product roadmap.

Some possible use cases:

Authentication with an IdP to gate access to content
Personalization by rendering dynamic content based on geolocation, device type, user attributes, etc.
Advanced image manipulation
Middleware between the CDN and an origin
A layer between the browser and a third-party API, perhaps to reformat the API response
Aggregating data from multiple origins to make it easier for the client browser to render it

Email aemcs-edgecompute-feedback@adobe.com with questions and comments!

Experience Manager Guides

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

Cloud Manager

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

Migration Tools

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

Universal Editor

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

Generate Variations

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

Experience Cloud Release Notes

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

recommendation-more-help