Hi @oalford, Short answer: the Mentorship “Microsoft integration” appears to be useful as a lightweight scheduling handoff, but I would not design around it as a full Outlook/Teams scheduling engine inside Mentorship. For your use case, it can help reduce friction for mentor/mentee 1:1s, but the program-led/group touchpoints will likely need to be handled outside the Mentorship flow or with a separate scheduling process.
What the Microsoft integration does in Mentorship
For Mentorship/Connections, the configuration supports a scheduling provider of Teams or Google Calendar, plus a “Static Teams Schedule Link” option under connections.scheduling. The implementation history indicates this started as a Teams deep link / link-out experience for scheduling chats, not a full in-product Outlook scheduler.
That’s different from Eightfold’s broader Scheduling product, which does support Microsoft Outlook/365 via OAuth and Microsoft Graph for calendar availability, event create/update/delete, and Teams meeting creation. I’d be careful not to assume those full Scheduling capabilities are automatically present in the Mentorship flow.
What it’s good for
It seems best suited for:
- Prompting mentor/mentee pairs to schedule their first conversation from the Mentorship task flow.
- Letting the pair move from an accepted mentorship or introductory chat into a real calendar interaction with less “now what?” friction.
- Supporting a lightweight mentorship journey with tasks, notes, nudges, feedback, resources, and admin usage/outcome tracking.
So: useful for pair-led 1:1 logistics, especially after the match is accepted.
What I’d design around / limitations
A few important limitations showed up:
- It is not clearly a full calendar-sync experience inside Mentorship. The evidence points to link-out/deep-link scheduling for Mentorship, while full Outlook calendar sync/event creation belongs to the separate Scheduling product.
- Outlook deep links were requested/preferred but not implemented in one Mentorship-related ticket; the item was marked “Won’t Fix”.
- Teams deep links had platform caveats — one ticket notes the Microsoft Teams native app on Mac did not appear to support the deep links, though Android mobile was confirmed.
- If Teams scheduling is not enabled, the schedule task can still exist but becomes more of a “Mark complete” task rather than a real scheduling link.
- For more complex scheduling patterns, customer feedback on Scheduling more broadly has called out restrictions around busy calendars, limited calendar options, and lack of flexibility for multiple predefined times.
Fit for your proposed program design
| Design element | Fit with current Mentorship capabilities |
|---|
| Front-loaded mentors / capped by capacity | Supported conceptually. Mentor Capacity lets mentors set active mentee capacity from 1–5, hides at-capacity mentors from recommendations, and disables the request button when full. |
| Mentor bios / focus areas | Supported. Mentors can add a bio and mentoring topics; mentees can discover/search based on skills, topics, jobs, career paths, etc.. |
| Mentees choose from bios | Supported via mentor discovery/profile browsing. |
| Mentor reviews mentee before confirming | Partially supported. Mentors can review the request details/message and accept/decline; an introductory chat flow can help vet fit before commitment I did not find evidence of a formal “mutual selection approval workflow” beyond request/accept/decline. |
| 3 program-led prescheduled sessions, including group sessions | I would not rely on the Mentorship Microsoft integration for this. Mentorship is more relationship/task oriented; program-led group scheduling likely needs Outlook/Teams, Events, or another scheduling process outside Mentorship. |
| 2 mentor/mentee pair-led 1:1s | Good fit. This is where the Teams scheduling handoff is most useful. |
| 5 fixed touchpoints total | Mentorship has journey phases/tasks — getting started, midpoint, wrap-up — but I did not find evidence that admins can natively configure an arbitrary five-touchpoint schedule with automatic meeting creation. |
Recommendation
Use the Microsoft integration as a lightweight convenience layer for pair-led meetings, not as the backbone of the entire program design.
For your design, I’d suggest:
- Use Mentorship for mentor profiles, topics, discovery, requests, capacity, notes, feedback, and relationship tracking.
- Use the Teams link-out only for the 2 mentor/mentee-owned 1:1s.
- Run the 3 program-led/group sessions separately via Outlook/Teams invites or another scheduling/event process.
- Add an intro chat step before formal acceptance if mutual selection feels important, but keep it optional or time-boxed to avoid adding too much friction.
- Start with capacity limits and a smaller pilot before scaling; a 1:5 mentor/mentee ratio is a reasonable reference point from prior guidance.
