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.
Release Date release-date
The release date of Adobe Experience Manager as a Cloud Service current feature release (2025.6.0) is June 26, 2025. The next feature release (2025.7.0) is planned for July 31, 2025.
Maintenance Release Notes maintenance
You can find the latest maintenance release notes here.
Experience Manager Assets as a Cloud Service assets
Enhanced Metadata Form management in Assets View
You can now import metadata forms from Admin view directly into Assets view. Any updates made to these forms in Assets view automatically reflect in Admin view, ensuring consistency across both experiences. This capability supports a seamless transition to the new Assets view while maintaining continuity with your existing metadata configurations.
New Features in Content Hub new-features-content-hub
Collections governance
Content Hub now lets you control access to collections during creation, ensuring only authorized users can view or manage grouped assets. It ensures improved security, better collaboration, organized asset management, and simplified governance.
Experience Manager Forms as a Cloud Service forms
- Universal Editor for Adaptive Forms and Form Fragments: The Universal Editor now supports the creation of both Adaptive Forms and reusable Form Fragments. Authors can visually build forms, configure submit actions, and add reCAPTCHA validation, all in a simplified, WYSIWYG authoring environment. This capability accelerates form creation, enhances consistency, and improves protection against spam and automated abuse.
Pre-release Features
-
Generate and Sync AFP Renditions from Adaptive Forms: The AFP Output Sync API enables administrators and users to generate AFP (Advanced Function Presentation) output from Adaptive Forms and synchronize the output with external systems or storage locations. AFP is a high-performance document format optimized for printing, often used in large-scale enterprise environments.
-
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 forms-new-early-access-features
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 of AEM Forms with Adobe Experience Platform: The AEM Forms to Adobe Experience Platform Connector enables seamless integration between Adaptive Forms and Adobe Experience Platform. This feature allows form data to be mapped to XDM schemas and submitted directly to AEP in real time. It streamlines data capture for personalization and activation use cases across Adobe Experience Cloud solutions.
Experience Manager as a Cloud Service Foundation foundation
Updated Deprecation Process updated-deprecation-process
Adobe regularly reviews features, libraries, APIs, and configurations to ensure they meet standards for performance, security, and value. When capabilities no longer meet these standards, they are marked for deprecation and usage must stop by a specified removal date. Leading up to this date, Adobe will remind customers with email notifications, and actions that need to be taken in Cloud Manager before proceeding with or deploying new builds. Failure to take the necessary action may result in an inability to upgrade to new versions of AEM leading to potential impacts around security, performance, reliability, and availability.
See the deprecation article for further information.
Deprecated Java APIs and OSGi configuration nearing removal dates deprecated-near-removals
Expand the list below to view the deprecated APIs and OSGi configurations that must no longer be used. For full details—including removal timelines—refer to the deprecation article.
Java APIs:
org.apache.sling.commons.authorg.apache.felix.webconsoleorg.eclipse.jettycom.mongodborg.apache.abderaorg.apache.felix.http.whiteboardorg.apache.cocoon.xmlch.qos.logbackorg.slf4j.spiorg.slf4j.eventorg.apache.log4jcom.google.commoncom.dreworg.bsonorg.apache.jackrabbit.oak.plugins.bloborg.apache.jackrabbit.oak.plugins.memory
OSGi properties:
org.apache.sling.commons.log.LogManager(all properties)org.apache.sling.commons.log.LogManager.factory.config(org.apache.sling.commons.log.file,org.apache.sling.commons.log.pattern)
Java 11 Runtime Deprecation java11-runtime-deprecation
The Java 11 runtime is now deprecated, and most environments have already been upgraded to the more performant Java 21 runtime.
If your environment could not be upgraded due to unsupported dependencies (see Java 21 runtime requirements), you should have received an email from Adobe with specific next steps. Please ensure all required updates are completed by August 28, 2025, so your environment can be upgraded without disruption.
Note: The runtime version is separate from your code’s build version. While we recommend building with Java 21, Java 11 builds are still supported for now. A separate deprecation notice for Java 11 builds will be shared in the future.
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 in late August, 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.
Default Purging of Older Versions and Audit Logs mt-defaults
Currently, content versions and audit logs have their associated purge maintenance tasks disabled by default and thus no data is removed unless explicitly configured.
However, to optimize repository performance, starting in early July 2025, purging will be enabled by default, following these guidelines:
Content Versions mt-content
-
New environments (created after an upcoming date (to be communicated later)
- Versions older than 30 days will periodically be deleted.
- The most recent five versions within the last 30 days are retained, along with the most recent version and the current version, regardless of their age.
-
Existing environments (created before this upcoming date):
- Versions older than 7 years will periodically be deleted.
- All versions within the past 7 years are retained.
- This high default threshold prevents unintended removal of recent data. However, it is recommended to configure lower values to optimize repository performance.
-
You may modify these defaults through YAML configuration, deployed using the config pipeline.
Audit Log mt-auditlogs
-
New environments (created after an upcoming date, which will be communicated separately):
- Replication, DAM, and page audit logs older than 7 days will periodically be deleted.
- All events are logged by default.
-
Existing environments (created before this upcoming date):
- Replication, DAM, and page audit logs older than 7 years will periodically be deleted.
- All events are logged by default.
- This high default threshold prevents unintended removal of recent data. However, it is recommended to configure lower values to optimize repository performance.
-
You may modify these defaults through YAML configuration, deployed using the config pipeline.
For more details, see the Maintenance Tasks article.
Edge Computing (Alpha 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:
- Authenticating users with an identity provider before granting access to content
- 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 APIs responses) before delivering them to the browser
- Composing and serving server-rendered HTML at the edge using content stitched from various backends
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.
CDN Configuration for Edge Delivery Services (Beta Program) cdn-eds-beta
The Adobe-Managed CDN offers flexible configuration options, as described in the Config Pipeline article.
Now in a beta, deploy a config pipeline for features including CDN origin selectors, response and request transformations, and more. Please reach out to aemcs-cdn-config-adopter@adobe.com with the details of your use case.
AEM Log-Forwarding to More Destinations (Beta Program) log-forwarding-beta
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 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.
Now in beta, you can forward AEM logs to Amazon S3, Sumo Logic, 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. Email aemcs-logforwarding-beta@adobe.com for access.
Learn more in the log forwarding documentation.
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.