Microsoft Outlook Plugin

PlaceOS Provide a plugin for Microsoft Outlook to facilitate room bookin

Adding Outlook Plugin to PlaceOS

The Outlook Plugin is treated like a normal Frontend Repository in PlaceOS Backoffice.

To add the plugin, you will require administrator access to PlaceOS. You can follow the instructions below or reference the Deploy a Frontend Interface document.

  1. Navigate to the Repositories tab in Backoffice.

  2. Create a new Repository.

  3. For repository name enter: Outlook Plugin

  4. For repository URL enter: https://github.com/placeos/user-interfaces

  5. For repository branch enter: build/outlook-rooms-addin/prod

  6. For folder name enter: outlookplugin

  7. Ensure repository type is set to Interface

  8. You should now be able to pull the repository and reference it in domains as outlookplugin i.e. https://company.placeos.com/outlookplugin/

  9. If configured correctly, the URL should load the frontend and redirect to Microsoft Authentication.

Create API Endpoint in Azure

To enable the application to authenticate and return a user token to PlaceOS, we need to create an API Endpoint in Azure App Registrations.

If you have previously configured Azure App Registrations for PlaceOS Room Booking or Calendar integration, you can simply add the endpoint to the existing App Registration on Azure.

Add Azure API Endpoint

These instructions are taken directly from Microsoft Documentation: Configure Azure AD App for Office add-in.

  1. Login to Azure Portal

  2. Navigate to Azure Active Directory -> App Registrations.

  3. Select the PlaceOS User Authentication app registration.

  4. Add a new scope, configure it with the following details:

    • Scope Name: access_as_user

    • Who can consent: Admin & Users.

    • Admin consent name: Access User and Room Calendars.

    • Admin consent description: All the app to read the user calendar and calendars of rooms the user has permission to view/book.

    • User consent name: Access User and Room Calendars.

    • User consent description: All the app to read the user calendar and calendars of rooms the user has permission to view/book.

  5. Click Add Client Application

  6. Add the following clients:

    • d3590ed6-52b3-4102-aeff-aad2292ab01c (Microsoft Office)

    • ea5a67f6-b6f3-4338-b240-c655ddc3cc8e (Microsoft Office)

    • 57fb890c-0dab-4253-a5e0-7188c88b2bb4 (Office on the web)

    • 08e18876-6177-487e-b8b5-cf950c1e598c (Office on the web)

    • bc59ab01-8403-45c6-8796-ac3ef710b3e3 (Outlook on the web)

Add Redirect URI

To ensure we can obtain the user token after authentication, you will need to register a redirect URI.

  1. Login to Azure Portal

  2. Navigate to Azure Active Directory -> App Registrations.

  3. Select the PlaceOS User Authentication app registration.

Update Manifest File

We will need to tell Exchange your users require permissions, this must be included with the manifest.xml file which also includes the Azure App Registration API Endpoint.

  1. If it does not already exist, add a <WebApplicationInfo> element to your manifest after the closing </Resources> tag.

  2. Set the <Id> element to your App Registrations Client ID.

  3. Set the <Resource> element to the API endpoint URL provided in the API section of your App Registration.

  4. Add a <Scopes> element which includes profile, openid and User.Read

Example:

      <WebApplicationInfo>
        <Id>client-id</Id>
        <Resource>api://placeosdomain.com/client-id</Resource>
        <Scopes>
          <Scope>profile</Scope>
          <Scope>openid</Scope>
          <Scope>User.Read</Scope>
        </Scopes>
      </WebApplicationInfo>

Generate the Manifest File

To deploy the plugin to Microsoft Exchange, a Manifest File detailing the location and parameters of the application is required.

PlaceOS is able to automatically generate and serve the manifest file once you have created the API Endpoint in Azure.

To generate the manifest file, follow these steps:

  1. Navigate to PlaceOS Backoffice.

  2. Select Manage Instance from the left menu.

  3. Select Staff API.

  4. Use the drop down list to select the domain you are intending to deploy the plugin to.

  5. You should already have a Staff API Registration if you have previously integrated PlaceOS with Microsoft Services. If not you can refer to the documentation on Configuring Staff API.

  6. Edit the Staff API Registration.

  7. Enable the Configure Outlook Plugin checkbox.

  8. Enter the App ID from your Azure API Endpoint.

Register Plugin with Exchange 365

In order for the plugin to work effectively with your organisation and to allow users to add the plugin to Outlook, it must be registered in Exchange 365 Admin.

To complete these steps you will require administrator access to Exchange 365.

Register the Custom App

  1. PlaceOS provide a manifest.xml file with the user interface, in the Custom App settings select the Provide Link to Manifest file option and enter your manifest.xml URL.

  2. You can click Next and Finish the Wizard.

Update the Custom App

If PlaceOS make changes to the plugin, the manifest.xml file version will be incremented and these changes may be updated in the custom app.

Follow the same steps to access the Custom App under Integrated Apps in Exchange 365, then:

  1. Select the Custom Room Booking app.

  2. Provide your manifest.xml URL Path.

  3. Click Update.

  4. Any changes in the manifest.xml will be applied and the plugin will be updated.

Add Plugin to Outlook

If the instructions are followed correctly, shortly after registering the custom app the plugin will become visible to users in Outlook Mc & Windows.

PlaceOS will either automatically generate the Manifest file or you will be provided with a correctly formatted manifest file to upload.

  1. In Outlook, Navigate to the Tools Menu and select Get Add-ins

  2. In the add-in window, select Admin-Managed.

  3. Select the Room Booking Add-in tile.

Last updated