Overview
The OfficePlace & Resource Central Integration Configuration Guide outlines the Step-by-step process for setting up an integration between OfficePlace and Resource Central. Configuration will be done in both OfficePlace and Resource Central.
Step-by-Step instructions
Follow the steps below to configure and set up the OfficePlace & Resource Central integration.
Prerequisite: Customer information for creation of the customer tenant in OfficePlace has been delivered to Add-On Products, who will inform you when the access has been granted.
Step 1: Login to OfficePlace
Begin by launching your web browser and entering the URL of the web server hosting OfficePlace in the address bar: https://admin.officeplace.global/
This will display the OfficePlace login screen as shown below:
Then, log in with your user account credentials provided, which have been assigned the appropriate permissions to access the required sections by Add-On Products. You will then be directed to the Organization Management section where you can view and manage the organizations you belong to, provided you have the appropriate permissions.
Step 2: Configure Entra Applications for Organization
Navigate to the Organization Management section and open the created organization. E.g.:
In your organization, you can configure settings to enable the connection to Azure AD / Exchange Online data for resources and users under the Application tab. The application configurations are necessary to sync data between the Organization and Azure AD / Exchange Online.
The Application Configuration section must be configured by selecting one of the two Permission types that will enable the ability of searching and synchronizing of identity information for users, resources, and groups, as well as calendar details between Entra ID / Exchange Online and your Organization. There are two permission types:
Permission Type | Description |
Delegated | Delegated permissions are granted to an application on behalf of a user. These permissions allow the application to act as the signed-in user, accessing data and resources based on what that user is allowed to do. Refer to this KnowledgeBase article - Azure Application Configuration for Delegated permission type for instructions on how to retrieve the details needed to fill in the fields. |
Application | Application permissions are granted directly to the application itself. These permissions allow the application to access resources or perform actions without the involvement of a user. Refer to this KnowledgeBase article - Azure Application Configuration for Application permission type for instructions on how to retrieve the details needed to fill in the fields. |
After filling in the required fields, you need to retrieve a token from the service account to ensure it has the necessary permissions to access the users, resources, and groups within the application. Click [Get token], and a pop-up window will appear. Enter the service account from your organization's Azure AD tenant to obtain an Access Token for accessing user and group identities, as well as resource calendar and mailbox. Refer to OfficePlace Administrator Guide – Appendix B to learn more about the requirements and rights needed for the service account used in this case.
Once the account is authenticated and authorized, a message will display confirming that the token has been successfully retrieved from that account.
Upon successful token retrieval, click [Save] to apply the configuration settings.
Step 3: Import resources in use within Resource Central to OfficePlace
After successfully configuring the Application tab, you can import groups of resources from Azure AD / EXO that are currently in use within Resource Central to OfficePlace.
To add new group(s) from Azure AD / EXO, click [Import] to open ‘Import groups’ screen.
Here, you can enter their information in the search bar to find groups within your Azure Active Directory (Azure AD) or Exchange Online (EXO) tenant. Click [Next] and the confirmation screen will appear.
Select the group type = Resource of the group by clicking the small arrow beside the group’s name. Click [Next] to finish.
With this, both the group itself and its resources are added to the OfficePlace Organization. Click on the button of a group to see its general information and list of members.
Step 4: Configure integration on OfficePlace
The next step is to set up the connection to your Resource Central application. For this, navigate back to the Tenant Management section, click the button next to your tenant, and then select the Integration Configuration tab to proceed with this step.
4.1. RC Integration
The Disable/Enable button helps configure the integration between Resource Central and OfficePlace. Toggle the button to automatically generate the Metadata Url. Copy this Url for future reference and usage. It is needed under Resource Central → System → Parameters͢ → Basic parameters when setting up Resource Central to connect with OfficePlace.
4.2. Authentication Client Information
In this section, you will create a client application that is used to set up the secure integration between Resource Central and OfficePlace.
On ‘Authentication Client Information’, you can click [Add more] to open the “Create client configuration” screen:
Field | Description |
Type | Type of client application. Select “Token configuration” in this context. |
Name | The name of the client. (required) |
Client ID | This is generated automatically by the system. No action is needed. |
Description | The optional description for the client. |
Client Secret | The password key used to authenticate the client. This is generated automatically by the system; however, you can create a new one by clicking [Generate]. (required)
Note: The created client credential will have its client secret hidden; therefore, make sure that you have copied its client secret before clicking [Create]. |
Expires | The duration for which the client configuration remains active. You can choose from the available expiration date options: limited (a specific number of months), unlimited (no expiration), or customize by selecting a random date of your preference. |
Then click [Create] to finally create this client application. Click [Yes] when the following confirmation emerges.
The created client credential will then be shown below, e.g.:
You can add multiple client secrets to a client credential by clicking [Add more] in Client Secret section. A new client secret is automatically created for you. You can also click [Generate client secret] to retrieve a new one. Then, select expiring duration for this client secret and click [Save].
Copy the values of Metadata Url, Client ID, and Client Secret for using in Step 5:
Step 5: Configure integration on Resource Central
After configuring the integration on OfficePlace side, you need to input the details retrieved in the previous step into Resource Central side to complete the connection between OfficePlace and Resource Central.
Login to Resource Central backend and navigate to SYSTEM → Parameters, then click the [BASIC] button on the toolbar.
The 'Basic Parameters' screen will appear as below:
Select ‘Use OP’ as the Exchange/AD connector and enter the Client ID, Client Secret, and Metadata URL obtained in the previous step. Click on the icon to retrieve data from Metadata Url and the remaining fields will be automatically populated.
Click [SAVE] then.
Step 6: Perform a full sync of resources in OfficePlace
To ensure all meeting data is up to date, you must perform a Full Sync of all resources.
In your organization, navigate to the Sync tab. From the drop-down list, select Sync Calendar where you can check the calendar synchronization status of all resources within the organization and manage their calendar syncing. You can notice that the RC resources that are enabled for OfficePlace to sync from are marked in the “RC Registered” column.
Click the [Full Sync All] button on the toolbar to retrieve the latest data from EXO, regardless of whether there have been any changes to the resource’s calendar or not.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article