How to add Microsoft Teams to JD Edwards EnterpriseOne

JD Edwards EnterpriseOne integration surface

• AIS Server REST with Orchestrator endpoints as the controlled entry point; token-based sessions are preferable to passing JDE passwords.
• Orchestrator Studio notifications and schedules for outbound triggers, and Real Time Events where your Tools release supports the event you need.
• Work Center and workflow approval objects, which hold the real approval state you must keep consistent with Teams actions.
• Read tables through AIS data requests: F4301/F4311 purchase orders, F0411 AP ledger, F4801 work orders, F4108 lots. Avoid direct SQL from the bot.
• JDE user and role security (including row and application security) to decide what each mapped user may see.
• One View Reporting for ad hoc dataset queries where an orchestration is overkill.

How it works

1. 1

   Decide the pattern

   Use Power Automate or Teams Workflows for simple notification flows, and a bot built with the Microsoft 365 Agents SDK or Bot Framework for conversational lookups. Product names have shifted over time, so check current Microsoft docs.

2. 2

   Register the app and identity

   Create an Entra ID app registration, define scopes, and map each Entra user principal to a JDE user ID in a maintained table. Unmapped users get read-only public data or nothing.

3. 3

   Expose JDE through Orchestrator

   Build one orchestration per action, such as GetOrderStatus, ApproveRequisition and ListHeldLots, each with strict inputs and a clear error shape.

4. 4

   Bridge to on-prem

   Put a small relay inside your network that calls AIS and talks outbound to the bot service, or publish the AIS path through an API gateway with mutual TLS. Avoid opening AIS directly to the internet.

5. 5

   Design adaptive cards

   Keep cards compact: key facts, one primary action, a deep link to the JDE form. Include a correlation ID and make actions idempotent so a double tap does nothing harmful.

6. 6

   Sync approval state

   When someone approves in JDE instead of Teams, update or remove the card so it cannot be actioned twice.

Security checklist

• Authenticate with Entra ID and enforce conditional access and MFA for anyone able to approve.
• Run actions under the mapped JDE user wherever possible, so JDE security and audit still apply.
• Scope each orchestration narrowly and exclude financial postings from the bot entirely unless reviewed.
• Store no JDE passwords in the bot; use tokens with short lifetimes and rotate service credentials.
• Retain card interaction logs for audit and align with your Teams retention policy.