JD Edwards licensing moves with the workload across cloud platforms. The metric conversion, the processor mapping, and the mobility window each change when the move lands on OCI, AWS, or Azure. The buyer side that reads the rules first carries the savings cleanly.
JD Edwards licensing is not constant when the workload moves to a cloud platform. The metric mapping, the processor count, and the mobility rules shift between OCI, AWS, and Azure. The Oracle Cloud Computing Environments Policy governs the count on AWS and Azure. OCI follows the OCPU rule directly.
The buyer side that documents the position per cloud holds the audit. The customer that runs JD Edwards across two or three clouds carries three separate entitlement records. The mobility rules differ when the workload returns from cloud to on premises. The route decision lands at planning time, not migration time.
JD Edwards runs cleanly on three cloud platforms. Each carries a distinct licensing posture. The route decision drives the multi year cost and the audit exposure.
OCI is the named Oracle cloud. The OCPU rule applies directly. One OCPU equals one Processor license. The math is the cleanest of the three.
AWS is an authorized cloud under the Oracle Cloud Computing Environments Policy. The two vCPU to one Processor rule applies on hyperthreaded instance families.
Azure is the second authorized cloud under the policy. The same two to one rule applies on hyperthreaded virtual machines. Some Azure families count differently and require contract review.
The JD Edwards Processor metric maps cleanly to OCI. The mapping on AWS and Azure follows the Oracle Cloud Computing Environments Policy. The concurrent user and Application User metrics travel with the workload unchanged.
| Cloud route | Processor mapping | Concurrent user | Mobility |
|---|---|---|---|
| OCI | 1 OCPU = 1 Processor | Travels with workload | Native, no policy lookup |
| AWS hyperthreaded | 2 vCPU = 1 Processor | Travels with workload | Authorized cloud policy |
| AWS non hyperthreaded | 1 vCPU = 1 Processor | Travels with workload | Authorized cloud policy |
| Azure hyperthreaded | 2 vCPU = 1 Processor | Travels with workload | Authorized cloud policy |
| Azure non hyperthreaded | 1 vCPU = 1 Processor | Travels with workload | Authorized cloud policy |
On premises JD Edwards licenses can move to authorized clouds under the policy. The reverse move from cloud to on premises has different rules. The mobility window is contractual.
The on premises license entitlement can run on AWS or Azure provided the customer does not exceed the entitled Processor count under the two to one rule. No paperwork to Oracle is required.
The reverse move is permitted under the master agreement. The customer documents the new deployment location and updates the internal entitlement record.
Moving to OCI follows the standard authorized cloud rules. Some customers convert the license to a subscription model for OCI which carries a different cost and term.
OCI is the cleanest cloud route for JD Edwards. The OCPU equals one Oracle Processor. The pricing math is direct. The mobility is native to Oracle.
AWS is the broadest cloud route for JD Edwards. The instance family selection is large. The licensing math follows the policy.
EC2 m5, m6i, r5, r6i, and x1e all support JD Edwards. The instance family decision drives the Processor count under the two to one rule.
JD Edwards databases on RDS for Oracle follow the same two to one rule. The RDS Multi AZ deployment can trigger an unintended doubling of the Processor count under Active Data Guard.
Dedicated hosts on AWS let the customer count cores rather than vCPU which suits some buyer side license positions.
Azure is the third cloud route for JD Edwards. The integration with Microsoft Active Directory is native. The licensing math follows the same two to one rule.
The cloud route decision lands at planning time. The right choice depends on the workload shape, the existing entitlements, and the cost target. Four gates run the decision cleanly.
The checklist takes the buyer from the renewal letter to the executed strategy. The window is the renewal anniversary. The earlier the work starts, the wider the option set.
On Oracle Cloud Infrastructure, JD Edwards Processor licensing maps directly. One OCPU equals one Processor license. The math is the cleanest of the three cloud routes because OCI is the named Oracle cloud and no policy lookup is required. The concurrent user metric travels with the workload unchanged.
AWS is an authorized cloud under the Oracle Cloud Computing Environments Policy. On hyperthreaded EC2 instance families, two vCPU equals one Processor license. On non hyperthreaded families, one vCPU equals one Processor license. The instance family decision drives the Processor count. EC2 m5, m6i, r5, r6i, and x1e all support JD Edwards under this rule.
No. The Oracle Cloud Computing Environments Policy is a non contractual document published on the Oracle website. The policy can change without notice. The buyer side counsel should review the cloud licensing position against the master agreement first and rely on the policy second. Customers with concerns may request a contractual amendment that codifies the cloud position.
Yes. Microsoft Azure is the second authorized cloud under the policy. The same two vCPU to one Processor rule applies on hyperthreaded virtual machines. The Dv5, Ev5, and HBv4 families all support JD Edwards. The Active Directory integration is native on Azure which suits enterprises with an existing Microsoft footprint.
The concurrent user metric travels with the workload across any cloud. The peak counting rule applies the same way on OCI, AWS, and Azure. The session log table remains the auditor view. The buyer side should run session hygiene before the audit regardless of the cloud route. The peak does not reset when the workload moves.
RDS for Oracle Multi AZ deployments can trigger an unintended doubling of the Processor count when Active Data Guard is enabled on the standby instance. The audit position treats the standby as a separately licensed environment. The buyer side mitigation is to run Multi AZ without Active Data Guard or to license both instances. The contract review should confirm the position before the deployment.
Yes. The reverse move from cloud back to on premises is permitted under the Oracle Master Agreement. The customer documents the new deployment location and updates the internal entitlement record. The license count does not need to be repurchased. The mobility rule supports both directions provided the entitled Processor count is respected.
Redress runs the workload mapping, the entitlement review, the per cloud math, the hybrid placement test, and the contract negotiation inside the Vendor Shield subscription and the Renewal Program. The work includes the order document review, the cloud licensing policy reading, the audit defense record, and the migration plan against the licensed Processor count.
Redress runs this practice inside the Vendor Shield subscription, the Renewal Program, the Oracle service line, and the Software Spend Assessment.
Read the related JD Edwards pricing models guide, the concurrent licensing article, the Oracle Knowledge Hub, the benchmarking service, and the Benchmark Program.
The companion playbook covers the Oracle Unlimited License Agreement decision tree, certification mechanics, and the negotiation moves that protect the customer at exit.
Independent. Written for CIOs, CFOs, and procurement leaders. No vendor partner affiliation.
Open the playbook in your browser. Corporate email only.
Open the Paper →JD Edwards on cloud is three different licensing problems. OCI is the named cloud. AWS and Azure run on the policy. The customer that decides the route at planning time captures the cost cleanly.
We have advised twenty JD Edwards cloud migrations across nine industries. The route decision lands at planning time, not migration time.
Cost benchmarks, license rightsizing patterns, and the negotiation moves that worked. Written for buyer side teams running active vendor decisions.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
