Microsoft Bookings items

Microsoft Bookings

Configuration required by the customer

This describes the process of getting the credentials required for eDesigner forms to read and write to a customers Microsoft Office 365 Calendars and Bookings APIs

The settings we require are:

• Booking Business eg [e-mail]

• Directory (tenant) ID eg 9688d675-**************

• (Application) client ID eg a4db50fe-*****************

• Client secret eg GTa************

• Username eg [e-mail]

• Password eg TN#***********

The Booking Business is the email of your business in Microsoft Bookings

To create the rest of the settings log in to the Azure portal

Part 1 – Create an App Registration

For the next three settings you need to create an App registration

Registering your application establishes a trust relationship between your app and the Microsoft identity platform.

In the Azure Portal go to Azure Active Directory -> App registrations -> New registration

Enter a display Name for your application. Users of your application might see the display name when they use the app, for example during sign-in. You can change the display name at any time and multiple app registrations can share the same name. The app registration's automatically generated Application (client) ID, not its display name, uniquely identifies your app within the identity platform.

Specify who can use the application, sometimes called its sign-in audience. Select: Accounts in this organizational directory only

Don't enter anything for Redirect URI (optional). You'll configure a redirect URI later.

Select Register to complete the initial app registration.

Once created, go the the Overview of the App registration where you will find the (Application) Client ID and the Directory (tenant) ID

Add a Redirect URI

A redirect URI is the location where the Microsoft identity platform redirects a user's client and sends security tokens after authentication.

You just need https://login.microsoftonline.com/common/oauth2/nativeclient

Add a client secret.

From Certificates & secrets, and a new Client secret. The secret Value is needed for the Client Secret setting

Configure the permissions

From the API permissions tab, add the following permissions

Configure the App roles

From the App roles tab create a role as below

Part 2 – Create a User

For the final two settings you need to create a user.

The Username setting is the ‘user principal name’ and the Password is the login password

For this user, under Applications, add the Graph explorer application

And for Licenses, add the assignments of Azure Active Directory and Microsoft 365