Foundation
Technical foundations that every Engage platform product — BookMe, Meet, Present, Insights — sits on. The work in this section is done once per tenant; the resulting configuration is reused across products without reconfiguration.
What lives here
| Area | Purpose | Owned by |
|---|---|---|
| Identity | Microsoft Entra ID setup, app registrations, portal authentication (Management Portal, Customer Portal). The identity backbone for staff and customers. | Azure / Entra admin |
| SCIM Provisioning | Push-from-source synchronisation of employees and meeting rooms from your Entra tenant into the platform. Runs on a ~40-minute cycle. | Azure / Entra admin |
| Microsoft 365 | Microsoft Graph integration for Teams meetings, Outlook calendar free/busy, and employee calendar operations. Delivered through the Azure Marketplace App Offer (Graph-Proxy mode) or via direct Graph API access. | Azure / Entra admin |
| Engage Platform Integration Onboarding | The customer-facing onboarding reference. Architecture overview and prerequisites for every integration surface — Foundation surfaces here, plus product-specific surfaces in BookMe/Meet/Present. Start here if you are onboarding a new tenant. | Cross-functional |
How to use this section
If you are onboarding a new tenant:
- Start with the Integration Onboarding Guide for the cross-cutting architecture and the per-surface prerequisites.
- Drill into each Foundation surface (Identity, SCIM, Microsoft 365) for the step-by-step configuration.
- Once Foundation surfaces are configured, move on to product-specific onboarding:
- BookMe Onboarding — CRM (Salesforce) setup and BookMe implementation phases
- Public API — programmatic access for your bespoke systems
Foundation vs product-specific
If you are touching anything in this section, the change typically affects every product on the platform. Product-specific configuration (BookMe portals, Present templates, Meet meeting settings) belongs in the product collections, not here.