Configure Outlook Calendar
Prepare the Microsoft application connection required for staff Outlook calendar event actions. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
What you’ll accomplish
Prepare the Microsoft application connection required for staff Outlook calendar event actions. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How the module flow works
The Outlook integration uses configured Microsoft application identity values and MSAL-based authentication actions.
Staff authorisation is required before the module can create, update or delete calendar events.
The connection is separate from Google and can be used according to organisational calendar policy.
Follow these steps
- Create or identify the approved Microsoft application.
- Enter the required client/application configuration in Appointments settings.
- Authorise the staff Microsoft account.
- Create a test Outlook event from an appointment.
- Check update and delete behaviour.
Fields and decisions to review
How to confirm it worked
After this workflow completes, Britixo keeps the appointment and its supported relationships connected. Reopen the appointment and verify the saved status, date, timezone, customer or lead, service, provider, attendees, reminder state, calendar or meeting reference, invoice reference and history that apply to this feature. External email, SMS, Google, Microsoft or payment outcomes must be checked separately from the Britixo database save.
- Open the saved appointment and confirm the final status and source.
- Check the participant, provider, timing and timezone from the full detail page.
- Review the relevant table filter, calendar, history, report or linked invoice instead of relying only on a success message.
Controls, checks and common mistakes
- Use the exact redirect address configured in Microsoft.
- Do not store secrets in public documentation.
- Test tenant policy and consent requirements.
- Use the least destructive correction and retain the appointment history when the booking existed operationally.
- Never bypass a permission, availability, approval, client-access or verification control by changing an unrelated route or setting.
