Using FluentBooking with Outlook Organizational Accounts

For several months, I've heard that FluentBooking doesn't work with organizational accounts on M365 or Outlook.com. It's been a pain in the neck, but I have a client's M365 accounts working correctly.

I wanted to share how I resolved the Microsoft Outlook calendar integration issue when standard, non-admin Microsoft 365 users encounter the "Admin consent required" block.

Because FluentBooking is an unverified multi-tenant application, Microsoft Entra ID blocks standard users by default unless the tenant administrator configures specific permission classifications and application settings.

Here is the process that allows standard users to connect their Outlook calendars without needing administrative roles:

1: Add the required permissions to the low-impact classification list.

In the Microsoft Entra admin center, go to Identity, then Applications, then Enterprise applications, then Consent and permissions, and open Permission classifications.

Under the Low classification, add the delegated Microsoft Graph permissions that FluentBooking requests:

Calendars.ReadWrite
User.Read
offline_access
openid
profile
email

2: Grant initial tenant consent as an administrator.

An administrator must trigger the connection once from an admin account. When the Microsoft consent prompt appears, accept it so the FluentBooking service principal registers inside the tenant Enterprise applications list.

3: Adjust the enterprise application properties.

In Enterprise applications, select FluentBooking and open Properties. Set Assignment required to No and save. This prevents Entra ID from blocking users who do not have an explicit app role assigned.

4: Have standard users connect from a clean browser session.

After these tenant settings propagate, standard users must use a fresh private or incognito window to connect their calendar under FluentBooking Host Settings. This clears any cached token sessions that previously failed with error 90095.

Once completed, calendar sync, conflict detection, and automated event creation work reliably for standard users.

Hopefully this helps your team assist other customers running into Microsoft 365 tenant consent issues.