2025.08.0 Release Overview Video

Transcript

It’s time for another great release of Adobe Experience Manager. In this release, we’ll walk through exciting new updates, enhancements, and features. Let’s check it out.

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.

This release brings several innovations and features to enhance your experience. Features like enhance customer security and trust by providing a secure connection and automation to AEM CMK. Productize OIDC for publish, JIRA. Author efficiency through easier rule creation. Bring your own markup. Content security policy. Bring your own Git. Snapshots and review. OAT OB button to download DOR. Bring your own Git. B Y O G.

Let’s start with the first group of innovations that unlock better content generation through intelligence.

Enhance customer security and trust by providing a secure connection and automation to AEM CMK. With customer managed keys exercise control over application and data encryption in Adobe Experience Manager cloud service, by managing data and application encryption organizations can heighten security with direct governance of your AEM application and data cryptographic keys. Teams can also raise confidentiality and integrity by reducing the likelihood of inadvertent access and disclosure of sensitive or proprietary data. Support for Azure Key Vault allows for key storage and management with an industry standard tool. Customers can now adopt the cloud with even more security confidence.

Productize OIDC for publish. JIRA. We are introducing OpenID Connect support for the published tier of AEM as a cloud service to meet long standing customer demand for secure standards based identity federation. This enhancement enables seamless integration with external identity providers, unlocking critical use cases such as intranet portals, B2C experiences and B2B partner access. Customers and partners will no longer need to attempt to implement custom OIDC authentication handlers with this native supported solution.

Broken rule detection made easy. For form authors, customers get clear visibility into broken rules with an easy red dot indicator, so they never miss a problem in adaptive form business logic. With automatic fixes for most rule breaks, users can repair issues in a single click, saving time and hassle. Anyone can quickly understand, spot and resolve issues making complex forms easy to manage without technical headaches.

Next up are enhancements for how to activate content. Edge delivery August updates. One, bring your own markup. GA. Edge delivery services is independent of the authoring tooling and supports multiple content sources. This means you could provide your own content source and publish the content from a repository you already have to AEM without having to migrate the content first. Two, content security policy. GA, GA, AEM boilerplate is secure by default against XSS and CSRF attacks. Three, bring your own Git. Limited availability. Customers can use their existing Git repo. GitHub Enterprise Bitbucket, Gitlabs, Azure DevOps cloud only, Adobe hosted repo. Four, snapshots and reviews. Limited availability. Publishing a set of content, dozens or hundreds of pages, usually for a launch of an initiative or event, as a snapshot for a particular time to enable review workflows.

OOTB button to download DOR. End users often need a downloadable document of record, but without a built-in option, authors must write custom code or add extra steps. A ready-to-use download DOR rule lets authors enable instant PDF downloads at click of a button with no development effort, speeding launch and improving user experience. In this last section, let’s explore optimization enhancements, …your own GitHub hosted repository in cloud manager and link them to their pipelines. With this, we are now offering a quicker way for customers to get their code to their AIM environments, removing the need for sync with the Adobe managed repository.

On top of that, once the connection between cloud manager and GitHub is established, we are enabled to offer feedback on customers’ code changes much sooner in their development process. With our new PR check functionality, an AIM developer working on a pull request in their GitHub repository will get the results of cloud manager code quality checks as soon as their pull request is created or updated.

This way, the developers will know if they are introducing any breaking change in their code as they are still developing it, and not much later, after they merge it and decide to actively execute a cloud manager pipeline like it was in the previously existing deployment flow in AIM.

As next steps, we want to extend those functionalities to the self-hosted versions of GitHub and enterprise, as well as other Git vendors, Bitbucket and GitLab. With that, the many customers that are using any of those Git options can benefit from the feature too. The onboarding and setup flow will be a bit different than the current one, where the customer has to install an app in their GitHub organization. For the other vendors, we want a unified experience. So, if a customer wants to, let’s say, onboard the Bitbucket repository, they will also have to validate it by going in their Bitbucket setup and creating an access token with specific permissions and then provide the token in cloud manager. Once this is done, the external repository is ready to go.

For the part of providing code quality checks on pull requests, this will most likely involve a one-time setup of webhooks in the customer repository, so that cloud manager can be notified about the developer’s activity on pull requests. After that, the experience will be similar, developers getting cloud manager code quality results before merging their code. These innovations are designed to help you move faster, collaborate better, and deliver more intelligent experiences at scale. Check out the release notes on Experience League to learn more, and don’t forget to like, comment, and subscribe to stay up to date on what’s next. Thanks for watching. We’ll see you in the next release.