Best Practices for the Integration
Here are some important things to keep in mind when implementing the Oracle Sales Redwood UX for the Microsoft 365 Integration add-in:
- Don't connect a single Microsoft email account to two instances of the Sales application. This can cause data to get cross-synchronized between the two Sales application instances.
- Don't model employees as contacts. Model them as sales resources. The application isn't designed to handle a person modeled as both an employee and a contact at the same time.
- Create separate applications for each Sales application instance in Microsoft Azure. In the application, add the users who are going to access the add-in of the instance. Deploy the manifest file from the corresponding instance into the Microsoft portal.
- Don't use the same email account against different instances, such as your stage environment and your production environment.
- Make sure the time zones settings match between Microsoft Outlook and Oracle Sales.
Important: If you're migrating the CX Sales for Microsoft 365 integration to the
Oracle Sales Redwood UX for Microsoft 365 integration, there are specific steps for the
migration. See the Migration Overview and Migration Best Practices topics for
more information.