Overview
The Microsoft integration connects Thread with Microsoft 365 services, enabling calendar access for scheduling, email capabilities, and user directory features. [SCREENSHOT: Microsoft integration connected status] Caption: Microsoft 365 integration connectedBenefits
Calendar Access
View availability and schedule meetings
Email Sending
Send onboarding emails via Outlook
User Directory
Access team member information
Enterprise SSO
Single sign-on for Microsoft-based organizations
Available Features
Calendar Integration
- View availability - See free/busy times for scheduling
- Schedule meetings - Create calendar events
- Meeting links - Generate Teams meeting links
- Room booking - Access conference room availability
Email Integration
- Send emails - Dispatch onboarding emails via Outlook
- Email tracking - Track opens and clicks
- Branded sending - Emails come from your domain
- Reply handling - Manage customer responses
Directory Access
- User lookup - Find team members
- Profile information - Names, titles, photos
- Team structure - Organizational context
Setup Instructions
Prerequisites
- Microsoft 365 subscription (Business or Enterprise)
- Global Administrator or delegated admin permissions
- Thread account with admin role
Step 1: Connect OAuth
Review Permissions
Microsoft shows permissions Thread is requesting:
- Read calendar information
- Send email on your behalf
- Read basic user profile
- Read directory data
Admin Consent (If Required)
If your organization requires admin consent:
- Admin must approve the application
- May see “Approval required” message
- Contact your IT admin for approval
Step 2: Configure Features
Enable Calendar
Toggle “Calendar Integration” to enable:
- Availability checking
- Meeting scheduling
- Teams link generation
Enable Email
Toggle “Email via Outlook” to enable:
- Sending onboarding emails
- Email tracking
- Reply handling
Configure Email Settings
If using email:
- Select default sending account
- Configure reply-to address
- Enable/disable tracking
Calendar Features
Viewing Availability
When scheduling meetings with customers:- Thread checks CSM’s calendar
- Shows available time slots
- Displays conflicts and busy periods
- Suggests optimal meeting times
Scheduling Meetings
Teams Integration
If your organization uses Microsoft Teams:- Meetings include Teams links by default
- No separate Teams setup required
- Works with existing Teams settings
Email Features
Sending via Outlook
Emails sent through Thread can use your Outlook account: Benefits:- Emails come from your domain
- Customers see familiar sender
- Replies go to your inbox
- Full tracking capabilities
Email Configuration
| Setting | Description |
|---|---|
| Sending Account | Which Outlook account sends emails |
| Reply-To | Where replies should go |
| Signature | Whether to include Outlook signature |
| Tracking | Open and click tracking |
Tracking Capabilities
Track email engagement:- Opens - When emails are opened
- Clicks - Link clicks
- Replies - Customer responses
- Bounces - Delivery failures
Use Cases
1. Automated Meeting Scheduling
Scenario: Schedule kickoff calls automatically. Workflow:- Account created
- Template triggers kickoff meeting action
- Thread checks CSM availability
- Sends scheduling link to customer
- Customer picks time
- Calendar invite sent to all
2. Branded Email Communication
Scenario: Send onboarding emails from your domain. Configuration:- Connect Microsoft integration
- Enable email via Outlook
- Select sending account
- Emails now sent via your Outlook
csm@yourcompany.com instead of generic Thread address.
3. Availability-Aware Actions
Scenario: Only assign actions when CSM is available. How it works:- Workflow checks CSM calendar
- If available, schedules immediately
- If busy, queues for later
- CSM never double-booked
Admin Consent
Why Admin Consent May Be Required
Microsoft organizations often require admin approval for new applications. This happens when:- Organizational policy requires admin consent
- Requested permissions need admin approval
- First user from organization is connecting
Requesting Admin Consent
Once admin consent is granted, all users in your organization can connect without individual approval.
Troubleshooting
Connection Requires Admin Consent
Connection Requires Admin Consent
Cause: Your organization requires admin approval.Solution:
- Contact your IT/Microsoft 365 admin
- Share the consent request link
- Admin must approve the application
- Then reconnect
Calendar Not Syncing
Calendar Not Syncing
Check:
- Calendar integration is enabled
- Correct account connected
- Permissions include calendar access
- Reconnect the integration
- Verify calendar permissions
- Check Outlook calendar settings
Emails Not Sending
Emails Not Sending
Check:
- Email feature is enabled
- Sending account is configured
- Account has send permissions
- Test send from Outlook directly
- Verify send-as permissions
- Check email configuration
Teams Links Not Working
Teams Links Not Working
Check:
- Teams is enabled for your organization
- User has Teams license
- Meeting policies allow external guests
- Create meeting manually in Teams
- Check Teams admin settings
- Verify meeting policy
Best Practices
Use Dedicated Account
Consider a shared mailbox for sending rather than individual accounts
Keep Calendars Updated
Accurate calendars ensure correct availability checking
Test Thoroughly
Send test emails and meetings before going live
Monitor Deliverability
Watch email bounce rates and delivery issues
Microsoft-Specific Tips
- Shared mailboxes work well for team email sending
- Distribution lists can receive replies for team visibility
- Room resources can be booked if permissions allow
- Delegate access enables sending on behalf of others
Security & Compliance
Permissions Used
| Permission | Purpose |
|---|---|
| Calendars.ReadWrite | View/create calendar events |
| Mail.Send | Send emails |
| User.Read | Basic profile information |
| Directory.Read.All | Team member lookup |
Data Handling
- Calendar data accessed in real-time (not stored)
- Email content logged for tracking
- Directory queries cached briefly
- All data encrypted in transit
Compliance
- SOC 2 compliant integration
- GDPR considerations honored
- Microsoft data residency respected
