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

The following section outlines the feature release notes for the 2026.10.0 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 (2026.10.0) is October 29, 2026. The next feature release (2026.11.0) is planned for November 19, 2026.

Maintenance Release Notes maintenance

You can find the latest maintenance release notes here.

Release Overview overview

The 2026.10.0 release of Experience Manager as a Cloud Service highlights new and recently available capabilities across Sites, Assets, Forms, and Foundation, alongside updates to developer tools and platform guidance.

Highlights of this release

  • More flexible content and media experiences: Sites prerelease adds a Composite data type for Content Fragments. Assets highlights include multilingual video captions and audio tracks, branded video playback, and a GIF-based countdown timer for Dynamic Media email templates.
  • AI-assisted governance and troubleshooting: The AEM Governance Agent can help prioritize vulnerability findings, while new capabilities in CX Enterprise Coworker let developers inspect workflows and investigate Dispatcher behavior using natural-language prompts.
  • Expanded developer and migration tooling: The Cloud Migration Agent skill adds migration patterns and beta validation, and the unified AEM MCP Server now supports Cloud Migration capabilities.
  • Platform changes to prepare for: The AEM Cloud Service SDK supports Java 25 for local development. Review the notices on CDN egress IP allowlists, the transition from built-in New Relic APM to OpenTelemetry, and deprecated Java APIs.

A range of beta, early adopter, and Limited Availability programs are also available this release. See the sections below for details.

AEM Beta Programs aem-beta-programs

Adobe Experience Manager (AEM) beta programs are a way for customers to get access to prerelease features and code, provide feedback, and guide the future of AEM.

IMPORTANT
Beta releases may contain defects and are provided “AS IS” without warranty of any kind. Adobe has no obligation to maintain, correct, update, change, modify or otherwise support (by way of Adobe Support Services or otherwise) the beta releases. Adobe advises customers to use caution and not rely on the correct functioning or performance of beta releases, or on any accompanying documentation or materials. Features and APIs in beta are subject to change without notice. Accordingly, any use of the beta releases is entirely at the customer’s own risk.

Benefits of participating

Getting early access to features that Adobe is developing lets customers and partners provide feedback and shape product development. It also helps them prepare to adopt new capabilities before general availability.

Current beta programs

The following sections list active beta programs.

Agents in AEM agents-in-aem

If you would like to explore the powerful, new AEM agentic capabilities across production, governance, optimization, discovery, and development, please learn about how you can access them here.

AEM Foundation (Beta programs) aem-foundation-beta-programs

See AEM Foundation beta programs.

Cloud Manager (Beta programs) cloud-manager-beta-programs

See Cloud Manager beta programs.

AEM Assets (Beta programs) aem-assets-beta-programs

See AEM Assets beta programs.

Experience Manager Sites as a Cloud Service sites

New features in Experience Manager Sites Prerelease prerelease-sites

Composite data type for Content Fragments

Content Fragment models can now use the Composite data type to group related fields and repeat them as a list inside a fragment. Composite content is stored in the fragment itself, so GraphQL and the OpenAPIs deliver it in one response without resolving references. See Composite Data for more information.

Experience Manager Assets as a Cloud Service assets

This section highlights new and recently available capabilities for Experience Manager Assets. It includes features that became Generally Available (GA) in the current release, as well as features that are currently in Limited Availability (LA) or Beta. LA and Beta features remain listed in this section until they become generally available.

Experience Manager as a Cloud Service Assets General Availability Features assets-general-availability-features

Dynamic Media with OpenAPI capabilities: Multi-caption and multi-audio track support for videos multi-caption-multi-audio

Dynamic Media with OpenAPI capabilities now support multiple captions and multiple audio tracks for video assets. It enables organizations to deliver localized and accessible video experiences to global audiences by associating multiple language-specific caption and audio tracks with a single primary video. Authors can efficiently manage these tracks from a unified interface, simplifying multilingual content delivery and supporting regional accessibility requirements.

Dynamic Media with OpenAPI capabilities: AI-generated video captions ai-generated-video-captions

AI-generated video captions in Dynamic Media with OpenAPI capabilities use artificial intelligence to generate captions automatically for video content. This feature is designed to improve accessibility and enhance the user experience by providing accurate, real-time captions. The AI analyzes the video’s audio track to transcribe speech and create captions, which can be edited for accuracy or customization. These captions help meet accessibility requirements and improve video engagement for audiences who rely on or prefer text-based video support.

Dynamic Media: GIF-based countdown timer gif-based-countdown-timer

AEM Dynamic Media now brings a GIF-based countdown timer to email templates, creating urgency at the moment of open and driving click-through on time-sensitive offers. Administrators can configure a Days/Hours/Mins/Secs display, a custom suffix, post-expiry fallback text, and a clickable destination URL.

Dynamic Media: Branded video viewer and customizable presets new-video-viewer-presets

Dynamic Media Branded video viewer delivers a performant, accessible, and fully customizable playback experience. Configurable playback modifiers, including autoplay, loop, and muted, give you complete control over viewer behavior. Custom CSS support and reusable branded video viewer presets let you customize player colors, controls, button styles, playback speeds, and video presentation settings for a consistent, on-brand experience across desktop, tablet, and phone layouts. Apply presets to videos in asset details, AEM Sites components, or playback URLs. Actionable analytics track views, watch time, completion rate, and engagement score, providing meaningful insights into video performance.

Content Hub: AI Search ai-search-content-hub

AEM Assets Content Hub now includes AI Search, an advanced search capability that understands the meaning and intent behind user queries instead of relying only on exact keyword matches. AI Search delivers more accurate and context relevant results by recognizing relationships between words, concepts, and user intent. It supports multilingual queries, handles misspellings and typos, understands synonyms, and surfaces relevant assets even when users do not use exact metadata terms.

For example, a search for Woman drinking coffee can also return assets tagged with related terms such as Lady, Girl, Latte, or Cappuccino.

Administrators can enable or disable AI Search in Content Hub using the Configurations menu by selecting either AI Search or traditional keyword search.

Content Hub: Custom Sorting options custom-sorting-options-content-hub

Content Hub now allows administrators to enable custom metadata fields as sorting options on the Content Hub home page. In addition to the default sorting options, Size, Modified, Name, and Relevance, administrators can configure business-specific metadata fields such as Channel, Region, SKU, or Campaign to help users organize search results more effectively.

Content Hub: Smart Collections smart-collections

Smart Collections enable you to automatically organize assets based on defined search criteria.
When you create a Smart Collection, the collection stores the search query and filter criteria instead of storing individual assets. Assets that match the configured criteria are automatically displayed in the collection.

Smart Collections automatically remain up to date. When newly approved assets satisfy the configured search criteria, they are automatically added to the collection.

Experience Manager as a Cloud Service Assets Limited Availability Features assets-limited-availability-features

Native Dynamic Media Template component in Adobe Journey Optimizer dynamic-media-component-ajo

The native Dynamic Media Template component lets marketers add and personalize AEM Dynamic Media templates directly in the Adobe Journey Optimizer email editor. Marketers can select existing templates or import layered PSD files, edit individual layers such as countdown timers, and configure text, CTAs, positioning, and timing without leaving the email editor. This enables governed, personalized, and dynamic email experiences, including open-time countdowns and personalized product content.

Dynamic Media with OpenAPI capabilities: Secure Delivery with Attribute-based Access Control secure-delivery-attribute-based-access-control

Attribute-based access control lets admins govern access to Dynamic Media with OpenAPI capabilities assets using metadata-driven rules defined for each user group. IMS-based restrictions allow DAM admins and brand managers to restrict delivery of specific assets to designated Adobe IMS users or groups. Users outside the permitted list receive a 404 response, and the asset is not delivered. This provides a secure way to manage asset delivery for campaigns, product launches, and other controlled distribution scenarios.

Dynamic Media with OpenAPI capabilities: Barcode and QR Code delivery barcode-qr-code

Dynamic Media with OpenAPI capabilities can now generate barcode and QR code images on demand and deliver them through hosted image URLs, which is useful for channels such as campaign emails. Request parameter locking protects selected values, such as the barcode value and type, so a changed value can not produce a different barcode with the same lock.

To request enablement, open an Adobe Customer Support ticket.

Content Hub lets you share multiple assets and collections through public links and update existing links by adding or removing assets and collections at any time. Administrators can manage shared links with controls for password protection, expiration, and link revocation to help govern external access. Branded recipient experiences help maintain brand consistency when sharing assets with external stakeholders.

Experience Manager as a Cloud Service Assets Beta Features assets-beta-program-features

Content Advisor browser extension content-advisor-browser-extension

Use the power of AEM Content Advisor for AEM Assets, in the application of your choice with the browser extension available here.

Why you will love it?

  • Zero setup, zero code. Install it, sign in, and start working. No integration, no custom connectors, no developer tickets.

  • Smarter suggestions, on your terms. Recommendations come from the whole page, or narrow them by selecting a region, highlighting text, or choosing an image. The more precisely you point, the sharper the results.

  • Pick exactly what you need. Choose any asset or any Dynamic Media rendition (the right size, format, or crop) and send it straight to your editor. Insert, drag and drop, or copy URL to the clipboard.

  • Works where you author. AEM (Cloud Service, Adobe Managed Services, or On-premise), other Adobe CX Enterprise products (where AEM Assets native integration does not exist), and third-party tools such as Google Docs/WordPress/Microsoft Powerpoint, and any other web application.

For more information, see Use AEM Content Advisor with the browser extension.

To send feedback, participate or learn more, send an email to aem-content-advisor-feedback@adobe.com.

Dynamic Media with OpenAPI capabilities: Video Interactivity video-interactivity

Video Interactivity lets authors add chapters and text, image, and card overlays to videos in Dynamic Media with OpenAPI capabilities. Authors configure them in the Video Interactivity editor. The configuration is saved on the asset and delivered with the approved video metadata for playback in the new Video Viewer.

To participate or learn more, send an email to dm-beta-feedback@adobe.com.

Dynamic Media: Video Engagement Report video-engagement-report

Turn video playback into actionable insight by providing per-video engagement metrics for the New Video Viewer, including views, impressions, watch time, completion rate, and engagement score, delivered as a monthly CSV to help teams measure content performance.

To participate or learn more, send an email to dm-beta-feedback@adobe.com.

Dynamic Media: Operations and Error Report operations-and-error-report

Give teams visibility into delivery health by reporting operational activity such as delivery request counts, smart crops, video encodes, and templates created, while surfacing failed delivery URLs with their referrer and failure count so issues can be pinpointed and fixed.

To participate or learn more, send an email to dm-beta-feedback@adobe.com.

Dynamic Media Template: Auto Translate auto-translate

Eliminate repetitive manual localization by using AI to automatically translate text and turn a single master template into variants across multiple locales, while preserving the visual integrity of your designs.

To participate or learn more, send an email to dm-beta-feedback@adobe.com.

Multi-portal Content Hub multi-portal-content-hub

Deliver tailored Content Hub experiences for each brand or business unit, while managing content centrally from a single source of truth.

To participate or learn more, send an email to aemcontenthubbeta@adobe.com.

AI-powered content onboarding and content supply chain automation ai-powered-content-onboarding-content-supply-chain-automation

The Content Supply Chain Agent provides two cooperating AI-powered agents:

  • CSC Blueprint Agent maps your end-to-end content supply chain, identifies gaps and anti-patterns, and helps define an agreed future state and prioritized action plan.
  • CSC Integration Agent implements governed content and metadata movement between systems through configured connections, supporting both one-time migrations and recurring synchronization.

To participate or learn more, send an email to aem-assets-coinnovation-interest@adobe.com.

UI Extensibility for Assets View ui-extensibility-assets-view-beta

Assets View supports UI Extensibility, a developer-first capability that empowers customers to tailor the out-of-the-box experience to meet their specific business requirements.
Customers can leverage existing stable extension points by following Adobe’s developer documentation to build and deploy extensions with minimal effort. For use cases where a required extension point is not yet available, Adobe works directly with customers to explore the requirements and assess the technical feasibility of delivering new extensibility APIs tailored to their needs, and may deliver such new APIs as Beta Releases.
Additionally, Adobe has developed a GenAI-powered extension generation tool currently available in an internal early adoption phase. This tool can significantly accelerate extension development time. Customers participating in this beta program will receive access to the tool and are encouraged to share feedback to help shape its evolution.
To participate or learn more, send an email to ASSETSVIEWUIEXTENSIBILITY@adobe.com.

Brand Aware Metadata (BAM) brand-aware-metadata-beta

AEM Assets now supports Brand Aware Metadata, an AI-powered capability that automatically generates custom metadata for assets when uploaded or re-processed. This reduces the need for manual entry by orders of magnitude, helping teams find assets and deliver new experiences much faster. Customers maintain a library of prompts that define how AI should populate any given metadata field, tailored to their own brand vocabulary and taxonomy. This prompt library includes a playground to preview results and a prompt optimizer that automatically drafts suggested improvements.

Adobe is actively expanding BAM’s capabilities through direct co-innovation with customers. Where a specific use case is not yet supported, Adobe works with participating customers to understand their needs and may deliver expanded capabilities as the beta progresses. Customers in this program gain early access to new features as they ship and are encouraged to share feedback that directly shapes the roadmap.

To participate or learn more, send an email to AEM-ASSETS-BRANDAWAREMETADATA@adobe.com.

Assets Sourcing portal for AEM Assets asset-sourcing-aem-assets

The Assets Sourcing Portal provides a secure, self-service experience for collecting assets from external contributors without granting them access to Adobe Experience Manager Assets. Contributors can upload assets, provide the required metadata, and submit content directly to a designated intake location while administrators maintain control over asset organization and governance.

Adobe works with participating customers to understand their needs and may deliver expanded capabilities as the limited availability program progresses. Customers in this program gain early access to new features as they ship and are encouraged to share feedback that directly shapes the roadmap.

To participate or learn more, send an email to AEM-Assets-Sourcing-Portal@adobe.com.

Support for additional asset types in Adobe Express integration assets-express-integration-asset-types-beta

Adobe Express integration with Assets helps all users create and edit on-brand content and increase content reuse. We have worked on supporting a growing list of asset / file types to be supported by the integration, and some of them are available early to customers interested in using them:

Asset view UI - “Open in Express” to import an asset into a new Express document in the embedded Express editor:

  • .mp4 video assets

Assets plugin in Adobe Express to import an asset into the current Express document:

  • .ai Adobe Illustrator assets
  • .indd Adobe InDesign assets
  • .mov video assets
  • .mp3 audio assets
  • .gif animated assets

To participate or learn more, send an email to aem-assets-express@adobe.com.

Experience Manager Forms as a Cloud Service forms

New features in AEM Forms forms-new-features

Adaptive Form authoring in CX Coworker adaptive-form-authoring-improvements

Authors can reuse existing designs, connect services, and refine form logic through chat in Adobe CX Enterprise Coworker. These capabilities bring Adaptive Form authoring actions into Coworker:

  • Import PDF or XDP into an Adaptive Form: Ask Coworker to import Portable Document Format (PDF) or XML Data Package (XDP) documents from AEM Assets to use existing designs as a starting point for an Adaptive Form.
  • Call services from form rules: Create rules in CX Coworker using natural language to invoke external services, receive data, and take action based on the response. For example, a form can call an external service to generate and send a one-time password (OTP), then call a service to validate the OTP entered by the user.
  • Create and edit REST API integrations: Create rules in CX Coworker using natural language to connect to a Representational State Transfer (REST) application programming interface (API) and take action based on the response. For example, when a user enters a product code, a form can call a product catalog API to retrieve the product name and price, then populate the corresponding form fields.
  • Edit existing rules: Describe changes in natural language to Coworker to refine existing form rules as requirements change.
  • Code mode for rule authoring: Author form rules in code mode when you need to work directly with rule code.
  • Authoring latency optimizations: Latency optimizations support a more responsive form authoring experience.

Example prompts in CX Coworker (replace the example asset path and field names with your own):

Capability
Example prompt
Import a PDF
“Convert the PDF at /content/dam/formsanddocuments/application.pdf into a Core Components Adaptive Form named Application.”
Call a service from a rule
“When Product Code changes, use the configured product REST API integration to look up that code and populate Product Name and Unit Price from the response.”
Create a REST API integration
“Create an integration using this cURL command and sample JSON response.”
Edit an existing rule
“Change the rule on Company so it is shown when Employee Type is Contractor or Partner.”

CAPTCHA v3 support captcha-v3-support

Use Completely Automated Public Turing test to tell Computers and Humans Apart (CAPTCHA) v3 support to help protect forms from automated submissions.

Forms Manager improvements forms-manager-improvements

Manage mixed form collections and move reusable forms between environments with improvements to folder deletion, downloads, and theme management:

  • Delete folders containing different form types: Delete folders containing both Core Components based Adaptive Forms and Edge Delivery Services forms while preserving shared Edge Delivery Services configurations, so other forms that use those configurations continue to work.
  • Download forms with their fragments: Download an Edge Delivery Services form together with its referenced fragments in the same package, reducing the need to collect dependencies separately when transferring forms.
  • Keep theme references current: Frontend theme redeployment automatically updates the form’s saved theme reference, so Forms Manager continues to show the correct theme rather than reverting to Canvas in the theme picker.

Early Adopter Features in AEM Forms

The following capabilities are available through the AEM Forms Early Adopter program. To request access, email aem-forms-ea@adobe.com from your official address and include your organization ID, program details, and the capabilities you want to use.

Interactive Communication Editor enhancements ic-editor-enhancements

Authors can create reusable document designs, add digital signature fields, and configure accessibility properties in the Interactive Communication (IC) Editor:

  • Add a Sign component: Place a digital signature field in a document and configure which fields are locked after signing, including fields in a named collection. Recipients can sign the generated PDF in Adobe Acrobat, helping teams protect completed document content.
  • Configure accessibility while authoring: Set accessibility roles, screen reader text and precedence, and navigation order, then generate tagged PDF output. These controls help authors prepare communications for readers who use assistive technologies.
  • Create XDP templates: Create and update existing XDP templates directly in the Interactive Communication editor, configure data bindings, and reuse fragments across document designs. Preview generated PDF output while refining the design.

Theme Editor for Core Components based Adaptive Forms theme-editor-core-components

Style Core Components based Adaptive Forms visually in the Theme Editor and preview changes as you work. Customize colors, typography, borders, and spacing, then reuse themes across forms to maintain a consistent appearance.

Dynamic Media images in Adaptive Forms dynamic-media-images-adaptive-forms

Authors can select Dynamic Media assets for the Image component in an Adaptive Form. The component resolves the selected asset reference to its Dynamic Media delivery URL, enabling teams to reuse centrally managed images in forms rather than uploading separate copies.

Custom submit actions in Universal Editor custom-submit-actions-universal-editor

Authors can select and configure custom submit actions for Edge Delivery Services Adaptive Forms in the Universal Editor’s Form Properties interface. Supported action-specific configuration fields appear when the action is selected, enabling teams to connect forms to custom submission processes without switching authoring experiences.

Experience Manager as a Cloud Service Foundation foundation

Experience Manager as a Cloud Service Foundation New Features foundation-new

Vulnerability assessment with AEM Governance Agent vulnerability

The AEM Governance Agent can list known vulnerabilities across one or more AEM instances, including their severity and affected components. You can filter findings by CVE, severity, environment, or component to prioritize remediation. See AEM Governance Agent use cases.

Java 25 for Local Development java25-sdk

The AEM Cloud Service SDK now supports building and running projects with Java 25 for local development and validation. Your AEM license entitles you to download Oracle Java 25 from the Software Distribution portal.

This is the first step toward Java 25 support in AEM as a Cloud Service. In the November release, Cloud Manager environments will let you opt in to Java 25 for the runtime, the project build, or both, so you can take advantage of performance improvements and modern Java features. Use the SDK now to validate your code and prepare for that release.

OpenTelemetry for Application Performance Monitoring (APM) (Limited Availability) otel

Now in Limited Availability (see note below for access), AEM as a Cloud Service supports OpenTelemetry. OTel is an open, industry-standard way to get traces, metrics, and logs together, sent to the APM provider of your choice. Also see advanced custom instrumentation documentation and tutorials.

To get on the list for access, email aemcs-otel-access@adobe.com, describing where you intend to ingest the data.

Server-to-Server OAuth Credentials in AEM Developer Console (JWT Credentials are deprecated) devconsole-oauth

Service Account (JWT) credentials in the AEM Developer Console are deprecated in favor of OAuth Server-to-Server credentials.

You can create OAuth Server-to-Server technical accounts in the AEM Developer Console. Your server-side application exchanges its client ID and client secret for an access token, so there is no JWT to sign and no private key or certificate to renew each year. Although they are deprecated, the JWT-style credentials will be supported for the foreseeable future. For details, see Generating Access Tokens for Server-Side APIs.

Dispatcher Insights and Workflow Inspection Agentic Capabilities in CX Enterprise Coworker capabilities-cx

Two new developer-related agentic capabilities are now generally available in Coworker Chat. Developers and administrators can use them to investigate workflow activity and dispatcher behavior in AEM as a Cloud Service in plain language, without opening the user interface or searching log files by hand.

AEM Workflow Inspection lets you check on workflow activity directly from Coworker. Ask which workflows are running or suspended, get a status summary, see what’s waiting in your workflow inbox, or find out why a workflow failed. You can look up a specific workflow, browse available workflow models, and ask follow-up questions as you troubleshoot.

Example prompts:

  • What workflows are running?
  • Are any running or suspended workflows showing recorded errors?
  • What’s in my workflow inbox?

AEM Dispatcher Insights helps you understand how your Dispatcher and Apache web tier handle requests. Coworker can analyze cache performance, investigate traffic and delivery issues, and review your security configuration. It covers three areas:

  • Caching and performance: includes Dispatcher cache hit ratio insights, query-parameter caching, cache headers and expiration, stale content and invalidation, and slow responses.
  • Traffic and request handling: includes traffic patterns and bots, 4xx and 5xx errors, filter and endpoint routing, multi-site and hostname routing, redirects and vanity URLs, and header forwarding.
  • Security: includes sensitive-path exposure, security headers, permission-sensitive caching, and an overall review of your Dispatcher configuration.

Example prompts:

  • Summarize Dispatcher cache performance for production today and compare it with yesterday.
  • Why is this page still showing old content after publication?
  • Investigate the intermittent 502 and 503 responses in production between 10:00 and 11:00 UTC today.

New Capabilities in Cloud Migration Agent Skill cloud-migration-skill

The AI-Assisted Code Migration skill migrates AEM 6.5 (or earlier) Java-stack projects to AEM as a Cloud Service in the IDE.

The skill now includes these patterns:

  • InputStream usage: java.io.InputStream findings are triaged by risk. Unclosed streams are fixed automatically, while memory, filesystem, and binary-streaming issues are proposed for your review.
  • Oak index conversion (beta): legacy _oak_index definitions convert to Cloud Service-compatible Oak index definitions using Adobe’s Index Converter, are renamed to the Cloud Service versioned index naming (<name>-custom-<n>), and are checked for datatype compatibility.

The skill also adds migration validation (beta), which builds and deploys migrated code to a local AEM as a Cloud Service SDK and checks the migration contract and bundle and component state. It never edits your source code.

Existing supported patterns include Legacy UI (Classic UI, ExtJS, and Coral 2 dialogs to Coral 3), template modernization, Guava cache to Caffeine, Dispatcher configuration conversion, unsupported run mode (URC) detection, Vault package dependency detection, Sling Scheduler, ResourceChangeListener, Replication API, OSGi EventListener and EventHandler, Assets API, HTL lint fixes, and OSGi configuration conversion.

For more information, see AI-Assisted Code Migration to AEM as a Cloud Service.

AEM MCP Server support for Cloud Migration Capabilities aem-mcp-cloud-migration

The AEM MCP Server allows you to configure a single URL in your chat application or coding agent to access a growing set of capabilities. It is also used by the AEM Claude Connector and AEM ChatGPT Plugin.

The AEM MCP Server now supports the Cloud Migration capabilities, used by the Cloud Migration Agent skill described earlier, which migrates AEM 6.5 (or earlier) Java-stack projects to AEM as a Cloud Service in the IDE.

With this addition, the AEM MCP Server has reached parity with the domain-specific MCP servers, which are now considered deprecated. Configure your MCP clients to use the unified AEM MCP Server going forward.

Experience Manager as a Cloud Service Foundation Important Notices foundation-notices

Update your Allowlists with Additional Adobe-managed CDN IP Addresses cdn-ips

If you restrict inbound connections to your systems by IP address, you may have allowlisted the IP addresses of the Adobe-managed CDN. This is common for destinations that receive CDN data directly, such as log ingestion endpoints.

New egress IP addresses are being added on January 11, 2027, at 00:00 UTC. If your allowlist doesn’t include them, valid traffic from the CDN, including log data, may be rejected.

What to do before January 11, 2027:

  1. Update your allowlist to include every IPv4 and IPv6 range in this public IP list. The list already includes the new addresses.
  2. To avoid this in the future, automate the update by monitoring the public IP list API for changes, or by subscribing to this status page for “IP address announcements.”

If you don’t allowlist the CDN’s IP addresses, no action is required.

Mandatory migration from Adobe’s built-in APM integration (New Relic) to OpenTelemetry otel-migration

OpenTelemetry (OTel) is replacing Adobe’s built-in APM integration (New Relic), which will be disabled at the end of November 2026. If your organization is using the built-in New Relic APM integration, see the FAQ for more information.

Deprecation of Domain-specific AEM MCP Server domain-mcp-deprecation

The AEM MCP Server has reached parity with the domain-specific MCP servers, which are now deprecated. Switch your MCP clients to the AEM MCP Server, which provides the same capabilities in a single endpoint.

IMS Authentication Rich Errors ims-auth-rich-errors

To help troubleshoot IMS integrations, imsauth has added support for rich errors.

Instead of returning only an HTTP status code, these errors provide additional context to help diagnose and resolve issues that can block authentication and access.

Winter 2027 Removal of Deprecated Java APIs java-api-deprecation

On March 31, 2027, a set of deprecated Java APIs will be removed, and it is critical to take action in order to achieve security compliance. Applications that have not removed APIs will not receive new features or bug fixes, and application stability and uptime may be negatively affected, and security risk exposure may increase.

See the deprecation article for full details, but for convenience, these APIs are listed below:

Expand to see the Java API deprecations
  • com.day.cq.wcm.commons.util
  • com.day.cq.xss
  • com.github.jknack.handlebars
  • org.apache.jackrabbit.webdav.client.methods
  • org.bson
  • org.apache.tika
  • org.apache.commons.fileupload
  • opennlp.tools
  • com.day.cq.commons.predicate

Preparing for Java 25: AEM Cloud Service Runtime Upgrade Timeline java25-announcement

Java 25 is the next long-term support (LTS) release after Java 21, delivering improvements across performance, developer productivity, and security:

  • Performance — Reduced memory footprint, more efficient garbage collection, and faster JVM warm-up benefit cloud-native deployments.
  • Developer productivity — Cleaner object initialization, more expressive pattern matching, and simplified concurrent task management reduce boilerplate and improve code clarity.
  • Security — Modernized cryptographic key derivation API to simplify common security workflows.

To help organizations plan testing and validation ahead of the necessary Java 25 runtime upgrade, Adobe is providing the following target dates. Any updates to this timeline will be communicated via release notes.

Timeframe
Milestone
October 29, 2026
AEM Cloud Service SDK supports Java 25 runtime. The Java 25 JDK is available for download from the Adobe Software Distribution portal.
November 20, 2026
Customers are encouraged to optionally enable the Java 25 runtime in their Cloud environments to validate behavior. Early adoption maximizes time to surface and resolve issues.
January – April 2027
Adobe will gradually migrate sandboxes and lower environments (RDE, Dev) to the Java 25 runtime. Customers should validate behavior and report unexpected issues, and are encouraged to enable staging and production environments as well. A temporary rollback to Java 21 is available while resolving any problems.
May 2027
All environment runtimes (including staging and production) migrate to Java 25. Java 21 runtime is decommissioned. The AEM Cloud Service SDK will no longer support Java 21.

AEM Cloud Service continues to support compiling customer code with Java 11, Java 17, and Java 21. However, Adobe recommends building with Java 25 (once available in AEM) to take full advantage of the latest language features and performance improvements.

Experience Manager as a Cloud Service Foundation Early Adopter Features foundation-early-adopter

CDN Log Forwarding to Amazon S3, Dynatrace, and New Relic (Beta Program) cdn-logforwarding

While logs can be downloaded from Cloud Manager, many organizations prefer to stream them to a logging destination of their choice. AEM supports forwarding AEM logs (including Apache/Dispatcher) and CDN logs to various destinations.

You can now forward CDN logs to Amazon S3, Dynatrace, and New Relic. Log forwarding is configured in a self-serve manner and deployed using the Cloud Manager config pipeline. Please email aemcs-logforwarding-beta@adobe.com to join the beta program, and learn more in the Log Forwarding documentation.

mTLS Authentication for Log Forwarding (Beta Program) mtls-log-forwarding-beta

Log Forwarding now supports mutual TLS (mTLS) client certificate authentication for Splunk, Elasticsearch/OpenSearch, and HTTPS destinations, for both AEM logs (including Apache/Dispatcher) and CDN logs. AEM as a Cloud Service presents a client certificate when it connects to your logging destination, so the destination can verify that the logs come from your environment.

mTLS for Log Forwarding is in beta. To join the Beta Program, email aemcs-logforwarding-beta@adobe.com with your program ID and environment IDs. Learn more in the log forwarding documentation.

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.

CX Enterprise Coworker: Developer-Focused Capabilities (Beta Program) coworker-ai-troubleshooting-beta

Today for developers, Coworker supports AI prompts to drive Cloud Manager. We’re further expanding agentic AI support for developer use cases — troubleshooting, insights, and productivity — in areas including:

  • CDN (e.g., Did my site experience any traffic spikes?, What’s my cache hit ratio?)
  • Replication (e.g., Why is my replication queue blocked?)
  • Code modernization (e.g., Propose a patch to replace deprecated APIs)

To join the Beta Program, email aem-devagent@adobe.com describing your interest.

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
experience-manager-cloud-service-help-main-toc