Skip to main content
Question

Outlook 365 Calendar Integration with Extended Enterprise

  • April 1, 2026
  • 2 replies
  • 6 views

Didn’t find anything in the “related post” link above, but I was curious if anyone here has solved for Outlook 365 calendar integration with multiple Extended Enterprise domains.
The issue we are looking at is how to link different EE Domain users to their respective login page to join the vILT event on the day. 
So far it looks like this will require multiple calendars, and multiple Outlook for Connect recipe sets. 

Does anyone have any other thoughts or suggestions on this?

2 replies

lrnlab
Hero III
Forum|alt.badge.img+10
  • Hero III
  • April 1, 2026

You may be able to do this using some logic + a look up table where the user info needs to be looked to to identify the domain they are in and then use the proper template that contains the base url leading to their domain. This will likely create events for each different domain in your connected outlook calendar though. Not sure if it can all be done with a single template or if you need to customize each one though. Might be worth a try.


Moshe.Machlav
Helper III
Forum|alt.badge.img+1

If you want to manage everything under a single Docebo Connect integration rather than juggling multiple calendars or relying entirely on native notifications, you can absolutely customize the out-of-the-box Connect recipe to handle the domain logic dynamically.

Relying on one "master" recipe is significantly easier for day-to-day operations and ongoing maintenance. You can achieve this by cloning the default Microsoft Outlook 365 recipe in Docebo Connect. Once cloned, you can insert a Lookup Table step or a Docebo API call to dynamically check the user's branch or Extended Enterprise domain. Based on that lookup, the recipe simply swaps the base URL string for the vILT join link before sending the Exchange calendar hold.

The major gotcha to keep in mind: once you clone and customize a built-in Docebo Connect recipe, you essentially "own" it. Docebo's official support typically only covers the out-of-the-box, unmodified recipes. If your custom logic breaks, you will be responsible for troubleshooting it. However, the trade-off is almost always worth it for the operational ease of maintaining a single recipe instead of building a separate one for every domain.

You can find the documentation on how to properly clone and maintain custom recipes (so they don't get overwritten by standard updates) here: https://help.docebo.com/hc/en-us/articles/12445938638098-Docebo-Connect-usage-Copying-recipes

Let me know if you'd like to dig deeper into setting up the Lookup Table mapping.