Polar in Microsoft Teams: the work written from the numbers, not from memory.
Microsoft Teams is where the work gets assigned. Connect Polar and an agent reads your governed metrics, then writes the weekly plan and the action items straight into your lists, tagged by priority, owner and channel, on a schedule. Polar is the numbers; Microsoft Teams is where they turn into work.
/Setup Guide
How to Connect Microsoft Teams to Polar.
A Polar account with your stack connected, a Microsoft Teams workspace, and an agent with the Polar MCP and your Microsoft Teams.
01 · What you need
A Polar account with your stack
A Polar account with Shopify and your sources connected. Microsoft Teams gets the same governed metrics your dashboards do.
Connect your data →A Microsoft Teams workspace
A Microsoft Teams workspace and one list or doc where the plan and the action items will land. Start with a single weekly list.
Open Microsoft Teams →An agent with both connectors
An assistant (like Claude) with the Polar MCP and Microsoft Teams connected, so it can read your data and create the tasks in one flow.
02 · Connect Polar and Microsoft Teams to your agent
1
Give your agent the Polar MCP ~2 min
Governed metrics, first-party and sourced.
Connect the Polar MCP to your assistant. It reads your governed semantic layer,
net sales, blended CAC, contribution margin, so every task it writes is grounded in a real number.2
Connect your Microsoft Teams ~2 min
The list it will write to.
1
Point the agent at the Microsoft Teams list or doc it should write to, a weekly planning list, or a growth backlog.
2
It uses two connectors together: Polar for the numbers, Microsoft Teams to turn them into assigned work.
3
Draft and schedule the payoff
Tasks, on a cadence.
Ask once for the weekly plan or for action items tagged by priority, owner and channel. Put it on a schedule and the list fills itself every Monday, before the standup.
push this week's action items into our Microsoft Teams list
create a task for any channel whose CAC moved more than 15%
create a task for any channel whose CAC moved more than 15%
Side by side
Microsoft Teams holds the work. Polar decides what the work should be.
Tasks and lists live in Microsoft Teams, and the numbers that should drive them live somewhere else, so the weekly plan gets written from memory. Polar supplies the governed figures and an agent turns them into tagged, assignable work.
Microsoft Teams on its ownon its own
+Microsoft Teams with Polarblended
The plan is written from memory, not from the data.
Tasks generated from Polar's governed numbers.
Every metric quoted in a task is looked up by hand.
Each item cites the metric that created it.
Someone has to spot a problem before it becomes work.
A task appears when a metric crosses your threshold.
The list depends on whoever filled it in.
The same inputs and the same definitions, every week.
The Gap
The connector is only half of it.
Your agent reads Polar's governed metrics over MCP and turns them into work inside Microsoft Teams: a filled weekly list, tasks tagged by owner and channel, a review doc that cites its numbers. First-party and sourced, never remembered.
Microsoft Teams
the numbers & the list to fill
tasks, tagged and assigned