Case studies / Passwordless booking portal
Cross-sector
How a self-service training booking portal gave staff an Eventbrite-like experience inside Microsoft 365
A self-service booking portal that lived inside Microsoft 365, with no new credentials and no admin burden. The booking and attendance data it kept clean is also what Copilot guidance and a recommendation agent could build on later.
One-time email code authentication, so any staff member could sign in with their work email.
Two-way sync with Microsoft Teams calendar events, removing drift between portal and calendar.
No accounts, no password resets and no licence overhead for the booking layer.
A reusable pattern for any organisation running internal events, cohorts or roadshows.
Case study
Situation
Staff needed to enrol on training sessions, see what they were booked into and remove themselves if plans changed. Training coordinators wanted to stop fielding emails asking to be taken off a session.
IT was clear about one thing: no new credentials. The organisation already had enough identity surfaces and did not want to provision and reset passwords for a booking tool.
Case study
Challenge
An Eventbrite-style experience usually means an external platform and another login. That solves the user experience problem and creates an identity problem in its place.
Building inside Microsoft 365 felt like the right answer, but the team did not want to require accounts, licences or admin centre work for staff who just needed to book a session.
Case study
What the firm needed to avoid
The portal had to be modern without becoming another system to manage.
- A separate identity provider for the booking surface.
- Drift between what was in the portal and what was in Teams calendar.
- Manual reconciliation of attendance lists.
- Coordinator inboxes filling up with cancellation requests.
Case study
What changed
Authentication was passwordless. A one-time code went to the user's work email, they entered it, they were in. No accounts to provision, no passwords to reset and no licence overhead for the booking layer.
The portal was wired to Microsoft Teams calendar events in both directions. If a user pulled out of a session in the portal, the Teams invite was removed. If they declined in Teams, the portal reflected it. The state never drifted.
Case study
Outcome
Training coordinators stopped fielding remove-me emails. Attendance data stayed accurate without anyone manually reconciling lists.
The pattern is reusable. The same shape works for internal events, training cohorts, partner roadshows or any programme where staff need a self-service booking surface inside Microsoft 365.
What staff could do without IT
Browse, book, remove, reschedule. The calendar stayed honest.
Browse and book sessions
Staff could see available sessions and book themselves in without raising a request.
Self-service removal
Pulling out of a session happened in the portal and reflected in Teams without coordinator involvement.
Decline in Teams, reflect in portal
If the user declined the calendar invite, the portal updated to match. No drift between the two.
Passwordless sign-in
Email code authentication meant any staff member could sign in with their work email and nothing else.
Coordinator attendance view
Live attendance data appeared in the portal without anyone manually reconciling lists.
Personal booking history
Each user could see what they were booked into, what they had attended and what was coming up.
Where Copilot fits next
A portal is a starting point for a wider AI surface.
With booking, attendance and feedback data in one place, Copilot guidance, recommendation agents and reporting all fit naturally on top.
Copilot session guidance
Copilot can recommend the right sessions for a user based on role, team and previous attendance.
Course recommendation agent
A narrow agent can answer questions about which sessions match a learner's needs.
Automated reminders
Power Automate can chase pre-session prerequisites and follow up on missed sessions.
Reporting for L&D leads
Attendance, completion and feedback data feed naturally into a reporting view.
What the firm learned
Portals only work when the data never goes stale.
- Passwordless email codes solve a real friction without weakening security.
- Two-way sync is the difference between trusting a portal and not.
- Self-service only works when the data never goes stale.
- Coordinators are the right users to design the experience around, not IT.
- The pattern is portable. The same shape carries events, cohorts and roadshows.
Sensible next moves
Layer Copilot and recommendations on top.
- Next Layer Copilot guidance for course discovery.
- Next Extend the two-way sync pattern to other booking surfaces.
- Next Add a reporting view for L&D leads.
- Next Pilot the pattern for an external partner cohort.
Related routes
Where this example connects to FiveForward services.
Microsoft 365 workflow automation
Self-service surfaces and integrations that live inside Microsoft 365 rather than alongside it.
Power Automate consultancy
Workflow design that keeps state consistent across Teams, Outlook and SharePoint.
Microsoft Copilot agents
Where agents fit once a portal has a clean dataset behind it.
Copilot for businesses
Copilot guidance for organisations running internal events and learning programmes.
Next step
Give staff a modern booking experience without adding another credential set.
Talk through whether a passwordless, Teams-connected portal would suit your training, events or roadshow programme.