Quick answer
Oracle Fusion 26D is Oracle’s fourth and final quarterly update of 2026. Cohort A customers see test environments update November 6, 2026, with production following November 20. Cohort B follows in December (test December 4, production December 18), and Cohort C in January 2027. As of October 27, Oracle’s Feature Listing shows 884 features in 26D, with 55 flagged as large-scale impact and 223 arriving with no action required. 26D shifts the focus from shipping new AI features to governing them: AI Agent Studio gains guardrails, model lifecycle management, AI unit budgets, and CI/CD integration, while several HCM agent types are replaced or deprecated. As a minimum, teams should capture a baseline that includes roles, privileges, profile options and offerings before their test environment updates, compare environments during the two-week window, and confirm production matches what was tested before cutover.
Oracle Fusion 26D by the numbers
From Oracle’s 26D Feature Listing as of October 27, 2026:
- 884 features: 370 in SCM, 286 in HCM, 79 in ERP, 46 in Sales, 41 in Service, 40 in Industry, 16 in Common Technologies, and 6 in Marketing.
- 454 features (51%) carry Oracle’s Redwood flag.
- 142 features are AI-tagged, including 101 AI agent features, 26 agentic applications, and 12 Fusion Claw features.
- 223 features arrive with no action required to enable them.
- 55 features are flagged as large-scale impact to existing processes, compared with 38 for 26C in the same listing. That is the most of any quarterly update in the listing, ahead of 26A (53) and 26B (52).
- 26 features from earlier updates reach the end of their opt-in window at 26D.
Oracle typically adds features throughout the quarter, so expect these numbers to grow. 26C grew by more than 100 features after it was first published. The scope of a release keeps moving after you start planning for it, which is a configuration management problem in itself.
When 26D reaches your environments
Oracle Fusion Cloud Applications update on a mandatory quarterly schedule. Test environments update on the first Friday of the update month, and production environments follow two weeks later on the third Friday.
For 26D, the timing is as follows: Cohort A updates in November, Cohort B in December, and Cohort C in January 2027. If you are unsure of your cohort, check your Oracle Cloud Console. Oracle publishes readiness details at least 30 days before Cohort A’s test environments update, and the 26D What’s New pages have been live since early September. (Source: Oracle ERP ACE: Harness the Business Value of Quarterly Updates)
26D also lands at the worst possible time of year for a lot of teams. Year-end close, holiday change freezes, and reduced staffing all overlap with the two-week testing window. And it arrives on top of 26C, which added 953 features of its own. Any configuration drift your environments picked up during 26C carries straight into 26D.
The pattern from 26C still holds. DevOps manages the release process: pipelines, promotion gates, automation, traceability. Configuration management controls what your environments actually contain: what is configured, how environments differ, and what changed and when. Oracle quarterly updates require both. If you missed it, our 26C breakdown covers that framing in detail.
What is different about 26D is where the changes land. Less of this release is about new screens. More of it is about roles, privileges, and setup, along with changes to the AI agents Oracle ships.
What 26D changes in your environment
Oracle adds governance controls for AI
Oracle’s 26D AI Agent Studio updates concentrate on governance, testing, and deployment controls rather than new AI capabilities. The Feature Listing includes:
- Add instruction guardrails to LLM nodes
- Configure models and manage model lifecycle
- Manage AI unit budget, consumption, and controls
- Test and validate AI Agent Studio workflows with ATLAS
- Integrate AI Agent Studio applications and workflows with CI/CD
- Use Oracle Fusion Claw to create autonomous outcomes with agentic applications
These are Oracle’s own controls for how agents are built, tested, and run, and they signal how much more activity in your Fusion environments will involve AI. Agents can work with master and transactional data, not only configuration, so review what each agent your teams use is allowed to do, and agree who owns that decision. With AI unit budgets in the picture, AI consumption also becomes a cost that finance and IT both have a stake in. The broader picture is covered in Flexagon’s Oracle AI readiness guide and our post on preparing Oracle environments for AI-driven change.
Agents and data objects are being replaced
26D includes several deprecations that may touch work your team has already built:
- Personal Information Assistant and Person Legislative Information agents are replaced by the Person Data Assistant agent.
- The Representative Agent (Supervisor Agent Type) is being deprecated.
- BI view objects in Oracle BI Cloud Connector are being deprecated and replaced, which can affect data extracts and downstream integrations.
This is a new kind of quarterly update work. AI agents your team built can now become technical debt the same way customizations do. Before you can plan a migration, you need to know which agents exist, which templates they were built on, and which environments they are deployed in. The same goes for any extract or integration that depends on a deprecated BI view object.
New features come with new privileges
Quarterly updates routinely change privileges, roles, and access, and 26D is no exception. Five 26D features list Security Adjustment as the action to enable, and others introduce new roles or privileges outright. A few examples:
- Dedicated Security Role for Absences and Entitlements in Absence Management.
- Separate Line Manager Access to Work Patterns in Human Resources, which requires a security adjustment.
- Control creation of new subinventories with a privilege in Inventory Management.
Some AI agents follow the same rules. For example, salary updates through the Employment Updates Agent require the user to already hold the privilege and data access needed for a salary change in the standard application. The agent does not grant additional access. (Source: K8 Mead)
The implication is simple. If role and privilege configuration differs between test and production, the same feature behaves differently in each. A clean test result means nothing if production users hold different access.
Most features need setup, and setup is configuration
Oracle’s Feature Listing shows the action required to enable each feature. For 26D, 374 features are marked Setup Required, 169 Potential Setup, 88 require an opt-in (with or without setup), and 18 are enabled through Visual Builder. Every one of those creates configuration that has to be consistent across environments and promoted from test to production with the same discipline as any other change.
Redwood: the SCM deadline moved, the work did not
Earlier guidance pointed to 26D for mandatory SCM Redwood adoption. In early September, Oracle moved the deadline for most SCM products from before 27A to before 27B, roughly one more quarter. (Source: K8 Mead: Oracle Has Moved the SCM Redwood Deadline)
The extra time helps. It does not reduce the work. Page Composer personalizations still need review, extensions and integrations still need validation, and role-based access still needs testing. Opt-in windows also continue to close. 26 features from earlier updates reach the end of their opt-in window at 26D, 16 of them in SCM, mostly in Manufacturing and Maintenance, including several Redwood work order and work definition pages. In Sales, two 26C features that migrate generative AI capabilities to AI agents also reach the end of their opt-in window. Use the extra Redwood quarter as contingency, not as a reason to pause.
What 26D means for your DevOps pipeline
Oracle is bringing AI into the release process
CI/CD integration for AI Agent Studio means agents, workflows, and their settings can follow the same approval processes, audit controls, and change management as everything else in your Oracle landscape. (Source: Oracle 26D What’s New: Integrate AI Agent Studio applications and workflows with CI/CD)
That is the right direction. It also means AI changes will increasingly arrive alongside the setup, extensions, and OIC integrations your release process already manages. Agree now who owns AI agent changes and how they are reviewed before they reach production.
Year-end timing changes the risk profile
For many teams, especially Cohort B and C customers, 26D testing overlaps with year-end close and holiday change freezes. That compresses the time available for testing and makes undocumented changes harder to catch. A documented baseline and an automated environment comparison matter more in a short, crowded window, not less.
Environment comparison is still the gate
Treat the two weeks between test and production as a structured pipeline stage. Run a formal environment comparison after test updates, document the delta, and use it as a gate before production cutover. For 26D, pay additional attention to the role and privilege assignments, not only functional setup. Flexagon’s enterprise DevOps capabilities guide covers environment comparison as a core platform capability.
Where Flexagon fits
26D is a release event and a configuration event at the same time, and the Flexagon platform is built for both. Flexagon Configuration Management captures point-in-time baselines of your Oracle Fusion Cloud and EBS environments, compares them live, and tracks changes, so you can separate what 26D changed from what was already different. Comparisons cover roles, privileges, and security profiles alongside functional setup. Flexagon DevOps moves setup changes, Visual Builder extensions, and OIC integrations from test to production through a controlled release pipeline, with an audit trail that doubles as SOX ITGC evidence.
Configuration Management meets Enterprise DevOps, applied to every quarterly update.
What to do before your test environment updates
Confirm your cohort and dates
Check your Oracle Cloud Console. Do not assume your cohort is the same as last quarter, and map the two-week window against your own year-end calendar.
Capture a baseline that includes security
Document the current configuration state of your test environment before it updates. For 26D, that baseline should include roles and privileges, not only functional setup. Without it, you cannot separate what 26D changed from what was already different.
Inventory agents built on deprecated templates
List every agent your team has built, the template it came from, and where it is deployed. Flag anything built on the Personal Information Assistant or Person Legislative Information templates for migration planning.
Map the features you plan to enable
For each 26D feature you intend to turn on, note whether it requires setup, a Visual Builder extension, or new privileges. That list becomes the scope of what needs to move from test to production.
During the two-week testing window
Two workstreams run in parallel. Functional testing validates that 26D works for your users. Configuration management validates that your environments are consistent and the changes are documented. Most teams run the first well. The second is where gaps appear.
Compare your test environment against the pre-update baseline as soon as it updates. Test privilege-gated features using real role assignments, not administrator accounts. Validate AI agent behavior before production, using ATLAS if your team has adopted it. And document what changed: the change record for 26D in production is part of your SOX ITGC evidence.
After production updates
Capture the post-26D production baseline and compare production against test to confirm that what was validated is what actually landed. That baseline becomes your starting point for 27A, which arrives in February 2027 for Cohort A customers.
Each quarterly cycle produces a baseline, and each baseline makes the next cycle easier. Teams that treat configuration management as a standing discipline, not a pre-update scramble, find that environment consistency becomes the default state.
Frequently asked questions
When does Oracle Fusion 26D update test and production environments?
For Cohort A, test environments update November 6, 2026, and production updates November 20, 2026. Cohort B updates in December (test December 4, production December 18). Cohort C updates in January 2027. Confirm your cohort in the Oracle Cloud Console.
How many features are in Oracle Fusion 26D?
As of October 27, 2026, Oracle’s 26D Feature Listing includes 884 features. 454 carry the Redwood flag, 142 are AI-tagged, 223 arrive with no action required, and 55 are flagged as large-scale impact. Oracle typically adds features during the quarter, so check the Feature Listing for the current count.
What is being deprecated in Oracle Fusion 26D?
In HCM, the Personal Information Assistant and Person Legislative Information agents are replaced by the Person Data Assistant, and the Representative Agent (Supervisor Agent Type) is being deprecated. 26D also deprecates and replaces BI view objects in Oracle BI Cloud Connector.
Did Oracle move the SCM Redwood deadline?
Yes. In September 2026, Oracle moved mandatory Redwood adoption for most SCM products from before 27A to before 27B. The required work, including personalization reviews, extension validation, and access testing, did not change.
How should AI agents be managed during an Oracle quarterly update?
Start with what Oracle is changing. Check whether any agents your teams use are being replaced or deprecated in 26D, and plan those migrations. Use Oracle’s own controls, such as guardrails, ATLAS testing, and AI unit budgets, to govern how agents run. And because agents can work with master and transactional data, not only configuration, agree who owns agent changes and how they are reviewed before production.
Preparing for 26D?
See the platform in action: Request a demo
References
Related Flexagon content
- Oracle Fusion 26C Hits Test Environments in August
- 10 Enterprise DevOps Platform Capabilities for 2026
- AI Readiness in Oracle Environments
- Preparing Oracle Environments for AI-Driven Change
- Oracle Cloud Applications
- Oracle Cloud Integration
Oracle primary sources
- Quarterly Updates Made Easy, Oracle Fusion Insider
- Harness the Business Value of Quarterly Updates, Oracle ERP ACE
- Oracle Fusion Cloud Inventory Management 26D What’s New
- Oracle Fusion Cloud HR 26D What’s New: Person Data Assistant
- Oracle Fusion Cloud Common Technologies 26D What’s New: AI Agent Studio CI/CD
- Oracle Fusion Cloud Applications 26D Feature Listing (accessed October 27, 2026)
