Microsoft Dynamics 365 integration with Oracle CPQ Running in Fusion
Oracle CPQ 26D supports integration for Microsoft Dynamics 365 and CPQ sites running in Fusion. This allows you to leverage Oracle Identity and Access Management (IAM)'s Identity Domains and Oracle Identity Cloud Service (IDCS), as an integrated identity management solution.
Use the Microsoft Dynamics 365 Integration with Oracle CPQ Running in Fusion to:
- Launch Oracle CPQ from Dynamics opportunities using single sign-on.
- Create and update CPQ quotes from the Microsoft Dynamics selling workflow.
- Synchronize quote details and line items back to Microsoft Dynamics using REST web services.
- Configure secure authentication using OAuth, SAML, Microsoft Azure, and Oracle IAM identity domains.
- Use the Microsoft Dynamics 265 connector and migration package to set up secure user management and site-specific settings.
Once the integration connection is established, a sales user can launch Oracle CPQ from Microsoft Dynamics opportunities via Single Sign-On user authentication to create or update a quote within CPQ and then seamlessly synchronize the quote details back to Microsoft Dynamics. This solution reduces the amount of time to generate quotes and provides seamless operation through standardized authentication and package-based deployment.
Steps to enable and configure
This integration requires the following prerequisites:
- A Microsoft Dynamics 365 environment
- Oracle CPQ running in Fusion
- OAuth 2.0 configuration
- API access and credentials for the integration
- Microsoft Azure and Oracle IAM identity domain or IDCS SAML configuration
- The required Dynamics solution package for the integration
Refer to the Oracle CPQ Running in Fusion with Microsoft Dyanmics Integration Guide for detailed information.
Tips and considerations
Oracle CPQ recommends testing the setup and end-to-end workflow in a non-production environment ahead of implementing the integration in a production environment.
Access requirements
Access to Oracle CPQ and Microsoft Dynamics integration administration is required, including permissions to manage OAuth client credentials, SAML identity provider configuration, integration package import/update actions, and environment deployment/validation activities.