2026.04.0 AEM Release Overview Video

Transcript

The latest AEM release is live. Packed with efficiency tools and performance boosts, this version is built to streamline your day-to-day. Here’s what you need to know.

Delivering intent-aware experiences starts with the ability to generate winning experiences faster, and activation puts the content to work. In order to drive intent-aware experiences, optimization needs to happen continuously.

Trust and governance is embedded in Experience Manager in every aspect from generation to optimization. And foundational services leverage AI to power the broad range of AEM applications.

Here is a breakdown of the key innovations we’ll be exploring today.

Log forwarding – CDN logs for Sumo Logic. Mail service support for Microsoft Graph API.

Relinking assets from a folder via Assetlink.

IDE AI tooling for code generation.

Versioning support for Forms.

New MCP servers and Clod connector.

AI translation integration.

Adobe Experience Manager onboarding agent via Assets. First, let’s take a look at the latest enhancements for content activation.

Log forwarding – CDN logs to Sumo Logic.

AEM’s log forwarding feature lets customers who work with logging vendors send AEM, including dispatcher logs, and CDN logs to that logging destination. This is convenient for organizations who have a mandate or preference to use a specific vendor for log ingestion, logging, and optimization use cases. It’s now possible to forward CDN logs to Sumo Logic. Previously, this was limited to AEM and dispatcher logs.

Mail service support for Microsoft Graph API.

AEM’s mail service now supports Microsoft Outlook via Microsoft 365 using the Microsoft Graph API.

This is particularly helpful for organizations who allow SMTP, which is already supported by the mail service. Authentication is via OAuth 2.0. Re-linking assets from a folder.

Creative teams working with InDesign and using linked assets from AEM in their documents are more efficient with re-linking files to assets or adapting to changes in the repository. For example, assets moving to a different location. When re-linking a broken link in InDesign, Asset Link offers an option to re-link other links from assets stored in the same folder in AEM.

This provides creatives with an additional quick way of updating links to the source of truth in AEM assets.

Next, let’s dig into some optimization enhancements and how they can help you work more efficiently. IDE AI tooling for code generation. Developers can become more productive by using AEM’s AI tools in IDEs like Cursor and VS Code with GitHub Copilot.

IDE AI tooling includes agent skills to generate code for AEM components, dispatcher configuration, workflows, and more. Local MCP servers for AEM and dispatcher debugging. See this red promo banner on the weekend homepage? In the next few moments, we’ll show you how to create this in any AEM component using a coding agent enhanced with AEM agent skills.

Open your project in an AI powered IDE and start by opening the agent chat and describing the component you want to build.

You can provide a design reference from your UX team or even supply a Figma design through the Figma MCP server to guide the implementation. If a design isn’t available, a clear plain language description works just as well.

Be sure to define the authoring dialogue fields.

In this weekend example, we include a promo label, CTA text and CTA link so the agent can generate the appropriate dialogue structure. Using the create component skill, the agent generates the required artifacts aligned with AEM best practices. Take a moment to review the generated code, then build and deploy it. Once deployed, open AEM authoring, add the component to a page, configure the dialogue and confirm that it matches the intended design.

With the support of structured guidance, you can move from concept to a working component more efficiently while staying aligned with AEM best practices.

Experience Governance MCP Server, AEM MCP servers and their associated tools let you interact with AEM using conversational prompts from surfaces such as chatbots and IDEs.

The Experience Governance MCP server is now available. It safeguards brand integrity and compliance, letting you evaluate content against brand governance rules and retrieve brand configurations and available governance checks.

Separately, Clod users can now browse Anthropix Connector Marketplace to one click install the Adobe Experience Manager Connector. This MCP server exposes a growing set of tools to interact with AEM, including editing content through prompting. Let me show you how to check if your website is on brand using the Experience Governance MCP server. For this demo, we’ll use the Frescopa coffee website and Clod as the MCP host. You can also use any AI powered IDE or chat application that supports the Experience Governance MCP server. First, in Experience Hub, go to governance context to define your brand guidelines.

For Frescopa, we’ve set up guidelines like voice, streaming, and text checks. You can also define image checks. Now, let’s move to Clod and connect to the MCP server in Clod Edit Custom Connector. Give it a name and enter the Experience Governance MCP URL. To connect to the Adobe hosted MCP server, sign in with your Adobe ID.

Once connected, you’ll see the available MCP tools. These tools load your brand checks through the MCP server.

In the Clod chat, start by asking for a list of brands. In this case, I have access to two brands defined in Experience Hub.

Next, ask for Frescopa brand checks.

These checks are loaded through the MCP server and include both text and image validations.

Now, let’s verify if the Frescopa coffee website is on brand.

As you can see, it found an issue.

The no shouty all caps CTAs check failed with two CTAs not following the guideline. With the Experience Governance MCP server, it’s easy to ensure your content always stays on brand.

AI translation integration. Get content translation right the first time. Achieving human translation quality at machine translation speed by using large language models as translation services for AEM. Instant high quality translation. Transcreation with style guidelines. Integrated in corporate AI strategy by leveraging customers own LLM license. So a new feature that has been added in Experience Manager and that is AI translation integration. Translation integration is where third party services for content translation are connected with AEM in order to perform the translation task. These translation services are set up in cloud services, translation cloud services, and are attached here to a configurable configuration. If we look at the global configuration that makes connected services available for all pages and assets across an instance, we’ve always had for many years, Microsoft Translator for example, integrated out of the box for content translation where all that a user has to do is to provide their credentials in order to configure Microsoft Translator for machine translation. Or if a customer chooses to use third parties like SmartLink or translations.com, GlobalLink for content translation, these companies would supply a connector that it gets installed in AEM and the user then configures this connector right here in those screens. What is now new is that we have an out of the box Gen AI connector. So the Gen AI connector now allows or lets customers use an LLM for translation and specifically Azure OpenAI GPT model to use this LLM for content translation. Since as we know, LLMs can translate content extremely well with a lot of contextual capabilities that machine translation was never able to provide since this is more a word by word configuration, Azure OpenAI can now be used for content translation with AEM. User brings their own API key and the other required information sets up Azure OpenAI for content translation in their AEM instance and can then use this service for content translation. Additionally, what is possible now with AEM is for users to upload translation style guides documents to AEM. A translation style guide is a document like here that every company’s corporate marketing department will have to define how content in certain languages should be translated. This is an Adobe, it’s an official Adobe localization style guide available from corporate marketing that has been used for all translation efforts across Adobe properties. And it defines how certain phrases should be defined, what tone should be used and anything that pertains to the specific language.

There’s style guides for German, French, for Italian, for every language that Adobe conduct gets translated in. For anyone who’s curious, a Microsoft translation style guides are actually available online and can be downloaded.

Such documents can now be uploaded to AEM and it’s a simple upload process where the locale, the target locale is defined and then you just pick your document and upload it to AEM. And what that then does is that the document has been processed by an agent, by a service in order to extract in JSON format translation guidelines from this document. We see them here for the German translation, for the Spanish translation, which were all extracted from uploaded translation style guide documents. We see with a little green light here that the extraction process has successfully been completed. If we upload a new document, this little light would be yellow while the document has been processed. So we’ll have a couple of minutes and then these translation guidelines are available for processing by the agent to create the prompts that include the content that should be translated. They will be sent to the LLM for content translation. Very similar to brand guideline documents, for example. So once the service is configured with the API key for the respective LLM, and again, right now it’s Azure OpenAI, we plan on adding support for Gemini, for Claude and DeepL as well in a future release. Then this service becomes available for content translation in the AM. Users will first, let me close this real quick. Users will first or more like system product owners, administrators will configure, going back in the Conf Global, will configure the agentic translation as a global default in the translation integration framework which also has been around since early versions of AM6 where for sites and assets, default translation methods are defined and users can pick from machine translation or human translation with a third party vendor and now with this new agentic translation for content in sites. So that when we go to a webpage here in Weaken, for example, and just pick a single page that we want to translate, let’s say the About Us page, and now we have a language root in German available, go to create and translate, translate this in German.

What happened? About Us, language copies, create and translate, translate this in German, and give the translation project a name, create this translation project, translation project was created. If we now switch over to our main project, our 2AM projects, and look at the translation project that was created here, right here, we see that the GenAI translation connector was chosen as a default for this translation activity. If we go into the project, we see that the GenAI service was used for translation, can also be observed in the properties of this translation project, just like machine translation before or human translation, now GenAI translation is available for translating in a job, in a translation job, this one particular page that was selected for translation. So this completes the demo, the new capability that we added is AI Translation Integration is available behind feature toggle in the AM March release, 2026-03, and will be available to the general public as GA in the April release, 2026-04. Thank you. AEM Onboarding Agent Assets.

Go live in hours to days of practitioner led work, not weeks to months of specialist led work. AEM Onboarding Agent translates business intent directly into AEM dam configuration. Other agentic dams focus on existing practitioners and their day-to-day, only AEM assets helps you get started.

Your dam owners can now complete setup themselves faster on best practice recommendations every time.

This agent is always ready to act safely, every change requires your explicit approval.

Chat with AI assistant for new users and new operations or upload attachments for experienced practitioners ready to automate at scale.

Four skills now in beta, folder hierarchy, tag taxonomy, metadata forms, and bulk import.

Ask your account team about Adobe’s AI explorers program for access.

These updates are all about helping you move faster, work better together, and deliver smarter experiences at scale.

Check out the complete release notes on Experience League.

Don’t forget to like and subscribe to stay updated.

Thanks for hanging out. Catch you in the next video.