> For the complete documentation index, see [llms.txt](https://ieg4.gitbook.io/edesigner-new/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ieg4.gitbook.io/edesigner-new/building-services/adding-content/microsoft-bookings-items.md).

# 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 <IEG4Council@ieg4.com>
* Directory (tenant) ID                    eg 9688d675-\*\*\*\*\*\*\*\*\*\*\*\*\*\*
* (Application) client ID                  eg a4db50fe-\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
* Client secret                                 eg GTa\*\*\*\*\*\*\*\*\*\*\*\*
* Username                                     eg <edesignerbookings@ieg4.com>
* 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.*&#x20;

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**

<figure><img src="/files/lbWkFMpxxsSqMMgjSOqK" alt=""><figcaption></figcaption></figure>

#### 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>

<figure><img src="/files/y9BdWwh09NBREKcm9ZTR" alt=""><figcaption></figcaption></figure>

#### Add a client secret.&#x20;

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

<figure><img src="/files/VDGJjKB6GKnKuHDFJM4h" alt=""><figcaption></figcaption></figure>

#### Configure the permissions

From the API permissions tab, add the following permissions

<figure><img src="/files/0UEy0JYbMvgcJWbgzyJn" alt=""><figcaption></figcaption></figure>

#### Configure the App roles

From the App roles tab create a role as below

<figure><img src="/files/XIUoStUuHihQNx2F0viz" alt=""><figcaption></figcaption></figure>

### 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

<figure><img src="/files/J6XPRN4cHn8yFJ3LEJof" alt=""><figcaption></figcaption></figure>

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

<figure><img src="/files/hn6PgkLYQfJSKVos9QmX" alt=""><figcaption></figcaption></figure>

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

<figure><img src="/files/mvoiqHtQ2CytGj7M7dWM" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ieg4.gitbook.io/edesigner-new/building-services/adding-content/microsoft-bookings-items.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.