Microsoft TeamsOracle Fusion Cloud ERP Agent view

How to add Microsoft Teams to Oracle Fusion Cloud ERP

Short answer

Build a Teams bot or workflow that receives Fusion events through Oracle Integration, posts adaptive cards to channels or people, and calls Fusion REST APIs on the user's behalf. Entra ID handles sign-in, and a mapping between Entra users and Fusion users keeps approvals attributable.

Many Fusion customers also run Microsoft 365. Finance, procurement and plant leaders live in Teams, while Fusion approvals sit in a notification email or the worklist. The result is stale approvals and people asking in chat for status they could read in the ERP.

The aim is not to recreate Fusion inside Teams. It is to push the few decisions that block work (approve this invoice hold, release this requisition, acknowledge this late receipt) into a card, and let people ask simple questions without opening the application.

Because Fusion and Teams are both cloud services, the integration is mostly identity and permissions. The design question is whose rights the card action runs under.

What teams use it for

Invoice hold resolution

Post a card to the AP team channel when a Payables invoice lands on hold, with supplier, amount, hold reason and buttons to assign or release.

Requisition approvals

Send procurement approvers an adaptive card with line items and budget impact instead of a worklist email.

Daily exception digest

Each morning, post late purchase orders, negative on-hand and unmatched receipts to the supply chain channel.

Plant questions in chat

Let a supervisor type 'status of PO 10045' to a bot and get header, receipt and invoice status.

Month-end close tracker

Show open close tasks by ledger and owner, and nudge task owners directly.

Oracle Fusion Cloud ERP integration surface

  • Fusion REST resources for invoices, purchase orders, requisitions and receipts; resource paths and versions vary by release update.
  • Payables invoice holds and approval tasks visible through REST and the worklist services on supported releases.
  • Business events and scheduled ESS jobs with BI Publisher output for batch digests.
  • Oracle Integration with the ERP Cloud adapter and REST adapters, which can call the Microsoft Graph and Bot Framework endpoints.
  • Federated sign-in through Oracle Identity Cloud Service or IAM domains connected to Entra ID, which is how a Teams user maps to a Fusion user.

How it works

  1. 1

    Choose bot or workflow

    A Power Automate workflow can post simple cards. A Teams bot (Bot Framework or Teams SDK) is better when you want questions, conversation state and card updates.

  2. 2

    Register in Entra ID

    Create the app registration, grant only the Graph permissions the bot needs, and configure the Teams app manifest.

  3. 3

    Align identities

    Map each Entra user to a Fusion user through the shared email or a federated subject, and store that mapping centrally.

  4. 4

    Receive Fusion events

    Use Oracle Integration to subscribe to events or poll a BI report, then hand the payload to the bot service.

  5. 5

    Render the adaptive card

    Include the minimum needed to decide, plus a deep link to the Fusion page for the full document.

  6. 6

    Act on the button press

    On Action.Submit, verify the clicker, check the document is still in the expected state, and call Fusion. Update the card so it cannot be actioned twice.

  7. 7

    Audit and alert on failures

    Record the Teams user, Fusion user, document and outcome; alert if a card action fails.

Example flows

Invoice price hold in the AP channel

Trigger: A three-way match creates a price hold on a supplier invoice.

  1. The event or digest identifies the invoice and hold name.
  2. The bot posts a card with invoice number, supplier, variance and PO price.
  3. A buyer takes the card and chooses Request Supplier Credit or Accept Variance.
  4. The service records the decision and calls the relevant action or creates a task for the AP analyst.

Result: Holds get an owner in minutes and the reason is stored with the decision.

Ask the ERP bot for PO status

Trigger: A planner types a PO number in a direct chat with the bot.

  1. The bot resolves the planner's Fusion identity.
  2. A read-only REST query fetches header, schedule and receipt data.
  3. A card returns promise dates, quantity received and invoice status.
  4. A button opens the PO in Fusion.

Result: A planner gets status without a login and without bothering a buyer.

Keeping data on-prem

Fusion is hosted by Oracle, so the practical on-premises piece is the bot service and any language model. Host the service in your own network or private cloud, allow outbound calls to Fusion and Microsoft Graph, and keep conversation logs there. If you want natural-language questions, run an open-weight model locally and let it translate the question into approved REST calls rather than free-form access. Messages still traverse Microsoft's Teams service, so confirm what your policy allows in a chat before putting supplier prices on a card.

Security checklist

  • Use delegated or per-user authorization for actions so the Fusion audit trail shows the real approver.
  • Limit the bot's Graph permissions and review them after each change.
  • Check document state at click time to prevent double approval from stale cards.
  • Keep sensitive fields (bank details, salary) off cards; link instead.
  • Restrict which channels may receive cards for restricted ledgers or business units.

Ways to get it done

Power Automate with Fusion connectors or HTTP calls

Effort: Days to a couple of weeks.

Simple notifications and low-volume approvals.

Custom Teams bot with Oracle Integration

Effort: A few weeks for a first set of cards.

Richer cards, conversation and tighter identity handling.

Partner build with Netray

Effort: Scoped pilot on one function such as AP or procurement.

Teams that want natural-language questions over ERP data under strict read-only controls.

Pitfalls

  • !Running every card action under one service account, which breaks segregation of duties.
  • !Cards that duplicate the whole PO, creating a second place to read stale data.
  • !Ignoring Teams rate limits during month-end bursts.
  • !Not handling users who exist in Entra but not in Fusion, or vice versa.
  • !Assuming event availability; some statuses need polling.

Frequently asked questions

Can approvals in Teams replace the Fusion worklist?

They can sit on top of it. The approval task still lives in Fusion workflow, and the card is a faster way to act on it. Keep the worklist as the system of record and audit source.

Do I need Oracle Integration?

Not strictly. A custom service can call Fusion REST directly. Oracle Integration helps with event subscription, retries, monitoring and adapters, so many teams use it for the Fusion side.

How is the user authenticated?

Teams signs the user in through Entra ID. You then map that identity to a Fusion user, ideally through federation, and perform actions with that user's rights or a controlled delegated mechanism.

Can the bot answer free questions about financials?

It can if you give it read-only tools that call approved queries. Avoid unconstrained SQL or open report access; scope by role and log the question and the query.

Is there a prebuilt Oracle to Teams connector?

Oracle does offer some Teams-related notifications and Oracle Digital Assistant channels, and third-party apps exist. Check what your release and licenses include before building.

Want Microsoft Teams working on your Oracle Fusion Cloud ERP?

A free 30 minute assessment: we map the integration path for your version and setup, and where it should run.

Get a free assessment