Overview of Enabling the Microsoft 365 Integration
You need to follow a few steps to enable the Microsoft 365 integration for Oracle Sales Redwood User Experience.
Before You Begin
Before configuring this integration for your Sales application, carefully review the following guidelines. These guidelines help prevent data duplication, sync errors, and incorrect or faulty configuration settings that can impact your users and the production environment.
- Use separate email accounts for each environment
Don’t connect the same Microsoft email account to more than one Sales application environment (like development, testing, staging, or production). Doing so can cause data conflicts.
- Use different test email accounts for each non-production environment. Usually it's only one or two test users for each of the non-production environment.
- Only use work email accounts with the production environment, including for pilot testing with a group of production users.
- Be selective about which contacts you sync
Avoid syncing "All Contacts" or large saved searches.
- Instead, use a smaller, focused group — like a “My Contacts” list.
- Syncing too many contacts can slow down Outlook. Users might need to manually delete large numbers of contacts, which is cumbersome.
- Create a separate Azure app for each environment
Each Sales application instance needs its own unique Microsoft Azure app, because the Azure application needs to be set up with redirect URLs that are specific for that Sales application instance.
- Avoid removing users permanently
Only use the "Remove user permanently" action in Microsoft 365 Sync Monitor if the user's Microsoft 365 account is no longer active, such as when a user leaves the organization.
- If you remove an active user and then add them back, it will cause duplicate data if they previously shared data with Oracle.
Next Step
Once all pre-setup guidelines have been reviewed, proceed to the Prepare for Setup section to begin configuration.
Prepare for Setup
Before you begin, prepare for the installation and roll-out of the Redwood UX add-in for Microsoft Outlook. Check these things first:
- To complete the setups, you need two users:
- A setup user in your Sales application. See Create Implementation (Setup) Users.
- An administrator user for the Microsoft Azure and Microsoft 365 portals. See Set Up the Application in Microsoft Azure.
- Your users need the Download Outlook Installer privilege to use the product. This privilege needs to be added only if the user isn't configured with predefined roles like Sales Administrator (ORA_ZBS_SALES_ADMINISTRATOR_JOB), Sales Manager (ORA_ZBS_SALES_MANAGER_JOB), and Sales Representative (ORA_ZBS_SALES_REPRESENTATIVE_JOB).
- Check that Oracle's Adaptive Search is deployed in the Oracle Sales application and that search indexing processes are run and regularly scheduled. See Configure Adaptive Search and Workspace.
- Make sure your software meets the prerequisite requirements listed in What are the system requirements for Microsoft integration?.
- If you're using the Microsoft Edge browser, ensure that the browser includes the
following trusted sites:
- https://*.office.com
- The Oracle Sales cloud domain: for example: https://*.oraclecloud.com
High-Level Implementation Steps
Here are the high-level implementation steps to complete the integration:
| Step and Description | Where to Get More Details |
|---|---|
| Step 1 Set up the Oracle add-in in Microsoft Azure. During the setup, you copy the generated Application ID and Application Key. |
|
| Step 2 Complete the integration steps in Application Composer. During this setup, you configure the Microsoft application information and generate the Microsoft 365 manifest file. You also review the data synchronization settings and make changes as needed. |
|
| Step 3 Schedule the synchronization processes to ensure they meet your business needs. |
|
| Step 4 Deploy the add-in and test the integration. This involves setting up user groups in Azure and giving a limited set of users access to the add-in. |
|
| Step 5 Sign in to Microsoft 365 and open Outlook to test the integration and the add-in. |
|
| Step 6 Configure the add-in, such as the share views for appointment and emails, or layouts for tasks. If you've configured layouts in CX Sales Mobile, or in the Oracle Sales for Microsoft 365 add-in, you can simply import the layouts to this integration. |
To enhance email functionality, consider enabling the Microsoft Exchange email integration in Oracle Sales Redwood UX. The integration is fully compatible with the email sync features and the Redwood UX Outlook add-in, ensuring seamless connectivity and a more streamlined user experience. See Exchange Email Integration for Digital Sales for more information.
User Agreement
Here's a copy of the user agreement that you opt in to when enabling the integration.This Oracle-Microsoft integration or add-in might enable you to link to or send your content or third-party content to, or otherwise access, or retrieve content from, Microsoft and its platforms, users, or services. Oracle doesn't control and isn't responsible for Microsoft sites or platforms or services, the performance or availability of the services, or any content received or sent. You bear any and all risks associated with access to and use of Microsoft sites, platforms, and services and are solely responsible for entering into and compliance with separate terms between you and Microsoft. Oracle isn't responsible for the security, protection or confidentiality of such content (including obligations in the Hosting and Delivery Policies and Data Processing Agreement and Oracle's Privacy Policy) that's transmitted to such Microsoft sites or platforms or services. You're solely responsible for obtaining or having any required consents or other legal basis for your use of this integration or add-in. Oracle reserves the rights to cancel your connection or integration if your use of this integration or add-in violates the terms of your Agreement(s) with Oracle.