DocumentationExperience Cloud KCS

Remediating outdated dependencies and deprecated APIs in AEM as a Cloud Service

Last update: October 14, 2026

Adobe Experience Manager as a Cloud Service (AEMaaCS) may report outdated dependencies and deprecated API usage in the Cloud Manager Health Assessment, even when the environment uses recent AEM SDK and Java versions. These findings can affect eligibility for Adobe updates, security patches, and support if they aren’t remediated. To resolve the issue, update outdated dependencies, refactor deprecated API usage, upgrade unsupported Java versions if required, and rerun the Health Assessment.

Description description

Environment

Adobe Experience Manager as a Cloud Service (AEMaaCS)

Issue/Symptoms

  • The Cloud Manager Health Assessment reports outdated dependencies, such as older library versions, in project repositories.
  • The assessment identifies deprecated API usage in the codebase.
  • These findings may persist even when the environment runs recent versions of the AEM SDK and Java.

Root cause

Outdated dependencies and deprecated API references remain in the codebase. These issues can prevent environments from receiving critical Adobe updates, security patches, and support. After the deprecation deadline, affected environments may fall outside Adobe’s standard commitments for performance, availability, and future enhancements.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Access the Cloud Manager Health Assessment:

    1. Sign in to Cloud Manager.
    2. Go to the Health Assessment section for the program and review the latest report.

  2. Identify all outdated dependencies and deprecated API references listed in the Health Assessment report for the code repositories.

  3. Update the outdated dependencies:

    • For each outdated dependency, update the project’s build files, such as pom.xml or build.gradle, to reference the latest supported versions compatible with the current AEM SDK and Java version.
    • Run a build to ensure there are no compatibility issues after updating the dependencies.

  4. Refactor deprecated API usage:

    • Search the codebase for APIs identified as deprecated in the Health Assessment findings.
    • Replace the deprecated API calls with their recommended alternatives by following the AEM SDK or Java documentation.
    • Test the application to verify that the refactored code works as expected.

  5. If the Health Assessment identifies an unsupported Java version, update the runtime to a supported version according to Adobe’s guidance.

  6. Validate the remediation:

    • Redeploy the application to the AEM as a Cloud Service environment.
    • Rerun the Cloud Manager Health Assessment to confirm that all findings are addressed and no new issues are reported.

  7. Monitor for future deprecations and regularly review Health Assessment reports and Adobe deprecation notices to proactively address new findings.

recommendation-more-help
experience-cloud-kcs-help-kbarticles