AEM Cloud Service Ops Checklist Before Year-End: New Relic APM Shutdown, OpenTelemetry, New CDN IPs, and JWT Credentials

Question

The 2026.10.0 release notes include several dated operational changes, and the first one is three weeks away. Here they are in deadline order, with Adobe’s status labels where the page gives one.

1. Built-in New Relic APM integration: disabled end of November 2026

Adobe’s release notes announce a mandatory migration from the built-in APM integration (New Relic) to OpenTelemetry. The built-in integration “will be disabled at the end of November 2026”, and Adobe’s deprecation list gives November 30, 2026. If you use the New Relic integration today for dashboards or alerts, plan the move now.

What the docs say about OpenTelemetry:

Status: Limited Availability. You request access by emailing aemcs-apm-beta@adobe.com, and Adobe enables it for your environments.
The two integrations can’t run at the same time. Once OpenTelemetry is enabled on an environment, the built-in one stops sending data.
You can move back until the end of November 2026.
It works with any APM platform exposing an OTLP/HTTPS endpoint, with New Relic, Grafana Cloud, Splunk Observability Cloud and ServiceNow Cloud Observability named as examples.
Logs: if you send logs over OpenTelemetry and also use legacy log forwarding to the same destination, you get duplicates.
I couldn’t confirm what happens after the deadline beyond the built-in integration being disabled, so don’t assume it’s reversible afterward.

Practical steps: request access early, rebuild dashboards and alerts against OpenTelemetry data on a non-production environment first, and compare signal quality before cutover. Whether OpenTelemetry data matches your old New Relic dashboards one-to-one is something to validate, not assume.

2. Server-to-Server OAuth in the Developer Console (JWT credentials deprecated)

The notes list Server-to-Server OAuth credentials in the AEM Developer Console and state that JWT credentials are deprecated. The notes give no status label for this item. If integrations still authenticate with JWT service credentials, inventory them and check the deprecation page for dates.

3. New Adobe-managed CDN IP addresses: January 11, 2027

The notes say additional egress IPs are added on January 11, 2027 at 00:00 UTC. If downstream systems allowlist Adobe’s CDN IPs (origins, partner APIs, firewalls), update those rules before then. This is a quiet outage risk because nothing in your AEM code changes.

4. Beta Program items worth knowing about (not production features)

Listed under Foundation Early Adopter Features, each labeled (Beta Program):

CDN log forwarding to Amazon S3, Dynatrace and New Relic
mTLS authentication for log forwarding
CAPTCHAs and bot-category WAF flags at the origin
Edge Authentication for Edge Delivery Services
CX Enterprise Coworker: developer-focused capabilities

Pilot these in a lower environment if they match a need, and keep them out of delivery commitments until they leave beta.

5. Developer agent capabilities labeled generally available

The notes describe two CX Enterprise Coworker capabilities, Dispatcher Insights and Workflow Inspection, as “now generally available” in the item text. That’s Adobe’s statement. Test them on real incidents before you rely on them for diagnosis.

Bottom line

Do the New Relic to OpenTelemetry migration first, because it’s the only item on a hard clock this month and OpenTelemetry is still Limited Availability. Then update your CDN IP allowlists and audit JWT credentials before January.

Has anyone already migrated off the built-in New Relic integration? How long access took, and whether your existing alerts carried over, would help a lot of teams here.