Office 365 client_id missing #21725
Replies: 1 comment
-
Hi @inside-mo! I'm Dosu and I’m helping the cal.com team. The Office 365 client_id for a self-hosted cal.com instance isn't set through the UI or environment variables. Instead, you need to add it directly to your database, specifically in the Prisma app table, under the slug office365-calendar. The integration code fetches the client_id from there during the OAuth process, and if it's missing, you'll see the error you described. There’s no built-in admin interface for this, so you’ll need to insert or update the record manually in your database. You’ll also need a client_secret in the same place for the integration to work properly. You can see how this is handled in the code here. To get a client_id and client_secret, you’ll need to register an application in the Azure Portal (Microsoft’s developer portal for Office 365/Outlook integrations). Once registered, copy the Application (client) ID and client secret, then update your cal.com database accordingly. Let me know if you need step-by-step instructions for the Azure registration or the database update! To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I was directed to GIthub via help@cal.com. Here's my issue: I installed a self-hosted version of cal.com and now wanted to connect my Outlook calendar with it, which resulted in this error message popping up after clicking on "install": Office 365 client_id missing.
Fair enough, but where exactly do I configure this Id? I checked all the settings and, unless I’m overseeing something, I couldn’t figure out where to put it (provided I can actually get one 😊).
Beta Was this translation helpful? Give feedback.
All reactions