Best Practices Analyzer · pattern code · Code & APIs
BPA code OU: Deprecated or removed APIs in use
When Adobe's Best Practices Analyzer reports OU, it has found deprecated or removed APIs in use on your AEM instance. Here is what that means for a move to AEM as a Cloud Service.
What to do
Replace with the API named in Adobe's deprecated and removed features list.
Step-by-step fix: AEM Cloud Service APIs removed on 26 February 2026.
Can it be fixed automatically?
- Not by Adobe's Content Transformer, which only handles content findings (ACV, CAV, DOPI, OAUI, PCX, REP and URS).
- In our pipeline, automation for this pattern is rated high: agents prepare the change and an engineer reviews it.
How much work is it?
Our readiness scan plans about 1.5 hours per finding at MAJOR importance (1.5× for CRITICAL, 0.5× for ADVISORY), plus a small fixed cost, capped at 200 hours for this code. INFO rows are treated as inventory and not costed. These are planning figures, not a quote.
Reading the row in results.csv
Filter the code column for OU. The importance column says how urgent each row is, identifier usually holds the repository path, and message describes the finding. See how to read a BPA report for every column.
Source: Adobe Pattern Detector documentation for OU. Checked 19 October 2026.