Strkr dashboards pull Outlook replies, Teams meeting touches, SharePoint document opens, Excel pipeline exports, and Entra sign-in context into the same tile grid your CRM activity, pipeline, and forecast already live on. One revenue view, Microsoft data included, no extra workspace to open.
Every rep lives inside Microsoft 365 all day: Outlook for email, Teams for calls, SharePoint for proposals, Excel for pipeline math. A credible Microsoft dashboard reads those surfaces and renders their signal next to the CRM record of truth. Not a mirror. Not a weekly ETL. A tile grid that shows what happened in Microsoft this hour and how it maps to the open pipeline. The six tile shapes below are the ones Strkr customers pin on day one.
The dashboard reads Outlook sent and received threads via the Microsoft Graph connection, matches them to the Strkr contact and deal records, and renders reply rate as a stacked bar by rep. A sales leader sees who is getting conversations and who is sending into silence. The data refreshes every ten minutes, which is faster than any Power BI cube refresh the IT team is going to schedule.
When a rep schedules a Teams meeting with an external domain, Strkr matches the attendee list to the account and increments the touch count on the open deal. The dashboard tile shows meetings per deal per week, filtered by stage. A manager sees which deals got time this week and which deals went radio-silent, which is the single clearest leading indicator of slip.
The proposal lives on SharePoint. The dashboard reads the audit log for file opens, matches the viewer to the contact record, and shows an open-count by stakeholder for every open deal. A deal where the economic buyer opened the proposal three times last week is a different conversation than a deal where only the champion opened it once. The signal is there in the audit log; the dashboard just surfaces it.
Finance wants the pipeline in Excel. The dashboard ships a scheduled export that writes a formatted .xlsx to a chosen SharePoint folder every Monday morning at 7 AM tenant time. The sheet includes stage age, forecast category, close date, and the Strkr AI risk score. Finance opens Excel, sees the fresh file, and runs their models. No manual CSV dance, no copy-paste from the pipeline page.
For regulated workloads, the dashboard reads Entra sign-in logs for Strkr access and flags anomalies: new countries, new devices, impossible-travel pairs. Security teams get a feed of CRM access context in the same place they already review the pipeline. The pattern turns Strkr into a Microsoft-aligned system of record rather than a separate audit island.
A hidden-until-you-need-it tile shows the health of the Microsoft Graph connection: token freshness, last successful sync per surface, error rate on the last 24 hours. Admins catch an expired token the morning it drifts, not the week a sales leader complains the Outlook reply numbers look off. The health view is the integration-support bar every real Microsoft dashboard eventually needs.
A manager clicks “share brief to Teams” from a deal page. The dashboard renders the deal brief (stakeholders, next step, risk score, last activity) as a Teams adaptive card and posts it to the deal channel. The rep opens Teams, sees the brief, acts on it. No tab-switching into the CRM to find the context, no copy-paste of a bulleted list into a Teams message by hand.
Teams running a sales@ or info@ shared mailbox want each inbound email to become a lead. The dashboard shows the volume by day, the current router rule, and the acceptance rate per owner. Shared mailbox is where Microsoft shops lose leads to inbox silence, and the dashboard puts the metric in front of a sales leader who can fix the routing before another month slips.
If reps work from Word templates on SharePoint, the dashboard counts opens by template and ties outcomes to downstream close rate. The two or three top-performing templates get surfaced; the three or four stale ones get retired. Enablement teams who used to guess which templates were earning their place now see the usage math every morning on the same dashboard that shows the pipeline.
The connection pattern matters more than the demo. A dashboard that mirrors Microsoft 365 data into a shadow warehouse adds a day of latency and a quarter of IT review. The Strkr pattern is a scoped Microsoft Graph app registration with delegated read on the surfaces the tiles need, nothing else. The connection flow below is the one the Microsoft 365 admin walks through on day one, and the one the security review signs off on by day three.
A tenant admin creates one Entra app registration for Strkr, grants Mail.Read, Calendars.Read, Files.Read.All, OnlineMeetings.Read, and AuditLog.Read.All, and consents on behalf of the tenant. No individual rep opts into anything. The grant is explicit, auditable in Entra, revocable in one click, and scoped to the exact surfaces the dashboard tiles need. Nothing broader is requested.
The write path (log an email to a deal) runs under the signed-in user via delegated permissions so audit shows the real actor. The tenant-wide reads (Entra sign-in logs, SharePoint audit) run under application permissions because they summarize across users. Both patterns are documented in the admin console with the exact scope list, so compliance review is a one-paragraph attestation.
Strkr subscribes to Microsoft Graph change notifications on inboxes, calendars, and SharePoint sites. When a reply arrives or a file is opened, Microsoft pushes a webhook to Strkr within seconds. The dashboard tiles reflect the event on the next render. No polling loop drains Graph quota, and the latency on reply-rate tiles is seconds, not hours.
Delegated OAuth refresh tokens renew for 90 days by default and keep rolling as long as the user signs in. Strkr watches the token clock and warns admins the week before expiration on any seat that has not signed in. The warning fires early enough that the token refreshes before the integration drops data, which is the number-one Microsoft-integration failure mode other CRMs ship with.
Privacy and regional law sometimes require per-rep opt-out of email logging. The settings page gives every rep a toggle to disconnect their mailbox from Strkr. The toggle is auditable, the state is per-rep, and the dashboard reflects the opt-out by excluding that rep from reply-rate tiles rather than silently returning blanks. Transparency over the mystery of a missing number.
For Microsoft 365 tenants in EU regions, Strkr routes the Graph calls through EU-hosted inference and reads the EU-hosted copy of the audit logs. The regional pattern is important for GDPR and for the sector-specific regulators who ask about data residency on every HIPAA review. Strkr is HIPAA compliant with a BAA available, and the Microsoft integration honors the same residency contract.
Microsoft Graph enforces per-tenant throttling. Strkr's connector respects the published quota, backs off on 429s, and queues retries. A tenant with 10,000 users does not accidentally burn its daily quota on a dashboard refresh. The connector reports its current quota usage in the Microsoft 365 health tile so admins see headroom at a glance.
Every call Strkr makes against Microsoft Graph lands in the Strkr audit log with the user identity, scope, surface, and response status. If a security team asks “what did Strkr read about this employee last Thursday,” the answer is one query, not a reconstruction from Microsoft audit plus Strkr audit plus timestamp alignment. One audit, one query, one answer.
An admin who revokes the Entra app grant cuts Strkr's access in seconds. The dashboard tiles stop updating with Microsoft data, flag themselves as “integration revoked,” and keep rendering the historical values that already landed in Strkr. No background process keeps reading. No cached token hangs around. The revocation contract is clean.
A blank dashboard is a research project. A starter dashboard with the right six tiles is a tool. Microsoft 365 customers who turn on the integration get three ready-made dashboards cloned into their workspace automatically. Each is editable, savable per role, and intended as a launching point rather than a frozen artifact.
The sales-leader starter blends the Strkr pipeline value tile with Outlook reply rate, Teams meeting count, and the top ten highest-risk deals from Strkr AI. A VP of Sales opens the dashboard every morning and sees the three signals they would otherwise bounce across four tools to assemble. The tile layout is the one most teams keep running without edits for the first quarter.
The rep starter shows the signed-in rep's open deals, today's Teams meetings, the proposals opened by their stakeholders in the last 48 hours, and the Outlook replies that landed overnight. A rep opens Strkr, scans the tiles, and has a ranked morning plan in under thirty seconds. No “where did I leave off” cold start.
The enablement starter ties SharePoint template opens, Outlook template reply rate, and downstream close rate into a single view. Enablement leaders who used to guess which templates were earning their keep see the math every morning. The retire-and-replace cadence shifts from annual to monthly, which is how enablement content stays current.
For the C-suite audience, the summary dashboard reduces each business function to a single tile with a trend sparkline. Sales pipeline, services utilization, finance DSO, HR headcount, each pulled from Strkr or a Microsoft 365 source. The executive opens the dashboard and gets the week in nine seconds. The depth lives behind the click; the surface is deliberately spare.
The marketing starter joins Strkr's campaign attribution to Outlook outbound and Teams meeting touches, so marketing can see which campaigns opened conversations that led to meetings that led to closed revenue. The attribution math is explicit, auditable, and runs on real activity rather than a web-only pixel view that most marketing dashboards still ship with.
For firms running a services arm, the utilization starter counts Teams meeting hours per consultant per week, groups by client, and ties the hours to the Strkr project record. Partners see where billable hours accrued. The tile replaces the weekly timesheet nag email most firms have been sending for a decade.
Microsoft shops typically consider three paths for a sales dashboard: ship Dynamics 365 and use its native Power BI tiles, ship a third-party BI tool on top of a CRM-of-choice, or ship Strkr with the Microsoft 365 integration turned on. The comparison below is the one buyers walk through in week two of evaluation.
Dynamics 365 Sales ships deep Microsoft 365 alignment and the dashboards embed Power BI natively. The honest footnote is that interactive Power BI content inside Dynamics assumes a Power BI Pro license on every viewer, which is $10 per user per month on top of the Dynamics license. For a 50-rep team, the Power BI line alone is $500 a month before the Dynamics seat price lands. Strkr dashboards do not require a Power BI license.
Running HubSpot plus Tableau or Power BI as the dashboard layer adds a license, an ETL, a refresh cadence, and a second audit log. For teams under 200 reps, the operational burden rarely earns its keep. Strkr dashboards live inside the same product as the CRM, which means one audit log, one permission model, and one refresh cadence.
Many Microsoft shops still run the pipeline in Excel. The pattern works at single-digit rep counts and breaks the first time two people edit the sheet in the same hour. Strkr dashboards replace the Excel ritual while still giving finance the scheduled .xlsx export they actually need for downstream models.
Some teams try to turn Teams channels into a pipeline-review surface by piping CRM updates as messages. The pattern works for a week and then the channel noise swamps the signal. Strkr publishes a weekly deal brief to a Teams channel rather than every record change, so the channel stays useful and the tile grid holds the detail.
Operations teams sometimes build dashboard-shaped SharePoint pages. The pages look right for a quarter and go stale by month four as the underlying list formulas rot. Strkr dashboards refresh continuously because the data is live, not a snapshot. The maintenance cost drops to near zero after the initial build.
Microsoft shops often glue CRM to Microsoft 365 with Power Automate flows. The glue works until Microsoft rolls a connector update and the flow fails silently. Strkr ships the integration as first-party code, versioned with the product, which means a Microsoft update does not quietly break a dashboard tile over a weekend.
Security teams at Microsoft shops ask the same seven questions on every CRM review. The answers below are the ones the Strkr admin can paste into the review document on day one.
Strkr is HIPAA compliant and offers a Business Associate Agreement on request. The Microsoft 365 integration honors the same BAA scope: the Graph calls route through infrastructure covered under the BAA, and the audit log retains the identity, time, and scope of each read.
Strkr is actively pursuing SOC 2 Type II with report completion targeted through 2026-Q4. Interim artifacts (controls documentation, penetration test results) are available under NDA. The Microsoft 365 integration is in scope for the audit alongside the core CRM.
Strkr is GDPR compliant with Standard Contractual Clauses in the standard contract and an EU-hosted inference path for EU tenants. The Microsoft 365 integration respects the regional residency contract, which means EU Microsoft tenant data never leaves the EU boundary.
The dashboard tiles are rendered from the same public API endpoints a customer can call directly. There is no privileged dashboard-only data path. A customer who wants to pull the Microsoft 365 reply-rate tile into their own BI tool can do so with a documented API call. Open API, no reverse engineering.
A rep role sees their own Outlook signals. A manager role sees the team's Outlook signals. An admin role sees the tenant-wide health. The role-based access model inside Strkr mirrors the Microsoft Graph scope choices, so a user never sees a Microsoft signal that a Strkr permission would otherwise hide.
When finance exports pipeline to Excel, the field-level visibility model travels with the export. A rep whose role masks the discount-approval reason does not see that column in the .xlsx. The export respects the same permission contract the UI does, which is the single most-missed security requirement in competitor products.
A Microsoft 365 admin consents to the Entra app registration, Strkr pulls the first batch of Outlook, Teams, and SharePoint signals within the hour, and the three starter dashboards clone into the workspace automatically. No Power BI license required, no shadow data warehouse to stand up, no quarter-long integration project. Open a trial and the Microsoft tiles are rendering by lunch.
No. The Strkr dashboard is a first-party tile grid rendered by Strkr, not an embedded Power BI report. Microsoft 365 data flows in via the Microsoft Graph API, and the tiles render inside Strkr with no per-viewer Power BI Pro license required. Teams that want to pipe the same data into Power BI can do so through the open Strkr API, but it is strictly optional.
Outlook mail (reply rate, thread matching to deals), Teams calendar and online meetings (meeting-touch count by deal), SharePoint audit (proposal opens by stakeholder), Excel through scheduled .xlsx export to a chosen SharePoint folder, and Entra sign-in logs for Strkr access anomalies. Each surface is a separately scoped Microsoft Graph permission that the Entra admin grants explicitly, and each is auditable and revocable in one click.
Dynamics 365 Sales ships deeper Microsoft 365 alignment natively, but the dashboards assume a Power BI Pro license on every viewer, which adds $10 per user per month on top of the Dynamics seat price. For a 50-rep team, that line alone is $500 a month before the CRM license. Strkr dashboards include the Microsoft 365 reads in the base price with no Power BI line item. For teams under 500 reps, the Strkr pattern typically consolidates spend and reduces admin burden.
Strkr is HIPAA compliant with a Business Associate Agreement available on request. SOC 2 Type II is in progress with report completion targeted through 2026-Q4, and interim controls artifacts are available under NDA. Strkr is GDPR compliant with Standard Contractual Clauses in the standard contract and an EU-hosted inference path for EU tenants. The Microsoft 365 integration honors the same residency and audit contracts as the core CRM.
Yes. Every rep has a per-user toggle in settings to disconnect their Outlook mailbox from Strkr. When toggled off, the dashboard excludes that rep from reply-rate tiles rather than silently returning blanks, and the opt-out event lands in the audit log. The pattern is important for teams working across regions with different consent regimes.
Delegated OAuth refresh tokens renew for 90 days by default and keep rolling as long as the user signs in. Strkr watches the token clock and warns admins the week before expiration on any seat that has not signed in recently. The warning fires early enough that the token refreshes before the integration drops data, which is the number-one Microsoft-integration failure mode other CRMs ship with. The Microsoft 365 health tile shows the current token status at a glance.
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.
