Microsoft 365 (Delegation Permission)

Owned by Patrick Terreaux (Unlicensed)
Last updated: Jul 09, 2024 by Amar Zerig
5 min read

Content

Overview

Delegated permissions are used by apps that have a signed-in user present. For these apps, either the user or an administrator consents to the permissions that the app requests and the app can act as the signed-in user when making calls to Microsoft Graph. Some delegated permissions can be consented by non-administrative users, but some higher-privileged permissions require administrator consent.

 

Create a ROOMZ user

 

The ROOMZ Server will read and write information with the meeting room's calendar on Microsoft Exchange using Microsoft Graph. We highly recommend creating a specific ROOMZ user for this purpose.

The created user does not need to have a license.

Access rights & calendar information

The following commands have to be executed using Exchange Online PowerShell with admin rights. Once executed, it might take up to 15 minutes before being effective.

a. Execute the following command and connect to your Microsoft 365 using an admin account.

Connect-ExchangeOnline

If you encounter an error while executing the above command, please click below this message and follow the instructions.

Install or start Exchange Online PowerShell Module. You can install the Module directly in the PowerShell on your Computer:

  1. Update your PowerShell to the latest version by using the following commands:

    winget install --id Microsoft.Powershell --source winget

    Please note that if you had PowerShell V5 before, the new PowerShell V7 will be a new app on your PC, we recommend to use the version 7.x.

  2. Now you can install the Module by the following commands:

    Install-Module -Name ExchangeOnlineManagement

    If you get an error message like the following, you have to allow PowerShell to run scripts:

    After the installation, we recommend to set the policy again to “restricted”:

  3. You need to import the module :

b. In order to provide the access to “roomz-manager” to the agenda of a meeting room, please execute the following command per room: (replace roomz-manager by the name of your ROOMZ user and my-room by the identifier of your meeting room)

Or you can execute the following one which will take all the room mailbox: (replace roomz-manager by the name of your ROOMZ user)

Meeting Title & Private Flag

 

By default, when a user is sending an invitation for reserving a meeting room, Exchange will only store the name of the organizer in the agenda of the meeting room. The meeting's title and the private flag are not stored.

This is the result you will get on a ROOMZ Display, if no setup is changed: 

If you want to show the meeting title, the following PowerShell command has to be executed for each room. When the meeting is considered as 'private', the title of the meeting will be replaced by 'Reserved' on the ROOMZ Display. 

(Adapt the parameter "myRoom@myorganization.fr" to the email address of the desired meeting room)

The following command allows applying the parameter to all rooms :

Once executed, this command will only be effective for the new meetings. When new meeting rooms are created, this command has to be executed again.
Make sure to activate “Show meetings titles” in the Room option set menu. From default, the titles are deactivated:

The title of the upcoming meetings will then be shown:

When a meeting is private, the display will show the information as follows :

Create the booking system in the ROOMZ Portal

 

  1. Login to the ROOMZ Portal and navigate to Global Settings - Booking system and select add booking system, there you select Google (Delegation):

 

  1. Then log in with the account created in step :

 

  1. Click on Add Resource and fill in the Name of the Resource, and the Resource ID (email address of the meeting room).

 

  1. You can click Test all and check the correct setup of your connector.

Everything’s green ? Great !

Something’s not working ? Just click on the Status Indicator to know more about the error

In case of an error, you can easily Edit your Resource and test the connectivity again

Once all the tests are OK you can move on to the next step !

Next Step

 

3 - Device Registration