Sparks with Exchange & SharePoint (without M365)

You use Exchange and SharePoint – self-hosted (on-premise), as Exchange Server/SharePoint Server, or hosted by a provider – without full Microsoft 365? Sparks connects calendar and files; meetings, chat and channels run in Sparks. Identity e.g. via Azure AD, AD FS or another IdP. One interface without dependency on the M365 cloud suite.

Integration with your hosting environment

  • Exchange calendar

    Connect calendar from hosted Exchange in Sparks. Appointments and meetings from one source – multi-backend calendar in one interface.

  • SharePoint / OneDrive

    Use files from SharePoint or OneDrive in Sparks. No duplicate maintenance: your existing file structure stays central, Sparks displays it where you collaborate.

  • Open options

    Sparks complements your Microsoft infrastructure with Matrix chat and E2EE, WebRTC video and EU hosting – so you can gradually gain more sovereignty.

Hosted Exchange and SharePoint provide calendar and files – Sparks is the interface for meetings, chat and channels.

Who is this combination for?

Your own or hosted Exchange and SharePoint (Exchange Server, SharePoint Server or compatible hosted services) 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 and SharePoint for customers or departments. With Sparks you offer a single interface for meetings and chat, without Teams licences or the M365 ecosystem.

  • Hybrid without Teams

    Email and calendar run on Exchange, files on SharePoint – 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 be used alongside existing clients; calendar and files remain the central source.

Technical integration at a glance

Sparks talks to your Exchange (server or hosted) via standard calendar protocols (e.g. Exchange API, CalDAV) and to SharePoint/OneDrive for files. Identity can be provided by Azure AD/Entra ID, AD FS or another IdP. Data stays on your or your hoster’s servers – Sparks is the interface for appointments, files, video and chat.

  • Calendar (Exchange)

    Appointments and meetings are read from your Exchange (Exchange Server or hosted Exchange) and displayed in Sparks. You schedule and start meetings from the same calendar – no double maintenance. Multiple calendar sources (e.g. Exchange + others) can be combined as a multi-backend calendar.

  • Files (SharePoint / OneDrive)

    Files from SharePoint or OneDrive (SharePoint Server or hosted) are embedded in Sparks in channels and chats. Storage remains in your Microsoft infrastructure; Sparks displays and uses the content where you collaborate.

  • Identity (Azure AD, AD FS, IdP)

    User sign-in for Sparks can be via Azure AD/Entra ID, AD FS or another identity provider (e.g. Keycloak). So you fit Sparks to your existing identity infrastructure – whether 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 that uses your existing Exchange and SharePoint infrastructure – without additional Teams or M365 clients.

Request Exchange & SharePoint integration