Introduction
The External Calendars app connects a Microsoft Outlook account to your platform and keeps calendar invitations for your ILT courses up to date automatically. When a learner or instructor is enrolled in an ILT session, they receive a real calendar invitation for each event of that session. When you change the session later (for example, you add an event, move a date or cancel an event), the invitation is updated or canceled in their calendar. Attendees accept or decline directly from their calendar, and their response is recorded on the session in the platform.
For learners, this means schedule changes always reach their calendar, so they are less likely to miss a session. For instructors, RSVP responses give early visibility on who plans to attend. For your organization, attendance improves while the manual work of coordinating invitations goes away.
The integration creates one calendar event, owned by the connected Outlook account, for each event of a session, and adds the enrolled users or instructors to it as attendees. Each attendee receives the standard invitation, update or cancellation that Outlook generates for that event. The app manages only this organizer-owned event. It never accesses or changes the attendees' own calendars, so learners do not need a Microsoft account, do not need to sign in to anything and do not need to grant access to their calendar. Docebo invites each attendee using the email address stored in their platform user profile, so there is no user mapping to configure. Attendees can respond from Outlook, Google Calendar, Apple Calendar or any other standards-based calendar application.
Microsoft Outlook (Microsoft 365) is currently the only supported provider for the organizer account. The External Calendars app is free and does not require Docebo Connect. If you currently send calendar invitations through Docebo Connect, read Migrating from Docebo Connect before you activate the app, because Connect and the External Calendars app must never manage the same calendar events at the same time.
Setting up the integration happens in two layers. First, in the External Calendars app, you connect one or more Outlook accounts and choose which of their calendars can be used. Then, in the Notifications area, you create an External Calendars notification that defines which sessions send invitations, who receives them, what the invitation says and which calendar sends it. If you already manage notifications, this second part will feel familiar: it is the same notification engine, with a calendar invitation as its output.
Before you start
Choosing the Outlook account
The Outlook account you connect becomes the organizer of every invitation it sends, and its email address is the sender that attendees see. There is no separate sender field to configure. Docebo recommends using a dedicated service account for production use rather than a personal mailbox, sized for the volume of invitations you expect to send (see Microsoft sending and subscription limits).
The connected account must be a licensed Microsoft 365 work or school user mailbox that can sign in directly. Shared mailboxes, resource or room mailboxes, Microsoft 365 group calendars, delegated calendars owned by another user, and personal Microsoft accounts (Outlook.com or Hotmail) are not supported. In particular, do not use an unlicensed Microsoft 365 shared mailbox as the dedicated service account: it has no password for direct sign-in, and Microsoft Graph does not support RSVP webhook subscriptions over delegated shared-calendar permissions. Create a licensed user mailbox for this purpose instead.
You can connect more than one Outlook account. Because each notification chooses its own account and calendar, different business units or use cases can send invitations from different email addresses, as long as each address is connected as its own account.
Microsoft permissions
When you connect an account, you sign in with Microsoft through a standard Microsoft authorization flow. You do not need to create an app registration in Microsoft Entra, and you do not need to provide a client ID or client secret. During sign-in, the External Calendars app requests these delegated Microsoft Graph permissions:
| Permission | What it allows |
|---|---|
Calendars.ReadWrite |
Create, read, update and delete events in the calendars that the signed-in account can access |
User.Read |
Sign in, and read the signed-in account's basic profile |
Please note: If your Microsoft tenant restricts or disables user consent for applications, the person connecting the account cannot grant these permissions on their own. In this case, an authorized Microsoft Entra administrator in your organization must approve them. Check your tenant's consent policy before you start, and especially before you stop any Docebo Connect recipes as part of a migration.
When user consent is restricted
If your tenant blocks user consent, Microsoft stops a standard user at sign-in until a Microsoft Entra administrator authorizes the Docebo app for the organization. The Outlook mailbox that stays connected to Docebo never needs Microsoft Entra administrator privileges: once the app is approved for the organization, any standard licensed Microsoft 365 user mailbox can sign in without administrator permissions.
Take care when the Entra administrator signs in from Docebo. Selecting Consent on behalf of your organization approves the app for every user in the tenant, but the same sign-in also pairs the administrator's own mailbox with Docebo. If that connection is left in place, invitations are sent from the administrator's mailbox instead of the dedicated mailbox.
Choose the approach that matches your tenant.
If your tenant uses the Microsoft admin consent request workflow:
- In Docebo, select Add connection and then Sign in with Microsoft, using the dedicated user mailbox.
- Submit the approval request in Microsoft.
- Ask the Entra administrator to approve the request from Microsoft Entra, without opening Docebo.
- Sign in with Microsoft again in Docebo, using the dedicated mailbox.
If your tenant does not use the admin consent request workflow:
- Ask the Entra administrator to select Add connection > Sign in with Microsoft once with their administrator account, and to select Consent on behalf of your organization. This approves the app for the whole tenant.
- Delete that temporary connection in Docebo straight away, before any notification uses it. Deleting it in Docebo keeps the organization-wide approval active in Microsoft.
- Sign in with Microsoft using the dedicated standard user mailbox to create the real connection.
Who can configure what
Only Superadmins can activate the External Calendars app from the Manage add-ons and integrations page, connect Outlook accounts and choose which calendars are available.
External Calendars notifications follow the same permission model as every other notification. Superadmins can create and manage them, and so can Power Users who have been assigned notification permissions, within the resources assigned to them. Power Users can only select the calendars that a Superadmin has made available. For details, see the Prerequisites chapter of Configuring notifications.
Instructors do not have access to the integration settings or logs.
Activating the External Calendars app
Log in as a Superadmin, then select Navigation menu > Add-ons and integrations (jigsaw icon) > Manage add-ons and integrations. In the Browse apps and features section, select the Third Party Integrations tab, or search for the app. Find External Calendars and select Activate.
Once the app is active, a new External Calendars item appears under Add-ons and integrations (jigsaw icon) in the Navigation menu, and a new External Calendars event type becomes available when you create a notification. You need to activate the app before you can configure any External Calendars notification, and you need at least one connected account before the rest of the app is available.
Best practice: If you do not use Docebo Connect for calendar invitations, you can activate the app ahead of time while you plan your rollout. Activating the app does not send any invitations by itself: nothing is sent until you connect an account, activate a calendar and turn on a notification. If you use Docebo Connect for calendar invitations, activating the External Calendars app stops the Connect integration from working, even before you connect an Outlook account. The Connect calendar invitation options are removed from courses and sessions, and RSVP responses sent by your Connect recipes are no longer recorded in the platform, including responses to events that Connect created before activation. Only activate the app when you are ready to complete the whole cutover in one session, as described in Migrating from Docebo Connect.
Deactivating the app
To deactivate the app, go back to the Manage add-ons and integrations page, select the My Apps tab, open the ellipsis menu in the External Calendars row and select Deactivate.
When you deactivate the app, the integration stops creating, updating and deleting Outlook events, and the External Calendars pages and notification options disappear from the platform. So that attendees are not left with invitations that will no longer stay up to date, Docebo also deletes every managed Outlook event with a future start date. Outlook then automatically sends a cancellation email to the attendees of each deleted event. This is Outlook behavior and Docebo cannot suppress it. The cancellation applies only to the calendar invitation: the ILT session itself stays in the platform, and learners remain enrolled. Past events are not affected.
Please note: When Docebo deletes a future calendar event, it also deletes the RSVP data linked to that event. RSVP data for events that have already ended is kept for audit purposes. If you reactivate the integration later, the future events are recreated as new calendar events with a new identifier, and their previous RSVP responses are not carried over.
Connecting an Outlook account
Select Navigation menu > Add-ons and integrations (jigsaw icon) > External Calendars. This page lists every calendar connection on your platform, with its provider, the user who created it, how many of its calendars are active and its connection status. Use the Search for accounts field to find a connection in the list.
To connect a new account, select Add connection. Choose Microsoft Outlook as the provider, then enter a name for the connection and, optionally, a description to help you recognize it later (for example, "Sales - Microsoft Calendar"). Select Add connection to continue.
Next, select Sign in with Microsoft, choose the Microsoft account to connect (or sign in with a different account) and grant the requested permissions. You can revoke this access from your Microsoft account at any time. When sign-in succeeds, the connection appears in the list with the Connected status. If the connection cannot be completed, the platform shows an error message and does not create the connection. You can try again from the connection list.
If your tenant restricts user consent, read When user consent is restricted in Microsoft permissions before you connect the account. Once the app is approved for your organization, Microsoft silently connects the account that is already signed in to your browser, without asking for credentials. To avoid connecting the wrong mailbox, use a private or incognito browser window when you connect a dedicated mailbox, so that Microsoft asks for the right credentials. The main calendar of every account is called Calendar in Outlook, and the platform does not display the Microsoft email address of a connection, so name each connection after the mailbox it uses.
Docebo refreshes the account's access automatically before it expires. If a refresh fails, Docebo keeps the pending calendar changes in a queue and retries them, and the connection shows a Re-authorize state in the connection list. Sign in with Microsoft again from that connection to restore it.
Managing an existing connection
Select a connection name in the list to open its details. From there, you can:
- Rename the connection or change its description, from Manage connection > Edit details.
- Choose which calendars of that account are available to notifications, in the Calendars section (see Selecting calendars).
- Update the list of calendars with Refresh calendars, if a calendar was recently added to or removed from the account in Outlook.
- Deactivate every calendar of that connection at once, from Manage connection > Deactivate all calendars. This stops invitations from all its calendars and deletes their future events, together with the RSVP data linked to those future events. Past events and their RSVP data are kept.
- Disconnect the account, with Unpair in the row menu of the connection list. Unpair has the same effect on the calendars as Delete: it deactivates all the active calendars of the connection, deletes their future events from Outlook (so Outlook sends a cancellation email to their attendees) together with the RSVP data linked to those future events, and removes the Microsoft Graph subscriptions. The only difference is that the connection stays in the list in an unpaired state, whereas Delete also removes the connection from the list.
- Delete the connection with Delete. Deleting an account has the same effect on its calendars as deactivating the app: Docebo deletes the future events managed by that account's calendars, and Outlook sends a cancellation email to their attendees.
Please note: If one of these actions affects a calendar that an active notification uses, the platform warns you before you confirm and gives you a link to the affected notifications. Review them first: deactivating or removing a calendar in use stops its invitations and deletes its future events.
Selecting calendars
Connecting an account does not make all of its calendars available. Open the connection and, in the Calendars section, select Activate next to each calendar that notifications should be able to use. Only active calendars appear when you configure a notification. Exposing only the calendars you need also keeps the list short and relevant for Power Users who manage notifications.
Each time you activate a calendar, the platform shows a reconciliation prompt. This prompt is used when you migrate from Docebo Connect, and it appears whether or not you have ever used Connect. If you have never sent calendar invitations for your ILT sessions from this calendar, skip it. If you are migrating, follow Migrating from Docebo Connect.
When you activate a calendar that supports RSVP, Docebo subscribes to Microsoft Graph notifications for that calendar. If the subscription cannot be created (for example, because the mailbox has reached its subscription limit), the calendar is not activated. If a calendar remains inactive after activation, check the available Microsoft Graph subscriptions for the mailbox and try again.
Please note:
- RSVP responses are only synchronized back to the platform for events created on the connected account's default Outlook calendar. You can still send and update invitations from any other calendar of the account, but Microsoft Graph does not send attendee responses for non-default calendars, so the RSVP status of those invitations never reaches the platform. This is a Microsoft limitation. For events created on calendars that do not support RSVP, Outlook shows invitees a note stating that no response is requested. The Accept, Decline and Tentative buttons remain visible as per Microsoft Outlook standard behavior. Responses given on these events are not synced to Docebo. If you need RSVP tracking from more than one mailbox, connect several accounts and use the default calendar of each one.
- Deactivating a calendar stops its upcoming invitations and deletes its future events, together with the RSVP data linked to them. Past events stay visible, but their RSVP responses can no longer be managed. If you reactivate the calendar later, its events are recreated with a new identifier and no previous RSVP history.
Setting the domain used in invitation links
Each calendar has its own domain setting, which you open from the edit icon next to the calendar. Docebo uses this domain only to build the {{session_link}} shortcode in that calendar's invitations, so that learners land on the right branded portal. The options depend on how your platform is set up:
| Platform setup | Domain options |
|---|---|
| No custom domain and no extended enterprise | The option is hidden, and links use your docebosaas.com address |
| Custom domain, no extended enterprise | Your custom domain (default) |
| Extended enterprise active, with or without a custom domain | Your docebosaas.com address, your custom domain (if you have one) and all your extended enterprise secondary domains |
Changing a calendar's domain, or your platform's main domain, updates the links in all the future events that use that calendar.
Please note: The calendar domain does not filter who is invited. Every invitation always includes all the users enrolled in the session, whatever their branch or domain. If a single session mixes users from different branches under one notification, all of them receive the same link domain, and it is not possible to route attendees of the same session to different domains. Using separate calendars is not enough on its own. If different audiences need different branded links, place them in separate sessions (or separate copies of the course, where this makes sense for your organization), then create a separate notification for each audience, each one using a calendar set to that audience's domain.
Example: Your platform has two extended enterprise domains, one for employees and one for partners, and both audiences attend the same ILT course. First, create one session for employees and one for partners. Next, activate two calendars, one with the employee domain and one with the partner domain. Then create two External Calendars notifications: the first targets the employee session and uses the employee calendar, and the second targets the partner session and uses the partner calendar. Each audience now receives links to its own portal.
For extended enterprise links to work properly, enable the Enable extended enterprise login restriction option, so that a learner who selects the link is taken to the session page on their own branch's domain. See Managing the Extended enterprise app. The External Calendars app does not support the "subfolder" option of extended enterprise. The subfolder option is the only way to enable extended enterprise without a secondary domain, so to use the app with extended enterprise you must have at least one secondary domain configured. If you activate extended enterprise after you have already set up your calendars, the domains already selected on those calendars do not change; the new domains simply become available to select from then on.
Creating an External Calendars notification
Connecting an account only makes calendars available. Nothing is sent until you create a notification that says which sessions trigger invitations, who receives them, what they say and which calendar sends them.
Select Navigation menu > Configuration (spanner icon) > Automation > Notifications and select the + icon in the top right corner. In the Create notification panel, set Courses as the Event category and External Calendars as the Event type. Enter a descriptive Name for the notification, then select Create and edit.
The notification configuration page has four tabs: Properties, Extra settings, Recipients and Trigger filters. You can select Save changes at any point to save a partial configuration.
Properties: choosing the calendar
In the Properties tab, under Calendar, select the Enable calendar as delivery channel check box, then choose the calendar that sends this notification's invitations. The account that owns this calendar becomes the organizer and sender of the invitations.
After you save the notification for the first time, the account and calendar become read-only. To send from a different calendar later, duplicate the notification from the notification list. The duplicate is created inactive, with the account and calendar unlocked. Select the new calendar in the duplicate and activate it: Docebo creates the invitations on the new calendar. Then deactivate or delete the original notification: Docebo deletes its future events from the old calendar, and Outlook sends a cancellation to their attendees. Attendees therefore receive a cancellation from the old calendar and a new invitation from the new one.
Properties: writing the invitation
Below the calendar, write the invitation. It has a subject in plain text, up to 255 characters, and a message body in HTML, written with the built-in editor. You can add shortcodes to both. Shortcodes use the double curly bracket format, for example {{course_name}}. Conditional statements are not supported, so you cannot show or hide part of the message depending on a value. If a shortcode has no value for a specific event (for example, {{location_name}} for an event with no location), it is replaced with an empty string.
These shortcodes are available for External Calendars notifications:
| Shortcode | Replaced with |
|---|---|
|
The ID, title and description of the course |
|
The ID, name and description of the session |
|
The ID, name and description of the event |
|
Classroom if the event has only a location, Webinar if it has only a videoconference tool, Hybrid if it has both |
|
The videoconference tool assigned to the event, if any |
|
The details of the event location, if any |
|
The details of the event classroom, if any |
|
Whether the event has a location or a classroom |
|
A link that signs the learner in and takes them to the session |
The {{session_link}} shortcode takes the learner straight to the session, already signed in, using the domain set on the calendar. The link does not enroll anyone: a user who is not enrolled in the session and selects the link sees a message saying they are not enrolled. A learner who accesses the platform through this link is counted as an active user.
The Classroom, Webinar and Hybrid labels of {{event_type}} can be translated, and Superadmins can change them.
Please note:
- There is no shortcode for the list of instructors of an event. Instructors can receive invitations (see Recipients), but instructor names cannot be inserted in the invitation text.
- Each notification has a single template, which applies to every course and session it covers. You cannot vary the template, the sender or the branding by branch, group or individual learner within the same notification. If different audiences need different wording, branding or senders, create separate notifications scoped to separate courses or sessions, each with its own template and calendar. Make sure that no course or session is covered by more than one of these notifications for the same recipient role, otherwise the users enrolled in it receive two invitations.
Invitation language
All the recipients of a notification receive the invitation in the same language: your platform's default language. If the invitation is not available in the platform default language, Docebo uses English. The learner's profile language, the course language, the Multi-language course property and the Session language field have no effect on the invitation language.
Please note: Calendar invitations cannot be translated per attendee. Docebo creates a single calendar event for all the attendees of a session event, and neither Outlook nor other calendar providers can adapt one event's invitation to each attendee's language. Docebo also cannot send a separate, translated companion email to each attendee through this notification.
Extra settings: hiding attendees
By default, depending on the calendar application, attendees may be able to see who else is invited. In the Extra settings tab, turn on Hide attendees so that each attendee sees only themselves in the invitation, while the organizer account still sees everyone. This option uses Outlook's own hide attendees setting. If you change it while the notification is active, Docebo updates the existing future events accordingly.
Please note: Hiding attendees is not guaranteed in every calendar application. Attendees who open the invitation in Outlook see only themselves, but attendees who open the same invitation in Google Calendar may still see the other attendees. This is a limitation of Outlook's hide attendees setting, and the platform shows a reminder banner next to the option. Keep this in mind for sessions where privacy between attendees matters, such as sessions with external audiences or with people from several companies.
Recipients: users or instructors
In the Recipients tab, choose whether the invitations go to the enrolled users or to the instructors of the covered sessions. You can select only one recipient role per notification. To invite both users and instructors to the same sessions, create two notifications, one with Users as recipients and one with Instructors.
Trigger filters: which courses and sessions send invitations
In the Trigger filters tab, choose whether the notification applies to all ILT courses and sessions or to a custom selection. With a custom selection, you can select specific courses (with all their sessions), specific courses with only some of their sessions, or specific sessions only.
When you change the trigger filters of an active notification, Docebo creates calendar events for the future session events that are now covered, and deletes the future events that are no longer covered. Past events are not affected.
When you duplicate a course, the copy (with any sessions and events you chose to duplicate) is not added to the trigger filters of the original course's notification, and the duplication itself does not create any Outlook events. Docebo starts sending invitations for the copy only once you add it to the trigger filters of an External Calendars notification. If a notification already covers all ILT courses and sessions, the copy is covered automatically.
Please note: You can save a notification whose trigger filters overlap those of another active External Calendars notification. When you do, the platform shows a warning that identifies the overlapping courses or sessions and the other notification, but the save still completes. If the same session is covered by two active notifications, its attendees receive duplicate invitations, so you are responsible for making sure each session is covered by only one active notification per recipient role.
Turning the notification on
When every tab is configured, open the notification and use the status button in the bottom right corner of the configuration page to switch it to Active. Activating the notification starts a batch creation: Docebo creates invitations for everyone currently enrolled in the covered sessions, for every event that ends on or after the activation date. Events that are still in progress are included. Events that ended before activation are not created.
Best practice: Activating a notification on a large, heavily enrolled selection of sessions sends a large number of invitations at once from a single mailbox. To stay within Microsoft's sending limits, consider activating in phases, for example by starting with a smaller trigger filter selection and extending it later, or by spreading the load across notifications that use different accounts.
Deactivating or deleting the notification starts a batch deletion: Docebo deletes every future calendar event that the notification manages, and Outlook sends a cancellation to each attendee. The RSVP data linked to the deleted future events is deleted too. Past events and their RSVP data are not affected.
Editing an active notification
When you change the template, the recipients, the trigger filters or the Hide attendees option of an active notification, or the domain of the calendar it uses, Docebo updates the affected future events. For example, if you change the template, every future event of the notification is updated, and attendees receive an updated invitation. Updates that only change information, such as a new room or a new description, do not reset attendees' RSVP responses, so attendees do not need to respond again.
Please note: For most notification types, it is recommended to deactivate a notification before editing it. Do not do this with an External Calendars notification: deactivating it deletes all its future calendar events and sends cancellations to every attendee, and activating it again sends new invitations with no previous RSVP responses. Edit the active notification directly instead.
How invitations stay synchronized
Once a notification is active, Docebo listens for changes on the courses and sessions it covers and updates the related Outlook events. The table below shows how common platform actions affect the calendar.
| Action in the platform | Effect on the calendar |
|---|---|
| A user is enrolled in a session | The user is added as an attendee of the session's events |
| A user is enrolled in the course but not in a session | Nothing happens: only session enrollment adds attendees |
| A user is unenrolled from a session, or their enrollment is archived (including when this happens through a learning plan unenrollment or archiving) | The user is removed from the attendees |
| Users are enrolled through a bulk enrollment job | The calendar event is updated once, with all the new attendees, after the whole job completes |
| A course, session or event is updated (for example, a new date, time, name or description) | The invitation is updated |
| The instructors of a session or event change | The invitation is updated only if its subject or body changes. If your notification does not use the related shortcodes, nothing changes. |
| A location, classroom or videoconference tool is assigned to an event, or changed on the event | The invitation is updated |
| The details of an existing location or classroom are edited in Classroom locations | Existing invitations are not guaranteed to be updated |
| A videoconference tool account is deleted | Existing invitations are not updated |
| An event or session is deleted or canceled | Only the related calendar events that have not started yet are deleted, and only the attendees of that session receive a cancellation. Past events stay in attendees' calendars and receive no cancellation. Other sessions of the course are not affected. |
| A canceled session is restored | The calendar events are created again, and attendees receive new invitations, so they need to respond again |
| A course is deleted or archived | The related calendar events that have not started yet are deleted, and attendees receive a cancellation. Past events stay in attendees' calendars and receive no cancellation. An event that is already in progress counts as started, so it is not canceled. |
| A course is duplicated | Nothing happens until the copy is added to a notification's trigger filters |
| A user's email address changes | The invitations are updated with the new address |
| A user is deactivated or deleted | Nothing happens immediately; the user is removed from the attendee list the next time the event is updated |
| The notification template changes | All the notification's future events are updated |
| The platform main domain or the calendar domain changes | The links in the affected future events are updated, and the invitations are updated as a result |
Changes made in Docebo (session creation or updates, enrollments, unenrollments) are not synced to Outlook in real time. Allow around 5 minutes for changes to appear. Bulk actions, such as mass enrollments, may take longer depending on the number of users and sessions involved. To avoid sending attendees a burst of almost identical updates when several changes happen close together, Docebo can group changes for up to 15 minutes before updating the calendar.
Please note: A deactivated or deleted user stays on the attendee list until the event is next updated. Because they can no longer access the platform, this has no practical effect.
Tip: There is no manual resend or test-send option for calendar invitations. If you need to push an update to a calendar event again (for example, after fixing a problem), make a change to the event, session or course details, or to the notification message. Docebo then updates the related calendar events.
RSVP responses
Attendees respond to the invitation from their own calendar application. Docebo records Accepted and Declined responses, as well as the absence of a response, in the RSVP column of the session's Enrollments and evaluations tab. To see it, select Navigation menu > Content and delivery (folder icon) > Courses > [course name] > [session name] and open the Enrollments and evaluations tab. From the ellipsis menu in an attendee's row, select RSVP overview to see their response for each event. Tentative responses are not recorded.
RSVP responses are separate from attendance and completion. An accepted invitation does not mark the learner as present; you still track attendance as usual.
Responses reach the platform through notifications that Microsoft sends when an attendee responds, rather than through periodic checks, so they arrive faster than with the Docebo Connect integration.
Docebo only records responses from users who are enrolled in the session. Responses from anyone else are discarded silently and do not appear as errors in the logs. This includes:
- people who received a forwarded invitation but are not enrolled in the session
- users who were unenrolled after the invitation was sent
- responses sent from a user's previous email address, after their email address changed in the platform
If an event is deleted in the platform but its Outlook event is left behind, Docebo detects the leftover Outlook event when a response for it arrives and deletes it.
Please note:
- RSVP responses are only synchronized for invitations sent from the connected account's default Outlook calendar. See Selecting calendars. Invitees of events on other calendars can still see the Accept, Decline and Tentative buttons in Outlook, but their responses are not synced to Docebo.
- The organizer account never receives its own Accept or Decline response from Outlook. If the connected organizer account is also enrolled in a session, its RSVP status stays Awaiting. This is expected Outlook behavior, and it does not affect RSVP synchronization for other attendees.
- The integration uses the same RSVP data as before, linked to the session event, and does not add an RSVP field to the learner's enrollment or any new reporting options. RSVP responses are not available in reports, cannot be exported from the platform interface and do not have a dedicated API endpoint. You can view them in the session's Enrollments and evaluations tab.
Microsoft sending and subscription limits
Mailbox sending limits
Docebo creates, updates and deletes the calendar events, but Outlook sends the resulting invitations from the connected mailbox. These invitations therefore count toward that mailbox's standard Exchange Online limits: 30 messages per minute and 10,000 recipients in a rolling 24-hour period. One event with 50 attendees counts as one message toward the per-minute limit and as 50 recipients toward the daily limit. For example, sending invitations to 17,000 people from a single standard mailbox exceeds the daily recipient limit.
These are Microsoft limits on your mailbox, and Docebo cannot override them. When a mailbox goes over a limit, Exchange Online usually delays the excess messages rather than dropping them, but the exact behavior depends on how Microsoft applies its limits at that moment.
For normal training volumes, a properly sized service account is enough. If you send very large or very frequent invitations, spread the load across several connected accounts and calendars, and activate large notifications in phases. Avoid using a single standard mailbox as a high-volume sender, which is the pattern Microsoft recommends against.
Please note: Microsoft's High Volume Email (HVE) service does not help with calendar invitations. HVE only applies to email sent over SMTP, while the External Calendars app manages events through Microsoft Graph, and Outlook sends the invitations itself.
Attendee limit per event
Microsoft Outlook supports up to 5,000 attendees per calendar event. We recommend keeping sessions within this limit, as Microsoft does not guarantee the behavior of events that exceed it.
Microsoft Graph subscription limits
Each activated calendar uses one Microsoft Graph change-notification subscription, which is how Docebo receives RSVP responses. Microsoft allows up to 1,000 subscriptions per mailbox, and other integrations that use the same mailbox share that capacity (in the same way, Docebo's subscriptions reduce the capacity left for those integrations). Docebo currently supports up to 100 activated calendars for the External Calendars app within one paired Microsoft tenant. A Microsoft Teams tenant paired with your platform also uses one subscription. If you plan to activate a large number of calendars, check your current Microsoft Graph subscription usage before you start. If you reach these limits, new calendars cannot be activated (see Selecting calendars).
Monitoring activity
Open a connection from Navigation menu > Add-ons and integrations (jigsaw icon) > External Calendars and select the Logs tab to see what the integration has done over the last 60 days. The log lists each creation, update and deletion of a calendar event. Each entry has a description of what the integration did.
To export the log, select Export. The platform prepares a CSV file in the background and notifies you when it is ready to download.
When a temporary problem occurs (for example, Microsoft is briefly unavailable), Docebo retries automatically, waiting a little longer between each attempt. You can also choose up to five platform users who receive a notification when the integration reports a technical error.
Configuration changes, such as activating or deactivating the app and creating or authorizing a connection, are recorded in the audit trail together with the user who made them. To view them, select Navigation menu > Data and analytics > Audit trail.
Tip: If a log entry shows an error that automatic retries could not resolve, fix the cause first (for example, reconnect an account in the Re-authorize state). Then make a change to the affected event, session or course, or to the notification message, so that Docebo updates the calendar event again.
Migrating from Docebo Connect
If you already send calendar invitations for ILT sessions through a Docebo Connect recipe for Outlook, you can move to the External Calendars app without losing your existing calendar events. Connect and the External Calendars app must never manage the same events at the same time, so the move is a controlled cutover: you prepare everything while Connect is still running, then complete all the remaining steps in a single, planned session. Doing the steps out of order can delete events you meant to keep.
If you do not use calendar invitations today, none of this applies to you. Follow the setup from Activating the External Calendars app.
There is no requirement to migrate immediately. Docebo Connect calendar integrations remain supported, and you can move on your own timeline.
Before the cutover
While your Connect recipes are still running, make sure that:
- the Outlook account you plan to connect is ready and sized for your invitation volume
- the person who will connect it can grant the Microsoft Graph permissions listed in Microsoft permissions, or has already obtained approval from a Microsoft Entra administrator
- any custom behavior your Connect recipes provide is covered by the External Calendars app, because the move cannot be undone in a standard way (see the note at the end of this chapter)
- you have planned a time when you can complete every step below in one session
Completing the cutover
First, stop every Connect recipe that creates, updates, deletes or synchronizes RSVP responses for calendar events. This freezes Connect so it cannot change or delete Outlook events during the cutover. Do not disable the Connect calendar invitation (RSVP) settings in your platform while any of these recipes is still running: turning them off can trigger Connect's own cleanup, which deletes the existing Outlook events.
Next, activate the External Calendars app. Activating the app is not a preparation step: from this moment the External Calendars app is the calendar integration in use, and the Connect calendar invitation settings are no longer used. Only activate it when you are ready to finish the remaining steps.
Please note: Activating the External Calendars app stops the Connect integration from working immediately, even before you connect an Outlook account. The Connect calendar invitation options are removed from courses and sessions, and RSVP responses sent by your Connect recipes are no longer recorded in the platform, including responses to events that Connect created before activation. Complete all the remaining steps in the same session.
Then connect your Outlook account and select the calendars you need, as described in Connecting an Outlook account and Selecting calendars.
When you activate a calendar, the reconciliation prompt appears. Choose to run the reconciliation. Docebo scans the Outlook events that Connect created in that calendar, matches each one to its session event in the platform and registers it so that the External Calendars app manages it from now on. The existing events are not deleted or recreated, so attendees do not receive new invitations for them.
Finally, create and activate your External Calendars notifications, as described in Creating an External Calendars notification. Reconciliation does not create them for you. Make sure their trigger filters cover both the sessions whose events were reconciled and the future sessions you want invitations for. When you activate the notifications, Docebo uses the reconciled events instead of creating duplicates. The content of a reconciled event is not changed when you migrate: it keeps what your Connect recipe sent until the event is first updated. From then on, all invitations, including updates to reconciled events, use the new notification template, regardless of what your Connect recipes sent before.
What reconciliation carries over
| Carried over | Not carried over |
|---|---|
| The existing Outlook events that were matched to a session event, and the link between each event and its session event | Connect recipes, invitation templates, trigger selections, recipients, the Hide attendees setting and the account and calendar selections. Recreate these in your External Calendars notifications. |
Please note:
- You can skip the reconciliation, but it is strongly recommended if you have upcoming events that Connect created. Skipped events are not managed by the External Calendars app: they stay in attendees' calendars but are no longer updated or canceled, and activating your notifications can send attendees a second, parallel invitation for the same event.
- Moving to the External Calendars app is one-way for reconciled events. Once reconciled, those events are managed by the External Calendars app, and deactivating the calendar, the notification or the app deletes them. Connect cannot take them back or recreate them automatically. Returning to Connect would mean deleting all the events managed by the External Calendars app, setting up Connect again and recreating every event from scratch by triggering all the affected enrollments again, which requires a procedure specific to your platform. Contact Docebo if you think you might need this, before you start the migration.
Security and data protection
This section summarizes how the External Calendars app handles your data when it connects to Microsoft Outlook.
What the app accesses and stores
The app processes the data it needs to create and maintain calendar events: the identity of the organizer and the connection details, the calendar IDs and metadata, the event content, the invitee email addresses and their RSVP responses, and the app configuration, mappings and operational records. The app does not add any HR data.
Authentication and permissions
The app connects to Microsoft through the Docebo multi-tenant Microsoft application, using the OAuth 2.0 authorization code flow. It uses delegated permissions: calendar read and write access (Calendars.ReadWrite) at calendar level, and basic profile access (User.Read).
Restricting the app to the calendars you select is enforced by Docebo, not by Microsoft. For this reason, we recommend that you connect a dedicated service account that has access only to the calendars you want to use.
Your Microsoft Entra administrator may need to approve the application. This approval is a technical authorization and is separate from any consent required by privacy law: you are the data controller and Docebo is the data processor. You can revoke the app's access at any time from Microsoft.
How data is protected
OAuth tokens are stored encrypted at rest, are refreshed automatically and are masked in logs. Docebo runs a vulnerability management program, and security incidents are handled in line with the Data Processing Agreement (DPA).
Retention and deletion
- When you deactivate a notification or disconnect an account, the future events managed by the app are removed from Outlook.
- Past events remain in Outlook, and past RSVP responses remain in Docebo.
- When you disconnect an account, the change notifications that Docebo subscribed to for that calendar are removed.
- The app logs are kept for 60 days.
AI, hosting and subprocessors
The app has no AI or LLM component. It runs on AWS and uses Datadog for logging. It introduces no new subprocessors, so your existing DPA applies. Microsoft is your own tenant.
Assurance
The Docebo SOC 2 Type 2 report covers the period from 1 August 2025 to 31 July 2026 and is available at trust.docebo.com (opens in a new tab). The External Calendars integration was released after this observation period, so it is not yet individually covered by the report.
More information
For more information about security and data protection, contact your Customer Success Manager or Docebo Support.
Known limitations
| Limitation | What to do |
|---|---|
| Microsoft Outlook is the only supported organizer provider | Attendees can still use any standards-based calendar application |
| RSVP responses are not synchronized for non-default calendars, even though Outlook still shows invitees the Accept, Decline and Tentative buttons | Use the default calendar of each connected account when you need RSVP tracking |
| The organizer account's own RSVP stays Awaiting | Expected Outlook behavior; no action needed |
| Tentative responses are not recorded | Only Accepted and Declined responses are recorded |
| Hide attendees does not hide the list in every calendar application | Take this into account for privacy-sensitive sessions |
| One recipient role per notification | Create one notification for users and one for instructors |
| One template and one language per notification | Create separate notifications for audiences that need different content, and make sure each course or session is covered by only one active notification per recipient role, otherwise enrolled users receive two invitations |
| No shortcode for the instructor list | Add instructor details to the event or session description instead |
| The link domain cannot vary within one session | Use separate sessions, notifications and calendars per domain |
| Editing a location or classroom record does not reliably update existing invitations | Make a change to the affected events to update them |
| Deleting a videoconference tool account does not update existing invitations | Assign a new videoconference tool to the affected events |
| Bulk enrollment updates the calendar only when the job ends | No action needed; the event is complete once the job finishes |
| Changes are not synced in real time (about 5 minutes; longer for bulk actions) | Allow time for changes to appear in Outlook |
| Outlook supports up to 5,000 attendees per calendar event | Keep sessions within this limit; Microsoft does not guarantee the behavior of larger events |
| A calendar is not activated if the Microsoft Graph subscription cannot be created, and no error message is shown yet | Check the available Graph subscriptions for the mailbox, then activate the calendar again |
| No manual resend or test send | Make a change to the event or the notification message to trigger an update |
| RSVP responses are not in reports, exports or the API | View them in the session's Enrollments and evaluations tab |
| Exchange Online sending limits apply to the connected mailbox | Use properly sized accounts, spread the load and activate in phases |
| Up to 100 activated calendars per paired Microsoft tenant | Activate only the calendars you need |
| The connected account must be a licensed Microsoft 365 user mailbox that can sign in directly | Do not use shared mailboxes, resource or room mailboxes, Microsoft 365 group calendars, delegated calendars owned by another user or personal Microsoft accounts (Outlook.com, Hotmail) |
| Migration from Connect is one-way | Validate your Connect use cases before you start |