Sparks with Exchange SE & SharePoint Server

Integration with your hosting environment

• Exchange SE / EWS calendar

  Read and write calendar via Exchange Web Services (EWS) – including RSVP. Appointments and Sparks join links from one source; multi-backend calendar in one interface.

• Outlook add-in

  Users keep Outlook at their desk: the Sparks add-in inserts online meeting links into Exchange appointments – no separate Sparks app required for scheduling.

• SharePoint Server on-prem

  Use files from SharePoint Server (checkout, versions, search) in Sparks. Separate from the Graph/M365 file path – your farm remains the source.

• Parallel M365 + on-prem

  Microsoft Graph (M365) and Exchange SE / SharePoint Server can be active as providers at the same time – e.g. hybrid migration or separate departments.

Who is this combination for?

Exchange Server / Exchange SE and SharePoint Server are often used in public authorities, mid-sized companies or data centres – without full Microsoft 365 or without Teams. Sparks provides the missing communication layer: video, chat and channels, displayed with your calendar and files.

• Data centre or hosting partner

  You host Exchange SE and SharePoint Server for customers or departments. With Sparks you offer a single interface for meetings and chat, without Teams licences or a full M365 ecosystem.

• Hybrid without Teams

  Email and calendar run on Exchange (EWS), files on SharePoint Server – but you don’t want the Teams app. Sparks uses the same data sources and replaces Teams as the client for meetings and collaboration.

• Migration or complement

  You’re planning a switch or complementing your Microsoft environment. Sparks can run alongside M365 Graph and existing clients; calendar and files remain the central source.

Technical integration at a glance

Sparks talks to Exchange SE via EWS (calendar, mail, contacts) and to SharePoint Server via REST (files, checkout, versions, search). Identity via Entra ID, AD FS or another IdP. Optional Office Online Server for in-browser edit. Data stays on your or your hoster’s servers – Sparks is the interface for appointments, files, video and chat.

• Calendar (Exchange SE / EWS)

  Appointments and meetings are read and written via EWS (including RSVP; series support follows). Sparks join URL in the appointment body. Multiple sources (e.g. Exchange on-prem + M365 Graph) can run in parallel as a multi-backend calendar.

• Files (SharePoint Server)

  Files from SharePoint Server are embedded in Sparks in channels and chats – including checkout/checkin and versions. Separate from the Graph channel path; storage remains on your farm.

• Identity (Entra ID, AD FS, IdP)

  User sign-in for Sparks can be via Entra ID, AD FS or another identity provider (e.g. Keycloak). So you fit Sparks to your existing identity infrastructure – cloud, on-premise or hybrid.

• Video, chat and channels in Sparks

  Meetings run via WebRTC in Sparks, chat and channels via Matrix. So you have a full collaboration interface on your Exchange/SharePoint infrastructure – without additional Teams clients.