{"id":7887,"date":"2026-11-11T20:38:54","date_gmt":"2026-11-11T20:38:54","guid":{"rendered":"https:\/\/onwardpath.com\/intelligence\/?p=7887"},"modified":"2026-11-11T21:25:50","modified_gmt":"2026-11-11T21:25:50","slug":"aem-as-a-cloud-service-2026-10-0-for-developers-the-dates-that-matter-and-two-timelines-that-moved","status":"publish","type":"post","link":"https:\/\/onwardpath.com\/intelligence\/aem-as-a-cloud-service-2026-10-0-for-developers-the-dates-that-matter-and-two-timelines-that-moved\/","title":{"rendered":"AEM as a Cloud Service 2026.10.0 for Developers: The Dates That Matter, and Two Timelines That Moved"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">AEM as a Cloud Service 2026.10.0 was released on October 29, 2026, and 2026.11.0 is planned for November 19. Most release-note coverage walks through new features. This post does something narrower: it pulls out the <strong>dated<\/strong> items that matter to developers and operators, checks them against Adobe\u2019s primary pages, and says plainly where the picture changed since our earlier posts. Two timelines moved, and one of them is only weeks away.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>What Changed Since Our Earlier Posts<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">If you read our earlier posts on Java 25 and the deprecated-API deadline, on the AEM MCP Server, or on code migration, here is what is now different according to Adobe\u2019s current notes:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><td><strong>Topic<\/strong><\/td><td><strong>Our earlier posts said<\/strong><\/td><td><strong>Adobe\u2019s current notes say<\/strong><\/td><\/tr><tr><td><strong>Java 25: lower environments (RDE, Dev)<\/strong><\/td><td>February to May 2027<\/td><td>January to April 2027 (now also &#8220;sandboxes and lower environments&#8221;)<\/td><\/tr><tr><td><strong>Java 25: all environments; Java 21 runtime<\/strong><\/td><td>June 2027<\/td><td>May 2027<\/td><\/tr><tr><td><strong>Java 25 SDK support<\/strong><\/td><td>Mid-October 2026 (planned; we could not confirm it shipped)<\/td><td>October 29, 2026 is listed as the SDK milestone, and a feature item says the SDK now supports building and running projects with Java 25 for local development<\/td><\/tr><tr><td><strong>Deprecated Java API notice<\/strong><\/td><td>Critical updates stop September 28, 2026<\/td><td>The current notes we read no longer show that notice. They show a &#8220;Winter 2027&#8221; removal on March 31, 2027 instead. We found no statement of what happened to the earlier notice.<\/td><\/tr><tr><td><strong>OpenTelemetry status label<\/strong><\/td><td>Beta (as its doc read at the time)<\/td><td>Limited Availability, in both the release notes heading and the feature doc (updated October 20, 2026)<\/td><\/tr><tr><td><strong>Cloud Migration and the AEM MCP Server<\/strong><\/td><td>The unified server does not cover Cloud Migration<\/td><td>The notes say the AEM MCP Server &#8220;now supports the Cloud Migration capabilities,&#8221; and that the domain-specific MCP servers are deprecated<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Sources and How Current They Are<\/strong><\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><td><strong>Source<\/strong><\/td><td><strong>Last updated<\/strong><\/td><td><strong>Notes<\/strong><\/td><\/tr><tr><td><strong>Current release notes for AEM as a Cloud Service<\/strong><\/td><td>November 4, 2026<\/td><td>2026.10.0 is the current feature release (October 29, 2026). 2026.11.0 is &#8220;planned for November 19, 2026.&#8221; Re-checked on November 12, 2026: not yet released, and the dates in this post were unchanged.<\/td><\/tr><tr><td><strong>Deprecated and Removed Features and APIs<\/strong><\/td><td>November 3, 2026<\/td><td>A long page. Part of it reached us only as a summary, so details below are limited to what we could read verbatim.<\/td><\/tr><tr><td><strong>OpenTelemetry for AEM (feature doc)<\/strong><\/td><td>October 20, 2026<\/td><td>States &#8220;This feature is in Limited Availability.&#8221;<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Adobe says: &#8220;Any updates to this timeline will be communicated via release notes.&#8221; Dates in this post can change.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>The Dates at a Glance<\/strong><\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><td><strong>When<\/strong><\/td><td><strong>What<\/strong><\/td><td><strong>Notes<\/strong><\/td><\/tr><tr><td><strong>End of November 2026<\/strong><\/td><td>Adobe\u2019s built-in APM integration (New Relic) is disabled; OpenTelemetry replaces it<\/td><td>OpenTelemetry is Limited Availability and needs an access request<\/td><\/tr><tr><td><strong>November 19, 2026<\/strong><\/td><td>2026.11.0 planned. Per the notes, Cloud Manager environments will let you opt in to Java 25 for the runtime, the project build, or both<\/td><td>Planned date, not yet released as of November 12<\/td><\/tr><tr><td><strong>November 20, 2026<\/strong><\/td><td>Customers encouraged to optionally enable the Java 25 runtime in Cloud environments<\/td><td>Adobe does not link this date to the November release; confirm<\/td><\/tr><tr><td><strong>January 11, 2027, 00:00 UTC<\/strong><\/td><td>New egress IP addresses added to the Adobe-managed CDN<\/td><td>Only matters if you allowlist CDN IP addresses<\/td><\/tr><tr><td><strong>January to April 2027<\/strong><\/td><td>Adobe migrates sandboxes and lower environments (RDE, Dev) to the Java 25 runtime<\/td><td>Temporary rollback to Java 21 is available<\/td><\/tr><tr><td><strong>March 31, 2027<\/strong><\/td><td>&#8220;Winter 2027&#8221; removal of a set of deprecated Java APIs<\/td><td>Nine packages in the notice; see the package-name caveat below<\/td><\/tr><tr><td><strong>May 2027<\/strong><\/td><td>All environment runtimes (including staging and production) migrate to Java 25; Java 21 runtime decommissioned; SDK drops Java 21<\/td><td>One month earlier than the previous notes<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<figure class=\"wp-block-image size-full is-resized\"><img decoding=\"async\" width=\"776\" height=\"477\" loading=\"lazy\" src=\"https:\/\/i0.wp.com\/onwardpath.com\/intelligence\/wp-content\/uploads\/2026\/11\/image.jpg?fit=776%2C477&amp;ssl=1\" alt=\"\" class=\"wp-image-7889\" style=\"aspect-ratio:1.62565445026178;width:621px;height:auto\" srcset=\"https:\/\/i0.wp.com\/onwardpath.com\/intelligence\/wp-content\/uploads\/2026\/11\/image.jpg?w=776&amp;ssl=1 776w, https:\/\/i0.wp.com\/onwardpath.com\/intelligence\/wp-content\/uploads\/2026\/11\/image.jpg?resize=300%2C184&amp;ssl=1 300w, https:\/\/i0.wp.com\/onwardpath.com\/intelligence\/wp-content\/uploads\/2026\/11\/image.jpg?resize=768%2C472&amp;ssl=1 768w\" sizes=\"auto, (max-width: 776px) 100vw, 776px\" \/><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\"><em>Dates from Adobe\u2019s current release notes (page updated November 4, 2026).<\/em><\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>1. The Built-in New Relic APM Integration Is Going Away (End of November 2026)<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The release notes carry a notice titled &#8220;Mandatory migration from Adobe\u2019s built-in APM integration (New Relic) to OpenTelemetry&#8221;:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><em>&#8220;OpenTelemetry (OTel) is replacing Adobe\u2019s built-in APM integration (New Relic), which will be disabled at the end of November 2026.&#8221;<\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you use that built-in integration, this is the item with the nearest date. Adobe\u2019s feature doc for OpenTelemetry, last updated October 20, 2026, describes the destination:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><td><strong>Topic<\/strong><\/td><td><strong>What the OpenTelemetry feature doc says<\/strong><\/td><\/tr><tr><td><strong>Status and access<\/strong><\/td><td>&#8220;This feature is in Limited Availability.&#8221; Access is requested from Adobe (the doc says to include your Cloud Manager program and environment IDs), and Adobe enables it per environment.<\/td><\/tr><tr><td><strong>Where it is not available<\/strong><\/td><td>HIPAA-scoped environments, Rapid Development Environments (RDE), and sandboxes.<\/td><\/tr><tr><td><strong>Signals and environments<\/strong><\/td><td>Traces, metrics, and logs (logs are optional, WARN level and above; the ability to adjust the level is &#8220;in development&#8221;). Production, stage, and development environments.<\/td><\/tr><tr><td><strong>How it is configured<\/strong><\/td><td>Through the Cloud Manager Config Pipeline, with a configuration file and a secret environment variable. The doc says changing environment variables needs the Deployment Manager role. Follow the doc for the current file contents.<\/td><\/tr><tr><td><strong>Prerequisites<\/strong><\/td><td>Your APM provider must accept OTLP\/HTTPS and be reachable over HTTPS. Private endpoints or a stable source IP need Advanced Networking with dedicated egress. Dynatrace OneAgent must be removed first if installed.<\/td><\/tr><tr><td><strong>Limits<\/strong><\/td><td>Telemetry goes only to your own APM provider (&#8220;Adobe does not surface this data back to you&#8221;). OpenTelemetry cannot run alongside another APM agent on the same environment. Sending both OpenTelemetry logs and Log Forwarding to the same destination produces duplicate messages.<\/td><\/tr><tr><td><strong>Moving off New Relic<\/strong><\/td><td>Once Adobe enables OpenTelemetry for an environment, New Relic no longer receives data from it. The doc says you can move back until the end of November 2026, and that Adobe will then move to OpenTelemetry &#8220;as its permanent observability solution.&#8221; It gives no specific shutdown date beyond the release notes\u2019 &#8220;end of November 2026.&#8221;<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Our reading (not Adobe guidance)<\/strong><\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">The mandatory move points at a feature labeled <strong>Limited Availability<\/strong>, which requires an access request and is not available for HIPAA-scoped environments, RDE, or sandboxes. Those are fair questions to put to Adobe now, not at the end of the month.<\/li>\n\n\n\n<li class=\"\">Ask Adobe how access is being sequenced before the end of November, whether your environment types are covered, and what exactly happens to an environment that has not moved. The pages we read say the built-in integration is disabled; they do not describe anything further.<\/li>\n\n\n\n<li class=\"\">Because OpenTelemetry cannot run alongside another APM agent, check whether you have anything else installed (the doc names Dynatrace OneAgent) before you request it.<\/li>\n\n\n\n<li class=\"\">The doc says you can move back until the end of November 2026. If you try it, treat that as a short evaluation window.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>2. Java 25: The Timeline Moved Earlier<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Adobe\u2019s &#8220;Preparing for Java 25&#8221; timeline, as of the notes updated November 4, 2026:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><td><strong>When<\/strong><\/td><td><strong>What Adobe says<\/strong><\/td><\/tr><tr><td><strong>October 29, 2026<\/strong><\/td><td>&#8220;AEM Cloud Service SDK supports Java 25 runtime.&#8221; The Java 25 JDK is available from the Adobe Software Distribution portal.<\/td><\/tr><tr><td><strong>November 20, 2026<\/strong><\/td><td>Customers are encouraged to optionally enable the Java 25 runtime in their Cloud environments to validate behavior; early adoption &#8220;maximizes time to surface and resolve issues.&#8221;<\/td><\/tr><tr><td><strong>January to April 2027<\/strong><\/td><td>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 as well. &#8220;A temporary rollback to Java 21 is available while resolving any problems.&#8221;<\/td><\/tr><tr><td><strong>May 2027<\/strong><\/td><td>&#8220;All environment runtimes (including staging and production) migrate to Java 25.&#8221; &#8220;Java 21 runtime is decommissioned.&#8221; &#8220;The AEM Cloud Service SDK will no longer support Java 21.&#8221;<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Things worth noting<\/strong><\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\"><strong>Opt-in arrives with the November release.<\/strong> A feature item says: &#8220;In the November release, Cloud Manager environments will let you opt in to Java 25 for the runtime, the project build, or both.&#8221; 2026.11.0 is planned for November 19. The separate November 20 row says customers are encouraged to optionally enable the runtime; Adobe does not link the two dates, so confirm what is available to you and when.<\/li>\n\n\n\n<li class=\"\"><strong>Compile target and runtime are separate.<\/strong> Adobe says it &#8220;continues to support compiling customer code with Java 11, Java 17, and Java 21,&#8221; and recommends building with Java 25 once it is available in AEM.<\/li>\n\n\n\n<li class=\"\"><strong>Local validation is available now.<\/strong> The SDK &#8220;now supports building and running projects with Java 25 for local development and validation,&#8221; and the notes encourage using it to prepare. The notes also say your AEM license entitles you to download Oracle Java 25 from the Software Distribution portal.<\/li>\n\n\n\n<li class=\"\"><strong>Rollback:<\/strong> the temporary rollback to Java 21 is mentioned only in the January to April row, and the notes do not say how long it stays available.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>3. &#8220;Winter 2027&#8221; Removal of Deprecated Java APIs (March 31, 2027)<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><em>&#8220;On March 31, 2027, a set of deprecated Java APIs will be removed.&#8221;<\/em><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">On the consequences, the notice says applications that have not removed the APIs &#8220;will not receive new features or bug fixes, and application stability and uptime may be negatively affected, and security risk exposure may increase,&#8221; and that &#8220;it is critical to take action in order to achieve security compliance.&#8221;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The notice lists nine packages. We compared them with Adobe\u2019s Deprecated and Removed Features page, which gives a hint for some of them:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><td><strong>Package in the release-notes notice<\/strong><\/td><td><strong>Hint on the Deprecated and Removed Features page, where one is given<\/strong><\/td><\/tr><tr><td><strong>com.day.cq.wcm.commons.util<\/strong><\/td><td>The deprecated-features page lists com.day.cq.wcm.commons.utils (with an &#8220;s&#8221;) and says to use com.day.cq.wcm.commons instead. The names differ by one letter between the two pages \u2014 check which one your code uses.<\/td><\/tr><tr><td><strong>com.day.cq.xss<\/strong><\/td><td>Use org.apache.sling.xss instead.<\/td><\/tr><tr><td><strong>com.github.jknack.handlebars<\/strong><\/td><td>No comment given.<\/td><\/tr><tr><td><strong>org.apache.jackrabbit.webdav.client.methods<\/strong><\/td><td>No comment given.<\/td><\/tr><tr><td><strong>org.bson<\/strong><\/td><td>No comment given.<\/td><\/tr><tr><td><strong>org.apache.tika<\/strong><\/td><td>No comment given.<\/td><\/tr><tr><td><strong>org.apache.commons.fileupload<\/strong><\/td><td>Use the official Servlet API for handling file uploads instead.<\/td><\/tr><tr><td><strong>opennlp.tools<\/strong><\/td><td>No comment given.<\/td><\/tr><tr><td><strong>com.day.cq.commons.predicate<\/strong><\/td><td>Use com.day.cq.commons.predicates instead.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Two things to check yourself<\/strong><\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\"><strong>The package name differs by one letter between pages.<\/strong> The release notes list com.day.cq.wcm.commons.util; the deprecated-features page lists com.day.cq.wcm.commons.utils. We don\u2019t know which is intended, so check what your code imports.<\/li>\n\n\n\n<li class=\"\"><strong>The deprecated-features page gives two sets of month-level milestones.<\/strong> One box near the top mentions reminders in November 2026, pipelines pausing in December 2026, and pipelines failing in January 2027; the Deprecated APIs section lists a different set of months in 2027. We could not tell which applies to which set of APIs, and the page does not resolve it. Ask Adobe, and until you hear back, we\u2019d plan against the earlier set. That is our caution, not Adobe\u2019s instruction.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The same page also says environments still using deprecated APIs will have the libraries removed from the AEM product injected into their custom project code and will not be subject to Adobe\u2019s standard commitments around performance and availability, and that affected pipelines pause at the Code Quality step (with an override for certain roles) and then fail. It also lists further packages with a later target of December 31, 2027, mostly marked tentative.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>The earlier September 28, 2026 notice:<\/strong> our previous post covered a notice about critical updates stopping on September 28, 2026. The current notes we read no longer show it, and we found no statement of its outcome. If it affected you, ask Adobe for your environment\u2019s status.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>4. New CDN Egress IP Addresses (January 11, 2027)<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><em>&#8220;New egress IP addresses are being added on January 11, 2027, at 00:00 UTC. If your allowlist doesn\u2019t include them, valid traffic from the CDN, including log data, may be rejected.&#8221;<\/em><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">If you restrict inbound traffic by IP, update your allowlist to include every IPv4 and IPv6 range in the public IP list the notice links to. The notice says the list already includes the new addresses.<\/li>\n\n\n\n<li class=\"\">To avoid repeat problems, Adobe suggests automating updates by monitoring that list, or subscribing to the provider\u2019s status page for IP address announcements.<\/li>\n\n\n\n<li class=\"\">&#8220;If you don\u2019t allowlist the CDN\u2019s IP addresses, no action is required.&#8221;<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>5. Other Developer-Facing Items, With Labels as Written<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A selection, not a full list. Where Adobe gives no label, we say so. We have not evaluated any of these.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><td><strong>Item<\/strong><\/td><td><strong>Label as written<\/strong><\/td><td><strong>Our note<\/strong><\/td><\/tr><tr><td><strong>AEM MCP Server support for Cloud Migration Capabilities<\/strong><\/td><td>No label<\/td><td>New in 2026.10.0. Updates what our earlier MCP and migration posts said.<\/td><\/tr><tr><td><strong>Deprecation of the domain-specific AEM MCP servers<\/strong><\/td><td>Important Notice, no label<\/td><td>&#8220;Switch your MCP clients to the AEM MCP Server.&#8221; No removal date given.<\/td><\/tr><tr><td><strong>New capabilities in the Cloud Migration Agent skill<\/strong><\/td><td>No label; two items marked &#8220;(beta)&#8221; in the body<\/td><td>Adds InputStream patterns; Oak index conversion (beta); migration validation (beta).<\/td><\/tr><tr><td><strong>Server-to-Server OAuth credentials in the AEM Developer Console<\/strong><\/td><td>No label; heading notes JWT credentials are deprecated<\/td><td>JWT-style credentials &#8220;will be supported for the foreseeable future&#8221;; no date. The deprecated-features page also lists Adobe Developer Console projects using Service Account (JWT) credentials as &#8220;Removed,&#8221; which is a different thing; check which you use.<\/td><\/tr><tr><td><strong>Vulnerability assessment with the AEM Governance Agent<\/strong><\/td><td>No label<\/td><td>Lists known vulnerabilities by severity and component.<\/td><\/tr><tr><td><strong>Dispatcher Insights and Workflow Inspection agentic capabilities in CX Enterprise Coworker<\/strong><\/td><td>Heading has no label; body says &#8220;now generally available in Coworker Chat&#8221;<\/td><td>Plain-language troubleshooting. We have not evaluated it.<\/td><\/tr><tr><td><strong>CDN log forwarding to Amazon S3, Dynatrace, and New Relic<\/strong><\/td><td>(Beta Program)<\/td><td>Separate from the built-in APM integration being disabled.<\/td><\/tr><tr><td><strong>mTLS authentication for log forwarding<\/strong><\/td><td>(Beta Program)<\/td><td>&nbsp;<\/td><\/tr><tr><td><strong>CAPTCHAs and Bot Category WAF flags at the origin<\/strong><\/td><td>(Beta Program)<\/td><td>&nbsp;<\/td><\/tr><tr><td><strong>Edge Authentication for Edge Delivery Services<\/strong><\/td><td>(Beta Program)<\/td><td>Covered in our earlier Edge Delivery access-control post.<\/td><\/tr><tr><td><strong>CX Enterprise Coworker developer-focused capabilities<\/strong><\/td><td>(Beta Program)<\/td><td>&nbsp;<\/td><\/tr><tr><td><strong>Composite data type for Content Fragments<\/strong><\/td><td>No label; listed in a Sites &#8220;Prerelease&#8221; section<\/td><td>&nbsp;<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>6. Labels That Moved Since 2026.9.0<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Labels are not fixed. Several Assets items that sat under a Limited Availability heading in the 2026.9.0 notes now sit under a General Availability heading in the 2026.10.0 notes. This is section-heading placement only; the item headings themselves carry no label, and we did not verify entitlement or rollout.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><td><strong>Assets item<\/strong><\/td><td><strong>In the 2026.9.0 notes<\/strong><\/td><td><strong>In the 2026.10.0 notes<\/strong><\/td><\/tr><tr><td><strong>Content Hub AI Search<\/strong><\/td><td>Limited Availability section<\/td><td>General Availability Features section<\/td><\/tr><tr><td><strong>Content Hub Smart Collections<\/strong><\/td><td>Limited Availability section<\/td><td>General Availability Features section<\/td><\/tr><tr><td><strong>Content Hub Custom Sorting options<\/strong><\/td><td>Limited Availability section<\/td><td>General Availability Features section<\/td><\/tr><tr><td><strong>AI-generated video captions<\/strong><\/td><td>Limited Availability section<\/td><td>General Availability Features section<\/td><\/tr><tr><td><strong>Multi-caption and multi-audio track support for videos<\/strong><\/td><td>Limited Availability section<\/td><td>General Availability Features section<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>What We\u2019d Do This Month (Our Reading)<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>This is our interpretation, not Adobe guidance, and we have not run these steps on a customer project.<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\"><strong>Find out whether you use the built-in New Relic APM integration.<\/strong> If so, this is the nearest deadline: contact Adobe now about OpenTelemetry access and environment coverage.<\/li>\n\n\n\n<li class=\"\"><strong>If you allowlist CDN IPs, schedule the update before January 11, 2027.<\/strong> If you don\u2019t, there is nothing to do.<\/li>\n\n\n\n<li class=\"\"><strong>Run your deprecated-API analysis against the latest SDK<\/strong> and look for the nine packages, keeping the package-name caveat in mind. Adobe\u2019s tutorial describes the AEM Analyser Maven Plugin for this.<\/li>\n\n\n\n<li class=\"\"><strong>Start validating on Java 25 locally with the SDK,<\/strong> and look for the Cloud Manager opt-in after the November release before deciding what to enable where.<\/li>\n\n\n\n<li class=\"\"><strong>If you use the domain-specific MCP servers,<\/strong> plan to move your clients to the unified AEM MCP Server. Adobe gives no removal date.<\/li>\n\n\n\n<li class=\"\"><strong>Check which kind of JWT credential you use,<\/strong> and note that Adobe says AEM Developer Console JWT credentials are supported for the foreseeable future.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>What We Haven\u2019t Verified<\/strong><\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">We read Adobe\u2019s pages on November 9, 2026 and re-checked the release notes on November 12, 2026. We have not implemented any of this on a customer project.<\/li>\n\n\n\n<li class=\"\">We read the pages through a summarizing tool. The Deprecated and Removed Features page is long, and part of it reached us only as a summary, so please check that page directly, especially the milestone months and package lists.<\/li>\n\n\n\n<li class=\"\">We did not verify how Adobe is sequencing OpenTelemetry access before the end of November, what happens to environments that have not migrated, or how long the Java 21 rollback lasts.<\/li>\n\n\n\n<li class=\"\">We did not verify the status of the earlier September 28, 2026 notice.<\/li>\n\n\n\n<li class=\"\">We did not evaluate any of the items in the &#8220;other developer-facing items&#8221; table, or verify entitlement for the Assets items.<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Checklist<\/strong><\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"\">Confirm whether you use the built-in New Relic APM integration, and contact Adobe about OpenTelemetry access if so<\/li>\n\n\n\n<li class=\"\">Check that your environment types are supported by OpenTelemetry (not HIPAA-scoped, RDE, or sandbox)<\/li>\n\n\n\n<li class=\"\">Check for another APM agent (for example Dynatrace OneAgent) that would conflict with OpenTelemetry<\/li>\n\n\n\n<li class=\"\">Update CDN IP allowlists before January 11, 2027, if you use them<\/li>\n\n\n\n<li class=\"\">Run the deprecated-API analysis and look for the nine listed packages; confirm the exact package name for your code<\/li>\n\n\n\n<li class=\"\">Ask Adobe which milestone months apply to the March 31, 2027 removal<\/li>\n\n\n\n<li class=\"\">Validate your build on Java 25 locally, and check Cloud Manager after the November release for the opt-in<\/li>\n\n\n\n<li class=\"\">Move MCP clients to the unified AEM MCP Server if you use the domain-specific ones<\/li>\n\n\n\n<li class=\"\">Review which JWT credentials you use in the AEM Developer Console<\/li>\n\n\n\n<li class=\"\">Re-check the release notes before each date, since Adobe says changes will appear there<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\"><strong>Final Thoughts<\/strong><\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The useful thing about reading release notes closely is how often the dates move. In the span of a few weeks, the Java 25 runtime schedule shifted by a month, the OpenTelemetry label changed, and a deprecation notice we covered stopped appearing. None of that is alarming, but it is a good reason to treat any date in a blog post, including ours, as a starting point for checking the primary page. If you do one thing this month, make it the New Relic question, since that date is the closest.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>AEM as a Cloud Service 2026.10.0 for Developers: The Dates That Matter, and Two Timelines That Moved<\/p>\n","protected":false},"author":7,"featured_media":7893,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"nf_dc_page":"","site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"advanced_seo_description":"","jetpack_seo_html_title":"","jetpack_seo_noindex":false,"jetpack_seo_schema_type":"","_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_hide_featured_image":false,"_jetpack_featured_image_duplicate_dismissed":0,"_jetpack_memberships_contains_paid_content":false,"nfd_image_url":"","nfd_onboarding_generated":"","footnotes":""},"categories":[138,227,128,37],"tags":[137],"class_list":["post-7887","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-adobe-experience-manager","category-aem","category-talent-solutions","category-technology-blog","tag-adobe-experience-manager"],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"https:\/\/i0.wp.com\/onwardpath.com\/intelligence\/wp-content\/uploads\/2026\/11\/macbook-neo-stock-5120x3202-25821-scaled.jpg?fit=2560%2C1601&ssl=1","_links":{"self":[{"href":"https:\/\/onwardpath.com\/intelligence\/wp-json\/wp\/v2\/posts\/7887","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/onwardpath.com\/intelligence\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/onwardpath.com\/intelligence\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/onwardpath.com\/intelligence\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/onwardpath.com\/intelligence\/wp-json\/wp\/v2\/comments?post=7887"}],"version-history":[{"count":4,"href":"https:\/\/onwardpath.com\/intelligence\/wp-json\/wp\/v2\/posts\/7887\/revisions"}],"predecessor-version":[{"id":7897,"href":"https:\/\/onwardpath.com\/intelligence\/wp-json\/wp\/v2\/posts\/7887\/revisions\/7897"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/onwardpath.com\/intelligence\/wp-json\/wp\/v2\/media\/7893"}],"wp:attachment":[{"href":"https:\/\/onwardpath.com\/intelligence\/wp-json\/wp\/v2\/media?parent=7887"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/onwardpath.com\/intelligence\/wp-json\/wp\/v2\/categories?post=7887"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/onwardpath.com\/intelligence\/wp-json\/wp\/v2\/tags?post=7887"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}