AEM as a Cloud Service 2026.10.0 went out on 29 October 2026, and the next feature release, 2026.11.0, is planned for 19 November 2026. Most of what 2026.10.0 adds is optional. The part that can bite is the set of platform notices: CDN egress IP allowlists, the move from built-in New Relic APM to OpenTelemetry, and deprecated Java APIs.
That makes this a good week for a short readiness pass. You don't need to adopt anything new. You do need to know which notices touch your programs before another release lands on top of them.
Key takeaways
- The notes were last updated on 16 November 2026, and 2026.11.0 is planned for 19 November 2026. Use the gap to read the notices, not to chase new features.
- Three platform notices deserve an owner each: CDN egress IP allowlists, New Relic APM to OpenTelemetry, and deprecated Java APIs.
- Java 25 support in the Cloud Service SDK is stated for local development. Test your build locally and don't assume wider changes.
- Multi-caption and multi-audio tracks for video in Dynamic Media with OpenAPI capabilities are a practical gain for teams that localise video.
- The Composite data type is a Sites prerelease, and the agent and migration items are beta or program-based. Pilot them away from production.
- A partner is most useful for the monitoring change and for migration validation, and least needed for reading notices and bumping a local JDK.
What actually changed in 2026.10.0, and what you can skip
The release overview groups the release into four themes: more flexible content and media experiences, AI-assisted governance and troubleshooting, expanded developer and migration tooling, and platform changes to prepare for. Only the last theme is a deadline-shaped item for most teams. The other three are menus.
On the content side, the Sites prerelease adds a Composite data type for Content Fragment models. It groups related fields and repeats them as a list inside one fragment. According to the notes, composite content is stored in the fragment itself, so GraphQL and the OpenAPIs return it in a single response without resolving references. In Assets, the highlights include multilingual video captions and audio tracks, branded video playback, and a GIF-based countdown timer for Dynamic Media email templates.
On the agent side, the AEM Governance Agent can help prioritize vulnerability findings. New capabilities in CX Enterprise Coworker let developers inspect workflows and investigate Dispatcher behavior using natural-language prompts. The Cloud Migration Agent skill adds migration patterns and beta validation, and the unified AEM MCP Server now supports Cloud Migration capabilities.
If you run a stable, single-region marketing site with no video and no migration under way, you can reasonably skip most of that list. If you run video-heavy campaigns across languages, or you are mid-migration from an older AEM setup, a few items are directly relevant. The next sections sort them by how much attention they deserve.
The three platform notices to read this week
The overview tells readers to review notices on CDN egress IP allowlists, the transition from built-in New Relic APM to OpenTelemetry, and deprecated Java APIs. The summary doesn't spell out the mechanics, so the full text of each notice in Adobe's documentation is where the detail lives. What a team can do now is decide who owns reading each one.
The egress IP notice matters to anyone whose security or network setup depends on IP filtering somewhere in the path that involves the CDN. If a partner API, a firewall rule or a customer's network policy names specific addresses, someone has to confirm whether the notice changes that list. This is usually a security or infrastructure owner, not a developer.
The New Relic to OpenTelemetry notice matters to anyone who looks at application performance data from the built-in tooling. Teams that built dashboards or alerts around it will need a plan for where that data comes from next. That's a monitoring decision with real cost in dashboards, alert thresholds and on-call habits.
The deprecated Java APIs notice is the one developers should read line by line. Deprecation is a warning period, not an outage, but warnings that nobody triages tend to become build failures later. A quick search of your custom code for the listed APIs tells you whether the notice is a non-event or a backlog item.
| Notice in the 2026.10.0 notes | Who should own it | First action |
|---|---|---|
| CDN egress IP allowlists | Security or infrastructure lead | Read the notice, list every system that filters by source IP, confirm whether any is affected |
| Built-in New Relic APM to OpenTelemetry | Platform or SRE owner | Inventory dashboards and alerts that depend on the current data, read the notice for what replaces them |
| Deprecated Java APIs | Lead developer | Search custom code for the listed APIs, log findings as backlog items with a size estimate |
| Java 25 in the SDK | Developers | Try the local SDK on Java 25 in a branch, record any build or test failures |
What Java 25 support in the SDK means for your build
The notes say the AEM Cloud Service SDK supports Java 25 for local development. That sentence is narrower than it may sound. It says nothing in the summary about changing what runs in your cloud environments, so don't treat it as a mandate to rewrite your pipeline.
The practical value is for developers. If your laptops or build agents already run a newer JDK for other projects, you no longer have to juggle a separate Java version just for AEM work. For teams that have been pinning an older JDK purely for the SDK, that's a small quality-of-life improvement.
A sensible way to test it:
- Create a branch and install the SDK version that matches 2026.10.0.
- Switch the local JDK to 25 and run a clean build of your full project, not just one module.
- Run your unit and integration tests, and start the local author and publish instances.
- Record every warning, especially anything that mentions deprecated or removed APIs, and compare it against the deprecated Java APIs notice.
- Only after that, decide whether to change developer onboarding docs.
Don't change your Cloud Manager build settings on the strength of this one line. Confirm the supported configuration in Adobe's documentation first, and make the change in a separate, reviewed pull request.
Multilingual video: captions and audio tracks
The Assets section describes Dynamic Media with OpenAPI capabilities supporting multiple captions and multiple audio tracks for video assets. Authors can associate several language-specific caption and audio tracks with a single primary video and manage them from one interface. The notes frame this as a way to deliver localised and accessible video experiences and to support regional accessibility requirements.
The before-and-after is easy to picture. A team with one product video in five markets often ends up with five near-identical assets, each with its own metadata, its own approvals and its own place in a campaign. With tracks attached to one primary video, the team has one asset to govern and several language options inside it. Whether that works for you depends on how your players and pages consume the video, which the summary doesn't cover.
There's also an AI-generated video captions item, described as using artificial intelligence to generate captions automatically for video content. The text available here is cut off after that, so read Adobe's page for the exact scope and availability before promising it to anyone. Automatic captions are a starting point. For anything regulated, public-facing or legally sensitive, a human review step should stay in the workflow.
Who should act: content operations and the accessibility owner. Pick one real video, add a second language caption track and a second audio track in a non-production environment, and watch how it behaves on a test page. If your site team has custom players, involve them early.
Agents, governance and migration tooling: pilot, don't plan around
The notes mention a run of agent-related items: the AEM Governance Agent for prioritizing vulnerability findings, CX Enterprise Coworker for inspecting workflows and investigating Dispatcher behavior, and the Cloud Migration Agent skill with beta validation. They also point to an Agents in AEM page for teams that want to explore agentic capabilities across production, governance, optimization, discovery and development.
The tone of the beta section matters. Adobe says beta releases may contain defects, are provided as is, and that features and APIs in beta can change without notice. Treat that as written. A beta validation step in a migration is useful as a second opinion. It isn't a replacement for your own acceptance tests.
Here's a position worth taking: the Dispatcher troubleshooting capability is the one most teams should try first, in a lower environment. Dispatcher configuration problems are common, they eat engineering hours, and a natural-language way to investigate them is easy to evaluate against a problem you already understand. The governance agent is also a reasonable pilot for security teams, but its output should feed your existing triage process rather than replace it. For anything that touches vulnerabilities, confirm fixed versions and remediation guidance against Adobe's official security bulletins.
What to avoid: giving any of these tools write access to production on day one, or putting them into a migration plan with a fixed date. Beta programs are for learning and giving feedback.
Composite data type for Content Fragments: a prerelease to evaluate
The Composite data type sits under Sites prerelease. That wording means it's early. For content architects, the appeal is clear from the description: grouped, repeatable fields stored inside the fragment, delivered through GraphQL and the OpenAPIs in one response, with no reference resolution.
The trade-off to think about is modelling. Today, teams often handle repeating structures, like a list of feature blocks or pricing tiers, by creating separate fragments and referencing them. That keeps items reusable but adds lookups. A composite keeps the group inside one fragment, which suits data that belongs to only one parent. If the same group will appear in many places, a reference is still the better fit.
A light evaluation looks like this:
- Pick one existing model that uses a reference list for data that is never reused elsewhere.
- Rebuild it as a test model with a composite in a non-production environment.
- Compare the GraphQL query before and after, and the authoring experience for an editor.
- Write down what you would need to migrate existing content, then stop. Don't migrate anything while the feature is prerelease.
How to roll this out and measure it
A small plan beats a big one. Split the work into a two-week readiness sprint and a longer evaluation backlog.
In the sprint, assign the three platform notices, run the Java 25 local build test, and check whether any of your integrations rely on IP filtering. Success looks like a short written note per notice stating either that it doesn't affect you or what the fix is, with an owner and a date.
For the evaluation backlog, list the optional items you care about: a multilingual video pilot, a Dispatcher troubleshooting trial, a composite model experiment. Give each a single question to answer, such as whether editors can manage a second caption track without help.
Measure with things you already track. For monitoring, count the dashboards and alerts that need rework. For the Java check, count warnings and build failures on the branch. For video, track the time an editor needs to add a language track compared with creating a new asset today. Don't invent targets you have no baseline for. Directional comparisons against your own current process are enough.
Where a partner helps and where you don't need one
You don't need outside help to read three notices, test a local JDK or try a caption track on one video. Those are a few days of work for an internal team that already knows its own setup.
A partner earns its fee on the harder parts. Re-establishing performance visibility after the monitoring change, especially across several programs, takes someone who has done it before. Migration planning, where the Cloud Migration Agent skill and the unified AEM MCP Server might feed into a larger move, benefits from people who have seen how migrations fail. And if you're comparing firms for this kind of work, the AEM partners directory and the side-by-side comparison tool are a faster start than cold outreach.
When you do brief someone, be specific. State which environments you run, which notices apply, what you want validated and what you want left alone. The AEM RFP template gives you a structure for that, and it keeps proposals comparable. If you are still deciding what kind of help you need, the advisor can narrow it down.
What not to do before 2026.11.0
Don't skip the notices because the headline features are more fun. Don't change production build or monitoring configuration based on a one-line summary. Don't promise AI-generated captions or agent-based migration validation to stakeholders until you've read Adobe's own pages and tried them. And don't let a beta or prerelease feature become a hidden dependency in a project plan.
The release notes will keep changing, and 2026.11.0 will bring its own list. A habit of reading the notices first, assigning an owner, and piloting the optional items in a sandbox will serve you better than any single release.
Sources
- Adobe Experience League: Current Release Notes for Adobe Experience Manager as a Cloud Service — Release dates, release overview, beta programs, Sites prerelease and Assets features for 2026.10.0
Frequently Asked Questions
When is the next AEM as a Cloud Service feature release after 2026.10.0?
The release notes say the 2026.10.0 feature release came out on 29 October 2026. The next feature release, 2026.11.0, is planned for 19 November 2026. Check the Experience Manager Releases Roadmap for activation timing.
Does AEM Cloud Service 2026.10.0 support Java 25?
The notes state that the AEM Cloud Service SDK supports Java 25 for local development. They do not say anything beyond that in the summary, so confirm the exact runtime guidance for your environments in Adobe's documentation before changing build settings.
What is happening to New Relic APM in AEM Cloud Service?
The release overview lists a notice about the transition from the built-in New Relic APM to OpenTelemetry. If your team relies on the built-in New Relic view for performance monitoring, read that notice in full and plan how you will get equivalent visibility.
Can I use the Composite data type for Content Fragments in production?
The notes list it under Sites prerelease, which means it is not generally available. Treat it as something to evaluate in a non-production setup and expect details to change.
What are the AEM agents mentioned in the 2026.10.0 notes?
The notes mention the AEM Governance Agent, which can help prioritize vulnerability findings, and capabilities in CX Enterprise Coworker for inspecting workflows and investigating Dispatcher behavior with natural-language prompts. They also mention a Cloud Migration Agent skill with beta validation. Access to agentic capabilities is explained on Adobe's own page.