Feature · CRM Office 365 Integration

The Microsoft stack, wired into every record.

Teams on Microsoft 365 keep Outlook, Teams, OneDrive, SharePoint, and Entra ID as the daily surface. Strkr lands the Microsoft activity on the record automatically: mail threads, meeting events, shared documents, identity. One Microsoft tenant, one Strkr tenant, one audit trail.

Start free trial See pricing
Outlook mail

Two-way sync with full thread fidelity.

Mail is the thickest activity surface on the record. The Outlook integration syncs sent and received mail against matching contacts automatically, respects the mailbox folder structure, and surfaces threads on the record timeline without rep forwarding. The sync runs through the Microsoft Graph Mail API with delta-change subscriptions.

Delta sync

Changes propagate in under 60 seconds.

The Graph Mail API delta subscription notifies Strkr of mailbox changes within 10 to 60 seconds of the Outlook action. New mail, sent mail, moved mail, deleted mail all propagate. The record timeline updates without the user hitting refresh. The pattern beats poll-based alternatives that run with 15-minute lag windows.

Thread matching

Message-ID preserved across replies.

Mail thread matching uses the RFC 5322 Message-ID header, which Outlook preserves across replies and forwards. One thread with 12 replies renders as one entry on the timeline with the 12 messages collapsed; the user expands to read specific messages. Thread splitting on In-Reply-To breaks is handled; the pattern matches how reps think about conversations.

Attachment surfacing

Files land on the record.

Mail attachments surface on the record attachments tab with the mail reference preserved. A PDF proposal attached to a sent email appears both inline on the thread and in the attachments collection. OneDrive-hosted attachments (common in modern Outlook) retain the link; the file never duplicates into Strkr storage unless the tenant policy requires a copy.

Suppress list

Internal mail does not pollute the timeline.

Internal emails between Strkr users (same tenant domain, no external contact in the thread) do not sync. The posture keeps the record timeline focused on customer-facing activity. Internal threads about an account still exist in Outlook, searchable there; Strkr does not duplicate the internal noise. The suppression respects the tenant domain and the opt-in overrides for specific internal thread patterns.

BCC-to-CRM

Reliable fallback for ad-hoc capture.

Reps who want to capture a thread without full sync (common for sensitive personal threads that should not auto-sync) can BCC a tenant-specific Strkr address. The BCC captures the single thread to the matching record. The pattern coexists with full sync as an opt-in override. For teams running limited-sync policy, BCC-to-CRM is the daily motion.

Shared mailbox

Team inbox mapped to a record.

Shared Outlook mailboxes (support@, sales@, hello@) map to a Strkr queue. Mail to the shared mailbox lands as cases or leads depending on the tenant configuration; replies route back through the mailbox. The pattern supports teams that run inbox-based intake without maintaining a separate CRM capture tool.

Teams calendar

Meeting booking and attendance tracking.

The Teams calendar integration covers meeting booking from the CRM, auto-attendance tracking against the record, and recording link surfacing when the meeting runs through Teams. Reps book meetings without copying links; attendance updates the opportunity activity timeline automatically.

Booking links

Share availability from the record.

Reps share a Strkr booking link from the contact or opportunity record. The link exposes the rep calendar availability (pulled from Entra ID calendar via Graph) and lets the prospect pick a slot. The booking creates a Teams meeting on the rep calendar, generates the meeting link, and writes the meeting event back to the record. No separate booking tool required.

Round-robin

Pool availability across the team.

Teams running inbound round-robin configure a pool booking link. The link exposes availability across the full pool and routes the booking to the next available rep. Routing respects territory, product focus, and current workload. The pattern suits inbound demo booking without an outbound rep manually assigning each one.

Meeting on timeline

The event lands on the record.

When a Teams meeting event binds to a record (via explicit booking or caller-ID match on the attendees), the event appears on the record activity timeline. Pre-meeting the entry shows scheduled details; post-meeting the entry adds attendance (who actually joined, how long) and the recording link if the meeting recorded.

Recording link

Teams recording visible on the record.

Teams meetings that record (per tenant policy or per meeting toggle) write the recording link to the record once the recording finishes processing. Transcripts generate from Teams Premium transcription where the tenant subscribes; otherwise Strkr ASR runs on the recording. The record carries both the audio reference and the searchable transcript.

Reminder flow

Auto reminders 24 hours and 2 hours before.

A booked meeting triggers the Strkr reminder flow: email at 24 hours, SMS at 2 hours (if contact phone is on consent). Prospects who need to reschedule tap the reschedule link in the reminder; the new slot writes back to the Teams calendar and the record. No-show rate on reminded meetings runs lower than on unreminded ones.

Timezone handling

Rep local, prospect local, meeting both.

The booking surface shows the rep availability in the prospect local timezone; the booked meeting shows on both calendars in their respective timezones. Timezone math respects daylight-saving rules per region; a meeting booked in March across DST transitions still lands at the right time on both sides. The pattern avoids the we meant 10 AM eastern, not pacific confusion.

SharePoint and OneDrive

Documents live where the team already stores them.

Teams on Microsoft 365 store documents in SharePoint or OneDrive. The integration surfaces documents on the record without duplicating into Strkr storage. The pattern respects the existing document governance; nothing about the Microsoft side changes for the integration to work.

OneDrive attach

Attach a OneDrive file to the record.

Reps attach a OneDrive file to a record from the Strkr attachment picker. The picker opens a OneDrive file browser; the selected file renders as a card on the record with permission inherited from OneDrive. Clicking the card opens the file in OneDrive natively. The pattern avoids file duplication while keeping the reference on the record.

SharePoint site link

An account site surfaces on the account.

Accounts with a dedicated SharePoint site (common in enterprise service delivery) link the site URL to the Strkr account record. Reps tap the SharePoint card on the account to open the site. For teams running document-heavy sales motions, the pattern keeps SharePoint governance intact while making the site discoverable from the record.

Permission inheritance

OneDrive permissions apply, not Strkr.

Documents stored in OneDrive or SharePoint inherit the Microsoft-side permissions. A rep without SharePoint access to a site cannot open the linked card from Strkr; Microsoft denies the access at the file open. The posture matters for compliance; Strkr does not become a backdoor around Microsoft document governance.

Document search

Microsoft Search across the account.

Strkr Account detail integrates with Microsoft Search for cross-record document discovery. A rep opens an account and sees Microsoft-side documents mentioning the account name, surfaced through the Graph Search API. The pattern catches institutional knowledge that lives in SharePoint but has not been explicitly linked to the record.

Co-authoring

Word, Excel, PowerPoint open live.

Office documents linked to a record open in the Word, Excel, or PowerPoint online editor directly from the Strkr card. Multiple reps editing a shared proposal see Microsoft co-authoring behavior; the integration preserves the native collaboration posture. The alternative of downloading, editing, re-uploading disappears.

Preview

Inline preview without open.

Document cards on the record render Microsoft-side thumbnails. A rep hovers to see a one-page preview of a Word doc or the first slide of a PowerPoint deck. Full-document review opens Microsoft; the preview is for quick glance scenarios. The pattern cuts the do I need to open this friction on busy record pages.

Entra ID identity

SSO, SCIM, conditional access.

Microsoft 365 tenants typically run Entra ID (formerly Azure AD) as the identity provider. Strkr integrates with Entra ID for single sign-on, SCIM user provisioning, and conditional access enforcement. One identity surface governs both the Microsoft side and the Strkr side.

SAML SSO

One sign-in, both systems.

Entra ID SAML SSO authenticates users into Strkr through the Microsoft identity surface. Users click the Strkr tile in their Microsoft My Apps portal or follow a direct Strkr link; Entra ID handles the login; the Strkr session establishes with the Entra ID claims. The pattern eliminates a separate Strkr password for every user.

SCIM provisioning

Users sync from Entra ID groups.

SCIM provisioning syncs user creation, update, and deactivation from Entra ID to Strkr. A new hire joining the sales Entra group auto-provisions into Strkr with the matching role. An offboarding user deactivates on both sides inside the standard sync window. The pattern replaces manual user management on both tenants.

Conditional access

Policy enforced at sign-in.

Entra ID conditional access policies (IP range, device compliance, MFA requirement, risk score) apply at the SSO handshake. A user outside the corporate IP range who has not completed MFA cannot establish a Strkr session until policy satisfaction. The posture matters for teams with strict device-management requirements.

Group-based roles

Entra group membership drives Strkr role.

Strkr roles map to Entra ID security groups. A user added to the Sales Reps group auto-receives the AE role in Strkr. A user moved from Reps to Managers receives the manager role. The pattern lets IT run role assignment through Entra group management rather than through dual-system updates.

Audit sign-in

Every session on the Entra log.

Every Strkr session establishes through Entra ID carries a sign-in entry on the Entra audit log with timestamp, IP, device, risk score. Security teams reviewing suspicious activity reconstruct the full session chain from Entra; Strkr adds its own activity log on top. The dual log posture matters for incident response.

MFA posture

Microsoft Authenticator or FIDO2.

MFA policy sits on the Entra side. Teams using Microsoft Authenticator, FIDO2 keys, or Windows Hello satisfy the Strkr MFA requirement through the Entra handshake. The pattern avoids a separate MFA setup on Strkr; the user memory is one method, not two.

Setup and governance

What installation looks like end-to-end.

A mid-sized Microsoft 365 tenant completes the full integration setup in roughly 90 to 120 minutes. The flow runs through the Microsoft admin consent, the Entra app registration, the SCIM endpoint connection, and the per-user mailbox sync approval. The admin runs it once; nothing on the user side needs retraining.

Admin consent

Three Microsoft Graph scopes.

The Strkr app in the Microsoft Entra marketplace requests three scope groups: Mail.ReadWrite plus Mail.Send for mail sync, Calendars.ReadWrite plus OnlineMeetings.ReadWrite for Teams calendar, Sites.Read.All plus Files.Read.All for SharePoint and OneDrive. The admin reviews and grants scopes at the tenant level; individual user consent is not required.

App registration

Strkr tenant binds to one Microsoft tenant.

One Strkr tenant binds to one Microsoft tenant through the app registration. Multi-tenant Microsoft organizations with separate business units register separate Strkr tenants per Microsoft tenant. The binding writes to the Entra app configuration; disconnection is a one-click revoke on the Entra side.

SCIM endpoint

Entra enterprise app pointer.

The Entra admin configures a SCIM endpoint on the Strkr enterprise app with the Strkr-provided tenant URL and secret. Provisioning runs on the Entra scheduler (default 40 minute cycle). Full-sync completes within the first cycle for small tenants; large tenants (over 5,000 users) complete inside two cycles. The pattern is standard SCIM, not a bespoke Strkr flow.

Mail sync approval

Per-user opt-in or admin override.

Mail sync requires per-user consent by default; the user signs into Strkr once and approves the mailbox sync scope. Admin override lets the tenant admin approve mailbox sync on behalf of users (common in strict IT environments). The posture is a tenant policy decision; both modes are supported.

Data residency

Microsoft region governs storage.

Microsoft 365 data stored on the Microsoft side (mail, documents, meetings) stays in the Microsoft tenant region (US, EU, UK, CA, AU, JP depending on tenant). Strkr-side storage (record metadata, activity log) runs in the matching Strkr region. The two-system posture respects data residency on both sides.

HIPAA posture

BAA chain stays intact.

Teams in healthcare with a Microsoft BAA extend the posture through Strkr with the standard Strkr BAA. The chain of custody runs Microsoft to Strkr with BAAs on both legs. SOC 2 Type II (in progress through 2026-Q4) covers the Strkr side; Microsoft maintains their own SOC 2 posture. The integration surface is auditable on both sides.

Thirty-minute demo on your Microsoft 365 tenant.

Bring your Microsoft admin credentials to a controlled sandbox tenant. We will walk Outlook sync, Teams booking, SharePoint linking, and the Entra SSO handshake live.

Book an M365 demo Explore phone integration
Common questions

What buyers ask about this feature.

Do we need a specific Microsoft 365 license tier for the integration to work?

The integration works with Business Basic and above for mail and calendar sync. SharePoint and OneDrive integration requires any tier that includes those services (most Microsoft 365 Business and Enterprise plans). Teams meeting booking requires Microsoft Teams, included in Business Standard and above. Entra ID SSO works with Entra ID Free (no premium tier required); conditional access policies require Entra ID P1 or above. The license requirements are documented on the Strkr trust center.

How does mail sync handle legal hold and litigation preservation?

Mail stored on the Microsoft side retains the Microsoft retention policy, including Microsoft 365 litigation hold. Strkr-side storage of mail metadata (for the record timeline) respects the tenant-set retention policy on Strkr. For teams with specific preservation requirements, the integration can run in metadata-only mode (sync subject lines and send dates but not body content), which keeps the record timeline informative while preserving the Microsoft side as the single compliance surface for mail content.

Can we integrate with on-premise Exchange instead of Microsoft 365?

The shipped integration targets Microsoft 365 (cloud) via Microsoft Graph. On-premise Exchange users can integrate through Exchange Hybrid configuration where the mailboxes are mirrored to Microsoft 365 for Graph access. Pure on-premise Exchange without any hybrid cloud presence is a professional-services conversation; the technical path uses EWS (Exchange Web Services), which Microsoft has deprecated for new scenarios. The practical guidance is to confirm the hybrid state before planning the integration.

What happens if a user leaves and their mailbox is deactivated on the Microsoft side?

The user deactivation flows through SCIM to Strkr within the standard sync window (one Entra provisioning cycle, typically 40 minutes). The historical mail sync for that user remains on Strkr records; new mail stops syncing because the mailbox no longer exists. Records previously owned by the departed user transfer to a configured backup owner per the tenant offboarding policy. The pattern avoids orphan activity on records after a departure.

Does the integration work for multi-geo Microsoft 365 tenants?

Yes. Multi-geo Microsoft 365 tenants (data residency per user geography) are respected by the integration. Mail for a US-based user stays in the US Microsoft region; mail for an EU-based user stays in the EU region. Strkr-side storage runs in the matching Strkr region for each user. The pattern suits multinational teams with regulatory data-residency requirements on specific geographies.

How does the Teams meeting integration handle Microsoft Teams Rooms (physical meeting rooms)?

Teams Rooms behave as calendar resources on the Microsoft side. The Strkr booking surface can expose Teams Rooms as additional meeting resources when the rep books from a record; the room availability pulls from the Entra resource calendar. On the record timeline, a meeting that ran in a Teams Room shows the room identifier alongside the attendees. The pattern suits hybrid teams running in-person and remote meetings against the same CRM record.

Related features

Pair this with...

CRM Phone Integration CRM Dialer Activity Tracking CRM Document Automation Account Management CRM with Workflow Automation

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.

Start free trial See pricing