TL;DR - Quick Answer
Microsoft Teams doesn’t save status history natively. You cannot check when someone was online yesterday or view past presence data using Teams’ built-in features.
Solution: Use a third-party presence tracking tool like The Green Dots that polls the Microsoft Graph API every 2 minutes and stores historical presence data.
Can You Check Teams Status History?
The Short Answer: No (Natively)
Microsoft Teams does not provide a built-in way to check someone’s status history. The Teams app only shows:
✅ Current real-time status (Available, Busy, Away, Offline) ✅ Custom status message (if set) ✅ Last activity timestamp (sometimes, inconsistently)
❌ NOT available: Historical status data ❌ NOT available: When someone was last online yesterday ❌ NOT available: How long they were in meetings ❌ NOT available: Patterns of availability over time
Why Doesn’t Teams Save Status History?
Technical reasons:
- Data volume: Storing presence changes for millions of users would be massive (288 data points per user per day)
- Privacy concerns: Microsoft doesn’t want to be seen as “tracking” employees
- Real-time focus: Teams is designed for current availability, not historical analysis
Microsoft’s position: “Presence is about what’s happening now, not what happened yesterday.”
Method 1: Using The Green Dots (Recommended)
How It Works
The Green Dots is a third-party tool that tracks Teams presence history by:
- Continuously monitoring Teams presence status throughout the day
- Storing presence data securely in the cloud
- Displaying 24-hour timelines showing Available, Busy, Away, Offline periods
- Providing historical reports going back weeks or months
Step-by-Step Setup
Step 1: Sign Up
- Go to app.thegreendots.io
- Click “Start Free 7-Day Trial”
- Sign in with your Microsoft 365 account
Step 2: Grant Permissions
- Microsoft will ask for consent to read presence data
- Click “Accept” (read-only permissions, no data modification)
- The Green Dots securely connects to your Microsoft 365 organization
Step 3: Select Team Members
- Choose which users to track (individual users or entire organization)
- Set timezone preferences
- Configure reporting preferences (weekly emails, alerts, etc.)
Step 4: Check Status History
- Dashboard shows real-time presence for all tracked users
- Click any user to view their 24-hour timeline
- Select past dates to view historical status data
- Export to CSV for further analysis
Pricing
- 7-day free trial (no credit card required)
- $2.00 per user per month after trial
- Volume discounts for 25+ users
Method 2: Activity Reports (Limited)
Microsoft 365 Admin Center provides basic activity reports, but they don’t show presence history.
What You CAN See
Teams Activity Report (admin.microsoft.com → Reports → Teams):
- Last activity date (not precise time)
- Chat messages sent
- Meetings attended
- Calls made
What You CANNOT See:
- ❌ Exact online times
- ❌ Status changes (Available → Busy → Away)
- ❌ Duration of each status
- ❌ Real-time or near-real-time data (reports lag 24-48 hours)
How to Access
- Go to https://admin.microsoft.com
- Reports → Usage → Microsoft Teams
- Select date range (up to 180 days)
- Export to Excel
Use case: Broad activity overview, not detailed presence tracking.
Common Questions
Is it legal to check someone’s Teams status history?
Yes, with proper disclosure. Key points:
✅ Legal if:
- Employees are notified
- Used for legitimate business purposes (coordination, not micromanagement)
- Complies with local labor laws
- GDPR compliant (if in EU)
❌ Not recommended if:
- Secret surveillance
- Used solely for performance reviews
- Violates employee privacy rights
Best practice: Be transparent. Notify team that presence tracking is enabled and explain why (coordination, work-life balance monitoring, etc.).
Can employees see that their status is being tracked?
Microsoft Graph API doesn’t notify users when their presence is queried. However:
Best practices:
- ✅ Tell your team presence is tracked
- ✅ Explain the purpose (helps with scheduling, not surveillance)
- ✅ Give access to their own data
- ✅ Use for team benefit, not individual punishment
Transparency builds trust more than covert monitoring.
How accurate is presence tracking?
The Green Dots provides highly accurate presence tracking with frequent status updates throughout the day.
Accuracy level: 95-98% capture rate of status changes
Limitations:
- Can’t detect “fake” presence (mouse jigglers)
- Multiple devices cause sync delays
- User can manually override auto-status
Can I check Teams status history for external users?
It depends on permissions:
External users in your tenant (guests): ✅ Yes, if admin grants consent Federated external organizations: ❌ No, presence limited to Available/Busy Public users: ❌ No access to presence data
Why: External presence data is controlled by the other organization’s admin, not yours.
How far back can I see Teams status history?
With The Green Dots: Unlimited history
- Data stored as long as subscription is active
- Can access presence data from months or years ago
- Export historical data to CSV anytime
With Microsoft Activity Reports: 180 days maximum
- Only aggregated activity (not detailed presence)
- No minute-by-minute status changes
With DIY Microsoft Graph solution: Depends on your storage
- Keep forever if you have database space
- Typically costs pennies per user per month for storage
Use Cases for Checking Teams Status History
1. Remote Team Coordination
Problem: Global team spans US, Europe, Asia. When can we meet?
Solution: Analyze 30 days of presence history to find 2-3 hour windows where 80%+ of team shows “Available” status.
Example insight: “Tuesdays 2-4 PM UTC: 18 of 20 team members typically Available”
2. Work-Life Balance Monitoring
Problem: Employees working excessive hours, burnout risk
Solution: Flag users who show “Available” status >50 hours/week or late at night
Example alert: “Alice has been Available past 10 PM local time 4 days this week”
3. Timezone Optimization
Problem: Don’t know when remote employee in Tokyo is actually working
Solution: Review presence patterns to identify typical work hours
Example insight: “Bob (Tokyo) typically Available 9 AM - 6 PM JST (consistent)“
4. Meeting Attendance Verification
Problem: Did team member actually attend the 2 PM meeting?
Solution: Cross-reference calendar invite with presence status at meeting time
Example check: “Status showed ‘Busy’ during meeting time slot → likely attended”
5. Project Timeline Analysis
Problem: Need to understand when team was actively working on Q4 launch
Solution: Review presence history for project period
Example analysis: “Team showed ‘Available’ status 60% more during launch week”
Best Practices for Status History Tracking
Do’s ✅
- Be Transparent: Tell team presence is tracked and why
- Focus on Patterns: Use for coordination, not minute-by-minute surveillance
- Combine Data Sources: Cross-reference with calendar, project timelines
- Set Clear Expectations: Define when immediate availability is needed
- Respect Time Off: Don’t expect responses during Away/Out of Office
Don’ts ❌
- Don’t Micromanage: Presence ≠ productivity
- Don’t Use for Performance Reviews Alone: Context matters
- Don’t Track Secretly: Transparency builds trust
- Don’t Ignore Timezones: “Available at 2 AM” may mean overwork
- Don’t Assume Accuracy: Status can be manually overridden
Alternatives to Status History Tracking
If tracking seems too invasive, consider these alternatives:
1. Team Availability Calendar
Create shared Outlook calendar where team updates availability manually
Pros: Simple, transparent Cons: Manual effort, often out of date
2. Daily Standup Updates
Quick async check-ins via Teams channel
Pros: Builds team connection Cons: Requires discipline, not historical
3. Scheduled Availability Windows
Set core hours where team commits to being Available
Pros: Clear expectations Cons: Less flexible for distributed teams
4. Meeting Scheduler Tools
Use Calendly, Microsoft Bookings for scheduling
Pros: Respects availability automatically Cons: Doesn’t solve ad-hoc coordination
Conclusion
Can you check Teams status history?
Native Teams: No Third-party tools: Yes (The Green Dots, DIY Microsoft Graph) Microsoft 365 Reports: Limited activity data only
Recommended approach:
- Use The Green Dots if you need easy, turnkey solution ($2/user/month)
- Build custom solution if you have technical team and want control
- Use Microsoft 365 Reports for broad activity trends only
Key takeaway: Microsoft Teams doesn’t save presence history by design, but third-party tools can fill this gap for legitimate business needs like coordination, work-life balance monitoring, and timezone optimization.
Check Teams Status History with The Green Dots →
Last updated: May 11, 2026
Related articles: