ORC Integration With Office365 V3
ORC Integration With Office365 V3
DISCLAIMER
This document in any form, software or printed matter, contains proprietary information that is the exclusive property of
Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle software
license and service agreement, which has been executed and with which you agree to comply. This document and
information contained herein may not be disclosed, copied, reproduced or distributed to anyone outside Oracle without
prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any
contractual agreement with Oracle or its subsidiaries or affiliates.
This document is for informational purposes only and is intended solely to assist you in planning for the implementation
and upgrade of the product features described. It is not a commitment to deliver any material, code, or functionality, and
should not be relied upon in making purchasing decisions. The development, release, and timing of any features or
functionality described in this document remains at the sole discretion of Oracle.
Due to the nature of the product architecture, it may not be possible to safely include all features described in this document
without risking significant destabilization of the code.
As shown above, the integration between Oracle Recruiting Cloud and Office 365 is achieved through the Microsoft
authentication API and the Graph API. (https://docs.microsoft.com/en-us/graph/overview)
The authentication between Oracle Recruiting Cloud to the Azure environment is made through an application configured at
the Active Directory level. The system registered application is defining the authentication mode, the security passcode, and
the security access for this application. The application needs the following application privileges:
Calendars.ReadWrite
User.Read.All
With those security privileges, Oracle Recruiting Cloud will get access through REST services to the Active Directory users
and the users calendar using an access token for the specific customer Office 365 Tenant Id. The full details of the
application configuration is described in detail in the section https://graph.microsoft.com/1.0/{resource}?{query-
parameters}
The below flow describes how the free/busy calendar scenario is achieved. Note that the flow represents a high level view
focusing on the integration points between the Fusion Oracle Cloud, the Microsoft Office 365 Cloud API’s and the Customer
Office 365 Azure Tenant.
The Oracle Recruiting Cloud administration is then used to configure the Active Directory application configured keys into
the Oracle Recruiting configuration as described in section
https://login.microsoftonline.com/{tenant}/oauth2/v2.0/token
Those operations are done through REST services passing through the universal Graph API single entry point.
https://graph.microsoft.com/1.0/{resource}?{query-parameters}
The below flow describes how the free/busy calendar scenario is achieved. Note that the flow represents a high level view
focusing on the integration points between the Fusion Oracle Cloud, the Microsoft Office 365 Cloud API’s and the Customer
Office 365 Azure Tenant.
Tokens can be retrieved for the Microsoft API using the configuration application
Active Directory users can be searched through the API integration
The calendar of the admin user can be retrieved
Steps to configure the Office 365 Calendar Integration in Oracle Recruiting Cloud:
1. Log into HCM Cloud.
2. Go to the Setup and Maintenance work area and search for the task Enterprise Recruiting and Candidate
Experience Information.
3. Fill the following information:
Calendar Name Yes The global calendar name that can be used to
write and delete the interview events.
Default Admin User ID No The fallback user ID that can be used to write
and delete the interview events. This user is
used in the case where the original user is not
able to write the event.
4. Press the Validate Integration button to check that the configuration is set up correctly.
a. The validation checks that Oracle Cloud Recruiting can get a token by using the Tenant Id, Application
Id, and Application Password.
b. If the default admin user is defined, the validation will check that this user is in the Active Directory
and that Oracle Recruiting Cloud has access to their calendar.
5. The integration configuration is complete.
Copyright © 2020, Oracle and/or its affiliates. All rights reserved. This document is provided for information purposes only, and the contents hereof are subject to change without
notice. This document is not warranted to be error-free, nor subject to any other warranties or conditions, whether expressed orally or implied in law, including implied warranties
and conditions of merchantability or fitness for a particular purpose. We specifically disclaim any liability with respect to this document, and no contractual obligations are formed
either directly or indirectly by this document. This document may not be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without
our prior written permission.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of
SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered
trademark of The Open Group. 0120