Current + Microsoft 365 integration

Your team already lives in Microsoft 365. Current connects through Microsoft Graph so project work shows up where people already work — in SharePoint, Teams, Outlook, and To Do — instead of forcing everyone into yet another tab. The integration is scoped, permissioned, and built to keep documents and conversations tied to the right project.

SharePoint project folders

Current can create and link a SharePoint folder structure for a project, so proposals, network diagrams, statements of work, and deliverables have a consistent home. Shared documents can be surfaced to partners through the client portal without ever exposing financials — partner document access is isolated at the database layer, not just hidden in the UI.

Teams channel mirroring

Project conversations don't have to be reinvented. Current mirrors project activity into a Teams channel so the people delivering the work see updates in the tool they check all day, and the discussion stays attached to the project record rather than scattered across DMs.

Two-way Outlook Calendar

Scheduling in Current respects real availability, and Outlook Calendar sync is two-way: project milestones and scheduled work can appear on a technician's calendar, and time booked in Outlook feeds back so the plan reflects what people are actually doing. Combined with Current's PTO- and availability-aware scheduling, that means the timeline is honest about who is free.

Microsoft To Do sync

Tasks assigned in Current can sync to a technician's Microsoft To Do list, so day-to-day work lands in a personal task list people already use. It closes the gap between the project plan and the individual's actual to-do list.

Entra ID single sign-on

Current supports Microsoft Entra ID SSO, so your team signs in with the identity you already manage. That means centralized access control, easier onboarding and offboarding, and no separate password to reset.

The Microsoft 365 connection uses a shared multitenant Azure app and standard Graph permissions. You control which capabilities are turned on, and everything a partner can see through the portal is governed by row-level security, so financial data never leaks through a shared SharePoint folder or a mirrored Teams channel.

What it actually connects

• SharePoint document libraries, so project files live where your team already works rather than in a second place.
• Teams channels tied to projects, so conversation and delivery stay together.
• Outlook calendar, so real meeting load is visible against project schedules.
• Microsoft To Do, so tasks reach people in the tool they already have open.
• Mailbox capture for the CRM, so customer email lands against the right company automatically.
• Microsoft Entra ID single sign-on.

The To Do boundary worth knowing

Project task sync to Microsoft To Do is deliberately one-way. Tasks flow out to To Do so an engineer sees them alongside everything else, but checking one off in To Do does not complete the underlying project task. That is intentional: completing a project task can move dates, notify a client, and trigger downstream scheduling, and none of that should happen from a checkbox in a personal task list that was ticked by accident.

Permissions and revocation

The connection uses delegated permissions granted by your Microsoft admin, and can be revoked from Microsoft at any time without touching Current. Mailbox capture is scoped and can exclude specific mailboxes, which matters because not every mailbox in an MSP should feed a CRM.

Why it matters

Most project tools ask your team to work somewhere new. Connecting the tools people already have open all day is usually the difference between a project system that gets updated and one that goes stale in a fortnight.