Rhythms connects with Microsoft Planner to automatically track task progress in your OKRs. Once connected, Rhythms pulls the latest data from your Planner plans, keeping your Key Results and Initiatives up to date without manual check-ins.
New to auto-updates? The How to Set Up Auto-Updates article covers the complete setup workflow, OAuth security, and what auto-updates can and can't do.
What You'll Connect
When you set up the Microsoft Planner integration, Rhythms AI helps you locate and configure tracking for:
Planner plans organized by team or project
Task completion based on whether tasks are marked complete
Checklist completion based on the percentage of checklist items completed within tasks
The setup conversation guides you through finding relevant plans and selecting the right tracking approach for your goal.
Before You Connect
Workspace Administrator Setup
Your workspace administrator needs to enable the Microsoft Planner integration before you can connect. See [LINK: Enable Integrations for Your Workspace] for workspace-level setup instructions.
β οΈ The Microsoft Planner integration requires your workspace to have MCP integrations enabled. If you don't see Microsoft Planner as an option when setting up auto-updates, ask your workspace administrator to enable it.
Microsoft Administrator Approval
Your IT administrator must grant consent for Rhythms to connect with your organization's Microsoft Planner data:
Step 1: Share this link with your IT Administrator
Step 2: Your IT Admin will:
Sign in and review permissions (read Planner plans, tasks, and profiles)
Click "Accept" to grant consent
β Once approved, all users in your organization can connect
Step 3: Connect your account
Click "Enable" below and sign in with your Microsoft 365 account
Start tracking Planner data in your OKRs
Access Requirements
You need:
A Microsoft 365 account with access to your organization's Planner plans
At least view permissions for the plans and tasks you want to track
Plans and tasks must be visible to you in Microsoft Planner
When you connect, Rhythms requests these Microsoft permissions:
Group.Read.All - Read your organization's Planner plans
Tasks.ReadWrite - Access Planner tasks (read-only despite the name)
User.ReadBasic.All - Read basic profile information for assignees
offline_access - Maintain connection between sessions
How to Connect Microsoft Planner
The setup process is covered in detail in How to Set Up Auto-Updates. Here's what's specific to Microsoft Planner:
Guide Rhythms to Your Plan
After authentication, the assistant opens a chat window to help locate the right plan. Instead of navigating through Microsoft Planner yourself, you describe what you want to track in natural language.
Example conversations:
"Track task completion in the Q1 Marketing Campaign plan"
"Monitor progress in the Engineering Sprints plan based on checklist completion"
"Calculate percentage complete for tasks in the Product Launch bucket"
The assistant searches your accessible Planner plans to find matches. It confirms what it found and asks clarifying questions if needed (like which bucket to focus on or which team members' tasks to include).
Rhythms analyzes your goal's title and description to recommend plans that might be relevant, marked with a sparkle icon. You can select a recommended plan or search for any plan you have access to.
Choosing Your Tracking Method
Rhythms offers two ways to calculate progress from Planner tasks:
Task Completion (default) Tracks the percentage of tasks marked as complete in the plan. A task counts as complete only when marked 100% done in Planner.
Checklist Completion Tracks the average percentage of checklist items completed across all tasks. This provides more granular progress tracking when teams use checklists to break down work.
Choose the method that best reflects how your team measures progress in Planner.
Optional: Filter by Bucket, Assignee, or Task
You can narrow which tasks count toward progress:
Filter by buckets: Track only tasks in specific buckets (for example, "Sprint 1" or "Design Phase")
Filter by assignees: Track only tasks assigned to specific team members
Filter by specific tasks: Track a manually selected set of tasks
If you don't apply filters, progress includes all tasks in the plan.
After You Connect
What Gets Updated Automatically
Once connected, Rhythms syncs with Microsoft Planner daily at 3 AM UTC. The sync updates:
Task completion percentages
Checklist item completion (if using checklist tracking)
Progress calculations based on your selected method
Progress history over time
What You Still Provide
Auto-updates handle the numbers, but you still provide context through check-ins. Use check-ins to explain:
Why progress changed or didn't change
Blockers or risks affecting your plan
What's coming next
How the numbers relate to your goal
See Effective Check-ins to Track OKR Progress in Rhythms for guidance on combining automated data with meaningful context.
Current Limitations
Microsoft Planner tracking works well for straightforward progress measurement, but has some constraints:
Progress Tracking
Task completion is binary. Tasks count as either 0% complete or 100% complete. Planner's partial completion percentages (like 50% done) aren't reflected in Rhythms progress calculations.
All child tasks are included. When tracking a plan, progress calculations include all tasks that match your filters. You cannot filter by task labels, even though the setup interface shows label options.
Sync Timing
Updates happen once daily. Rhythms syncs with Planner at 3 AM UTC each day. Changes made in Planner won't appear in Rhythms immediately. Plan for a delay of up to 24 hours.
Configuration Changes
You cannot edit settings after setup. If you need to change which plan you're tracking, which filters you're using, or your tracking method, you must disconnect and reconnect. When you reconnect with new settings, progress history from before disconnection is preserved but there will be a gap during the change.
To test new settings: Set up the new configuration on a different Key Result first to verify it works as expected before disconnecting your active tracking.
Scale Considerations
Plans are limited to 1,000 tasks. If a plan contains more than 1,000 tasks, Rhythms can only retrieve and track the first 1,000.
Large organizations may see slower initial searches. If your organization has many Planner plans, the initial search during setup might take longer as Rhythms analyzes all accessible plans to find matches.
Team profile loading varies by size. Organizations with many team members (20+) might experience slightly longer loading times when displaying assignee information during setup.
What This Means for Your Goals
These limitations don't prevent tracking progress, but they do affect how you structure your approach:
Choose plans that naturally contain the scope you want to track
Use Planner's bucket structure to organize work into trackable segments
Consider manual check-ins when you need more complex filtering or real-time updates
For partial completion tracking, use checklist-based tracking instead of task completion
If these limitations affect your workflow, let us know through the feedback option. We're evaluating enhancements based on user needs.
Adjusting Your Connection
You cannot modify your Planner connection settings after setup. If you need to change your plan, filters, or tracking method, follow the disconnect-and-reconnect process described in the parent article: How to Set Up Auto-Updates.
Important: Test new configurations on a separate Key Result before disconnecting your active tracking to avoid unexpected results.
Frequently Asked Questions
Can I connect the same Planner plan to multiple Key Results?
Yes. Multiple people can connect the same plan to different Key Results or Initiatives. Each connection is independent and doesn't affect others.
What happens if I lose access to the Planner plan?
Auto-updates will stop when Rhythms can't access the plan data. Reconnect with a plan you can access, or switch to manual check-ins.
Can I connect both Planner and another tool to the same Key Result?
No. Each Key Result or Initiative can have one auto-update connection at a time.
How often does Rhythms sync with Planner?
Once daily at 3 AM UTC. Changes in Planner can take up to 24 hours to appear in Rhythms.
What if progress doesn't match what I expected?
First, verify your filters in Planner. If you filtered by bucket or assignee, make sure the right tasks are in those buckets or assigned to those people. Remember that label filtering isn't currently supported, even though it appears in the setup interface.
If you're using task completion tracking, verify that tasks are marked 100% complete in Planner. Partial completion percentages (like 50% done) aren't reflected in Rhythms.
If you're using checklist tracking, verify that checklist items are marked complete within the relevant tasks.
Can I track multiple Planner plans in one connection?
No. Each connection tracks a single plan. To track multiple plans, set up separate auto-update connections on different Key Results or Initiatives.
Does Rhythms modify tasks in Planner?
No. Rhythms only reads data from Planner. It never creates, updates, or deletes tasks, checklists, or plan information.
Why can't I filter by labels even though they appear in the setup interface?
Label filtering is shown in the interface but not currently functional in the backend. Use bucket or assignee filters instead, or track plans that naturally contain your desired scope.
Can I track time-based metrics like "Complete all tasks within 48 hours"?
No. Planner tracking focuses on completion counts and percentages, not time-based metrics. For deadline-based goals, consider manual check-ins or tracking in tools designed for time metrics.
Related Articles
How to Set Up Auto-Updates - Complete auto-update workflow, OAuth security, and reconfiguration process
Enable Integrations for Your Workspace - Workspace administrator setup for Microsoft Planner integration
Effective Check-ins to Track OKR Progress in Rhythms - How to combine automated data with contextual updates
Understanding OKR Automatic Rollup - Why Objectives use rollup instead of direct auto-updates
