Skip to Content
Microsoft 365 Integration
Module 10 · OAuth 2.0 identity join · calendar + mail two-way · Conditional Access inherited from Entra ID
Tenant
4cg.onmicrosoft.com
BBN-managed Entra ID
Calendar sync today
47
events synced both ways
Emails to CRM
184
auto-attached to customer timeline
CA policies
6
inherited · MFA · device · IP
🪄 AI inbox triage: classifies inbound mail (lead / dispute / RFQ / support), drafts reply with cited context from CRM + jobs, summarises long threads.
AI Resolve: triage Sarah's inbox Draft replies to 12 RFQs Summarise customer call transcripts

Connected office staff

OAuth 2.0 SSO · only office cohort (~50 staff) — workers use phone-number + OTP via M4b PWA
UserEmailRoleCalendar syncMail syncLast sync
Sarah Chen sarah.chen@4cg.com.au ops director ✓ Active ✓ Active 2m ago
Marcus Patel marcus@4cg.com.au state manager QLD ✓ Active ✓ Active 8m ago
Linh Nguyen linh@4cg.com.au state manager NSW ✓ Active ✓ Active 14m ago
Tom O'Brien tom@4cg.com.au supervisor STA ✓ Active ✓ Active 1h ago
Harish Arora harish@4cg.com.au CEO ✓ Active ✓ Active 31m ago
Jenna Smith jenna@4cg.com.au CFO ✓ Active ✓ Active 23m ago

In-scope integrations

  • OAuth 2.0 SSO — office staff log in with M365 credentials
  • Calendar two-way — bookings/jobs sync to user calendars; meeting invites flow back
  • Outlook mail — sent/received emails auto-attach to CRM customer timeline (Module 1)
  • Conditional Access — MFA · device compliance · IP allowlist · inherited from Entra ID
  • No per-worker licence — 700 casuals use phone-number + OTP via M4b PWA

Out of Phase 1 scope

  • Teams deep integration (Phase 2)
  • SharePoint as backend store
  • Power Platform integration
  • SAML federation (not required — OAuth 2.0 is sufficient)

M10 is intentionally thin — joining identity + sharing calendar/mail is the scope; deeper Office integrations are change-request territory.