Oracle Fusion Cloud Procurement 26D: Microsoft Teams Collaboration for Procurement Documents

 

Introduction

Oracle Fusion Cloud Procurement 26D introduces an enhanced collaboration capability that allows users to create and access Microsoft Teams conversations directly from supported procurement documents and intake requests.

With this capability, procurement professionals can discuss purchase orders, agreements, requisitions, contracts, and intake requests without manually creating or searching for separate Teams chats.

The feature connects Oracle Fusion Cloud Procurement with Microsoft Teams through Microsoft Graph APIs and Oracle AI Agent Studio, helping teams maintain a more contextual and consistent collaboration experience.

What Is New in Oracle Procurement 26D?

The new View Conversation action allows users to launch a Microsoft Teams conversation from supported procurement pages.

Supported business objects include:

• Purchase Orders

• Blanket Purchase Agreements

• Contract Purchase Agreements

• Purchase Requisitions

• Procurement Intake Requests

• Related Change Orders

When a conversation already exists for a document, Oracle opens the existing chat. Otherwise, a new conversation is created.

The conversation title includes document-identifying information, helping participants understand which procurement transaction is being discussed.

Key Business Benefits

1. Contextual Procurement Collaboration

Users can initiate discussions from the relevant procurement transaction rather than creating separate chats manually.

For example, a buyer reviewing a purchase order can open its associated Teams conversation to discuss pricing, delivery schedules, or supplier-related concerns.

2. Improved Buyer and Requester Communication

For purchasing documents, the conversation automatically includes the person initiating the conversation and the document buyer. Additional participants can be added directly in Microsoft Teams.

For requisitions, the initial participant list can include the preparer, requesters, and assigned buyers.

3. Consistent Conversation History

Oracle maintains a common Teams conversation for a procurement document and its related change orders. This reduces fragmented discussions and makes previous conversations easier to locate.

4. Better Intake Request Coordination

Requesters, intake managers, and reviewers can access conversations from the applicable intake request pages. Participants are added according to the role and action that initiates the conversation.

5. Support for Changing Business Responsibilities

When the buyer changes, opening the conversation adds the current buyer to the existing chat. Previous participants may remain in the conversation and should be managed in Teams when necessary.

Solution Architecture

The integration involves four main components:

1. Oracle Fusion Cloud Procurement: Provides the purchase order, agreement, requisition, and intake request pages.

2. Oracle AI Agent Studio: Hosts the Procurement Conversation Assistant workflow and its Integrate Teams Chat tool.

3. Microsoft Entra ID: Provides application registration, client credentials, and OAuth 2.0 authentication.

4. Microsoft Graph API and Microsoft Teams: Creates or accesses the conversation and manages chat participants.

The high-level interaction is:

Oracle Fusion Procurement page → View Conversation → Procurement Conversation Assistant → Microsoft Graph API → Microsoft Teams chat

The integration uses OAuth 2.0 client credentials to authenticate the external REST call to Microsoft Graph.

Implementation and Configuration Steps

Step 1: Register an Application in Microsoft Entra

An administrator must register an application in the Microsoft Entra admin center.

1. Navigate to App registrations and create a new application.

2. Enter a descriptive name, such as Procurement Conversation Assistant.

3. Copy the Application (client) ID.

4. Create a client secret under Certificates & secrets and securely store its value.

5. Open API permissions and add these Microsoft Graph application permissions:

   • Chat.Create

   • Chat.ReadBasic.All

   • ChatMember.ReadWrite.All

6. Grant admin consent and verify that the permissions show as granted.

7. Copy the tenant-specific OAuth 2.0 token endpoint (v2) from the application's Endpoints section.

Client secrets must be protected and renewed according to the organization's security policies.

Step 2: Configure the Microsoft Teams Connection in Oracle AI Agent Studio

Open Oracle AI Agent Studio and locate the Integrate Teams Chat tool used by the Procurement Conversation Assistant workflow.

Configure the external REST connection as follows:

Configuration	Required value
Instance URL	https://graph.microsoft.com/v1.0
Authentication	OAuth 2.0 client credentials
Client ID	Microsoft Entra Application ID
Client Secret	Secret value generated in Entra
Scope	https://graph.microsoft.com/.default
Audience	Leave blank
Token URL	Tenant-specific OAuth 2.0 v2 endpoint
Use Body for client credentials	Retain the delivered setting

Save the tool configuration after validating the connection details.

Step 3: Validate User Identity Mapping

For every requester and participant, ensure that the email address configured in the Oracle Fusion user account matches the User Principal Name (UPN) of the corresponding Microsoft Entra account.

Also confirm that the Microsoft Entra account is enabled for Microsoft Teams.

Important: Access to a procurement document in Oracle Fusion and membership in its associated Teams conversation are separate permissions.

Step 4: Enable View Conversation on Procurement Pages

Use Oracle Visual Builder Studio to enable the action on the required pages.

1. Open the applicable procurement or intake request page in Oracle Fusion.

2. Select Edit Page in Visual Builder Studio.

3. Select Configure Page Properties.

4. Under Header, set View Conversation Agent to Procurement Conversation Assistant.

5. Publish the extension.

6. Repeat the configuration for each required view and edit page.

Repeat the process for relevant requisition, purchasing document, intake request, and change-order pages as applicable.

Enabling the action on a view page does not automatically enable it on the related edit page or change-order page.

Example Business Scenario

Consider an organization processing a purchase order for IT equipment.

The buyer needs confirmation from the requester and technical team about the delivery schedule and equipment specifications.

Traditional approach:

• The buyer manually creates a Teams chat.

• Participants search for the purchase order number.

• Discussions may be scattered across email and multiple chats.

• When the buyer changes, the team must identify the correct discussion.

With Oracle Procurement 26D:

• The buyer opens the purchase order in Oracle Fusion.

• The buyer selects View Conversation.

• Oracle opens the existing conversation or creates a new one.

• The buyer and relevant participants discuss the transaction in context.

• Related change orders use the same conversation associated with the base purchase order.

This approach improves traceability of business discussions, although the Teams conversation itself does not replace Oracle's formal procurement transaction records or approval workflow.

Security, Access, and Important Considerations

Implementation teams should consider the following points:

• Document security: Adding a participant to a Teams chat does not grant access to the corresponding Oracle procurement document.

• Formal approvals: Discussions in Teams do not submit, approve, or update procurement transactions. These actions must be completed in Oracle Fusion.

• Identity alignment: Oracle user email addresses must match the corresponding Microsoft Entra UPNs.

• Participant management: Changes to requisition preparers, requesters, or assigned buyers do not necessarily update existing chat membership automatically.

• Client secret management: Renew the client secret when required and update the Oracle Teams connection.

• Role provisioning: Users and administrators need the applicable AI Agent Studio duty roles, runtime permissions, and access to the relevant application pages.

Administrators should validate both the AI agent permissions and the business roles that control access to procurement pages before deployment.

Recommended Testing Scenarios

Before moving the feature into production, validate the following scenarios:

1. Create a Teams conversation from a purchase order that has no existing chat.

2. Reopen the same purchase order and verify that the existing chat is reused.

3. Open a related change order and verify that it uses the base purchase order conversation.

4. Test the View Conversation action from a purchase requisition.

5. Test conversation creation and access from requester, intake manager, and reviewer pages.

6. Verify that users without Oracle document access cannot gain access simply through Teams membership.

7. Validate participant handling when the buyer or requisition responsibilities change.

8. Test authentication, expired-secret handling, and the required Microsoft Graph permissions.

Conclusion

Oracle Fusion Cloud Procurement 26D makes procurement collaboration more contextual by connecting business documents and intake requests directly to Microsoft Teams conversations.

For implementation teams, the main work involves configuring Microsoft Entra application permissions, establishing the OAuth 2.0 connection in Oracle AI Agent Studio, validating user identities, and enabling the View Conversation action through Visual Builder Studio.

The result is a more connected procurement collaboration process that complements—not replaces—Oracle Fusion's transaction processing, security, and approval controls.

Reference: Oracle Fusion Cloud Procurement 26D What's New – Collaborate on Procurement Documents and Intake Requests Using Microsoft Teams.