Microsoft 365

Most enterprise intelligence tools are built for Google Workspace users and ported to Microsoft as an afterthought. The Teams connector ingests messages. The SharePoint connector pulls files. The Outlook integration syncs calendar. Each one bolted on separately, none of them aware of the others.

BASAL treats Microsoft 365 as a first-class stack from the start.

What happens when you connect

Run basal connect --microsoft and BASAL begins reading across all five surfaces simultaneously.

Outlook calendar events don't become a list of meetings. Each event becomes a structured node: attendees resolved to known identities, attached files linked to the event, and whether a Teams meeting link signals a recorded session. When a recording appears in OneDrive after a call, BASAL finds it within 30 minutes and routes it through the same transcript extraction that processes Google Meet recordings.

Outlook email threads become commitment chains. When a VP writes "we'll have the proposal to legal by end of week," that sentence lands in the knowledge graph with a timestamp, a sender, and a recipient. BASAL doesn't watch for a follow-up to confirm it was delivered. It tracks the thread and notes when nothing arrived.

Teams channels carry context that email doesn't. Project decisions made in a Teams channel — the ones buried in reply threads that nobody scrolls back to find — get extracted alongside the document they referenced in the tab. BASAL reads both and links them.

SharePoint and OneDrive documents don't get indexed as files. Each document gets matched to recent calendar events by title proximity and time window. A proposal deck uploaded the day before a quarterly review isn't just a file on OneDrive — it's the evidence for what was said in that room.

Planner tasks complete the picture. When a Teams discussion produces an action item that becomes a Planner task, BASAL connects the chain: the conversation that created the commitment, the task that formalized it, and the due date that's now two weeks past.

The same intelligence, your stack

Every capability that BASAL delivers for Google Workspace users applies without modification to Microsoft 365:

• Entity resolution across Outlook contacts, Teams users, and SharePoint permissions
• Timeline reconstruction from email threads, meeting notes, and document edits
• Commitment tracking from email bodies, chat messages, and Planner tasks
• Relationship mapping from who attends what, who co-authors which documents
• Knowledge graph growth from calendar, communication, and document signals

At 30 days, BASAL has a working model of your organization's active relationships. At 90 days, it surfaces patterns across all five surfaces that no search in any single Microsoft app would find.

For hybrid organizations

Many organizations run both stacks. A sales team on Google Workspace, an engineering team on Microsoft 365, a finance team that somehow uses both. BASAL reads them in parallel. A commitment made in Gmail and referenced in a Teams channel lands in the same knowledge graph, with both sources cited.

The knowledge boundary is your organization, not your tool vendor.