Contents
Microsoft 365 dominates business productivity. Outlook manages communications. Teams handles collaboration. SharePoint stores documents. Calendar coordinates schedules. For most organisations, Microsoft 365 is where work lives.
Operations platforms that ignore this reality create friction. Staff switch between systems. Data lives in silos. Manual copying introduces errors.
SwiftCase connects to Microsoft 365, linking your operational workflows to the tools your team already uses. The Outlook email and calendar connections are built in. SharePoint, OneDrive and Teams connect through SwiftCase's Configurable API, set up for your workflows during implementation. This guide explains what's possible and how to make the most of it.
Why Microsoft 365 Integration Matters
The Disconnection Problem
Without integration, operational systems exist in isolation:
Calendar disconnection: appointments scheduled in your case management system don't appear in Outlook. Staff double-book. Customers receive conflicting information. Manual calendar updates become another task to forget.
Email silos: customer communications happen in Outlook while case records live elsewhere. Finding the full picture requires searching multiple systems. Important emails get missed.
Document fragmentation: files scatter across SharePoint, OneDrive, local drives, and operational systems. Version control becomes impossible. Staff waste time hunting for the right document.
Context switching: moving between systems breaks concentration. Each switch costs mental energy and introduces error opportunities.
The Integration Solution
Microsoft 365 integration eliminates these problems:
Unified calendars: appointments created in SwiftCase automatically appear in Outlook calendars, and changes made there come back.
Email connectivity: send emails from within SwiftCase using your existing Outlook account. Incoming emails associate automatically with the correct case. The complete conversation lives with the case record.
Document storage: a workflow can send case documents to SharePoint or OneDrive, so they can be reached from either system.
Seamless experience: work in whichever tool suits the task. Data flows automatically between systems.
Calendar Integration
How It Works
SwiftCase connects to Microsoft 365 calendars through OAuth 2.0 authentication. Once connected, the integration supports bidirectional synchronisation.
Creating appointments: when you schedule an appointment in SwiftCase, the integration creates a corresponding Outlook calendar event. The event includes:
- Appointment title and description
- Date, time, and duration
- A Teams meeting link, if the calendar is set to add one
Updates and cancellations: changes in either system synchronise. Reschedule in Outlook, and SwiftCase updates. Cancel in SwiftCase, and Outlook reflects it.
Practical Applications
Customer appointments: schedule site visits, consultations, or assessments. Your team sees appointments in their familiar calendar interface.
Internal meetings: coordinate case reviews, handovers, or escalations. Book meeting rooms through the standard Outlook process while keeping appointments linked to cases.
Deadline management: create calendar events for important deadlines. Court dates, renewal deadlines, or regulatory submissions appear in Outlook where they're hard to miss.
Configuration Considerations
Calendar selection: SwiftCase writes to a calendar of its own in each connected account, so its appointments sit alongside your other events without touching them.
Meeting links: decide whether a connected calendar's appointments should carry a Teams meeting link.
Email Integration
How It Works
Email integration connects SwiftCase to your Microsoft 365 mailbox, enabling both sending and receiving through familiar email infrastructure.
Outbound email: send emails from SwiftCase using your Outlook account. Recipients see messages from your normal email address with proper signatures and formatting. Sent emails log automatically to the case timeline.
Inbound email: emails received at designated addresses or matching certain patterns can route to SwiftCase automatically. The system associates them with the correct case and adds them to the communication history.
Threading: email conversations maintain proper threading. Recipients can reply normally, and responses appear in the case record alongside the original message.
Practical Applications
Customer communication: send updates, requests, and notifications from within the case context. No need to switch to Outlook, compose a message, and manually log it. Everything happens in one place.
Template-based messaging: combine email integration with SwiftCase templates. Send consistent, professional communications with case data merged automatically.
Bulk communications: notify multiple customers or stakeholders efficiently. SwiftCase can send personalised emails to case-related contacts in batches.
Audit trail: every email sent or received appears in the case timeline. Auditors, supervisors, or future case handlers see the complete communication history.
Configuration Considerations
Sending identity: decide which email address sends SwiftCase messages. Individual user addresses maintain personal relationships. Shared mailboxes suit team-based workflows.
Routing rules: configure how inbound emails match to cases. Email addresses, subject line patterns, or embedded reference numbers can all serve as matching criteria.
Attachment handling: email attachments are added to the case's documents.
Signature management: maintain consistent email signatures. SwiftCase applies its own signature for each user.
SharePoint Integration
How It Works
SharePoint connects through the Configurable API, which can upload case documents to a SharePoint or OneDrive library as a step in a workflow.
Document storage: case documents can be copied to SharePoint as well as kept in SwiftCase, so your existing SharePoint structure, permissions, and retention policies apply to them.
Folder structure: the upload can be set up to file each case's documents in a folder of its own.
Version control: SharePoint's versioning capabilities apply to case documents. Track changes, restore previous versions, and maintain complete history.
Search and discovery: documents stored in SharePoint appear in SharePoint searches. Find case documents through either system.
Practical Applications
Regulatory compliance: organisations with document retention requirements can leverage SharePoint's compliance features. Retention policies, legal holds, and audit capabilities apply to case documents.
External sharing: SharePoint's sharing capabilities extend to case documents. Share files with external parties through secure links without giving access to SwiftCase itself.
Collaboration: multiple people can work on case documents simultaneously using SharePoint's co-authoring features. Changes sync automatically.
Backup and recovery: SharePoint's backup infrastructure protects case documents. Disaster recovery follows your established SharePoint procedures.
Configuration Considerations
Site structure: determine where SwiftCase creates folders. A dedicated document library maintains clear separation. Integration with existing structures requires careful planning.
Permissions: decide how SharePoint permissions interact with SwiftCase access. Options range from mirroring SwiftCase permissions to using SharePoint's own access controls.
Metadata: SharePoint metadata can enrich case documents. Case numbers, types, and status can flow to SharePoint properties, enabling powerful filtering and search.
Retention: align SwiftCase document lifecycle with SharePoint retention policies. Ensure documents persist as required and delete when appropriate.
Teams Integration
How It Works
Teams notifications are also set up through the Configurable API, which can post a message to a Teams channel when a workflow step runs.
Channel notifications: SwiftCase can post updates to Teams channels when significant events occur. New cases, status changes, escalations, and deadlines can all trigger Teams messages.
Formatting: messages can carry the case details your team needs, laid out as a card.
Practical Applications
Team awareness: keep teams informed about work in progress. New assignments, completed tasks, and status changes post to shared channels.
Escalation handling: urgent matters trigger Teams alerts. On-call staff see escalations immediately in the platform they're already watching.
Management visibility: summary notifications keep managers informed without requiring them to monitor SwiftCase constantly.
Cross-team coordination: when cases involve multiple teams, notifications to shared channels keep everyone aligned.
Configuration Considerations
Channel selection: choose which Teams channels receive which notifications. High-volume updates might warrant dedicated channels. Critical alerts might go to existing team channels.
Notification frequency: balance awareness against noise. Every minor update might overwhelm. Only major events might miss important context.
Information included: determine what case information appears in Teams messages. Sensitive details might warrant limited exposure.
Setting Up Microsoft 365 Integration
Authentication
Microsoft 365 integration uses OAuth 2.0 authentication:
-
Admin consent: a Microsoft 365 administrator grants SwiftCase permission to access your organisation's resources. This one-time step authorises the integration.
-
User connection: individual users connect their accounts. This enables personalised access respecting their Microsoft 365 permissions.
-
Token management: SwiftCase manages authentication tokens automatically. Refreshing and renewal happen behind the scenes.
Permissions Required
The integration requests specific Microsoft 365 permissions:
Calendar permissions: read and write access to calendars for synchronisation.
Mail permissions: send mail permission for outbound email. Read permission if routing inbound mail through SwiftCase.
SharePoint permissions: read and write access to specified sites and libraries for document storage.
Teams permissions: channel message posting for notifications.
Your administrator controls which permissions to grant. Integration features work independently, so you can enable calendar integration without email integration, for example.
Best Practices
Start focused: begin with one integration aspect rather than enabling everything simultaneously. Calendar integration might deliver immediate value. Add email and SharePoint as needs clarify.
Test thoroughly: verify integration behaviour with test cases before production use. Confirm emails send correctly, calendars sync properly, and documents appear where expected.
Document configuration: record configuration decisions for future reference. When questions arise about why integrations behave certain ways, documentation provides answers.
Monitor initially: watch integration behaviour closely after deployment. Early detection of issues enables quick correction before problems compound.
Train users: ensure staff understand how integrations work and what to expect. Surprises create confusion and erode trust.
Common Use Cases
Case-Based Customer Communication
A customer contacts your organisation. The case record captures their details. Throughout handling, all communication happens through SwiftCase:
- Initial acknowledgment email sends automatically when the case is created
- Staff compose follow-up emails within the case context
- Customer replies route to the case automatically
- The complete conversation history stays with the case
- Appointments appear in both SwiftCase and Outlook
- Documents share through SharePoint links
The customer sees normal email from your organisation. Your team works efficiently with everything in one place.
Field Service Coordination
A service team schedules site visits:
- SwiftCase creates the appointment with all job details
- The technician's Outlook calendar updates automatically
- Job documents appear in SharePoint for mobile access
- Completion updates post to the team's Teams channel
No manual calendar entries. No forgotten appointments. No missing paperwork.
Multi-Party Coordination
A case involves external experts or partners:
- Internal coordination happens through Teams channels
- Expert appointments sync to the connected calendars of the people involved
- Documents share through SharePoint without granting system access
- Email communications log automatically regardless of recipient
Everyone sees what they need to see. Nothing falls through the cracks.
Troubleshooting Common Issues
Calendar Events Not Appearing
If appointments don't sync to Outlook:
- Verify the user's Microsoft 365 connection is active
- Check that calendar permissions are properly granted
- Confirm SwiftCase's own calendar is present in the user's Outlook
- Review any synchronisation delay settings
Emails Not Sending
If outbound emails fail:
- Verify send permissions are granted in Microsoft 365
- Check that the sending account is properly connected
- Review email addresses for formatting issues
- Check for Microsoft 365 sending limits
SharePoint Documents Not Syncing
If documents don't appear in SharePoint:
- Verify SharePoint permissions are properly configured
- Check that the target site and library exist
- Confirm folder creation permissions
- Review file size and type restrictions
Moving Forward
Microsoft 365 integration transforms SwiftCase from an isolated operational system to an integrated part of your productivity ecosystem. Work flows between systems automatically. Staff use familiar tools. Data stays synchronised.
Start with the integration aspect that addresses your biggest pain point. Expand as you gain confidence and identify additional opportunities. The goal is seamless operation where the boundaries between systems become invisible.
Ready to connect SwiftCase to Microsoft 365?
See how calendar, email, and document integration would work with your specific setup. We'll demonstrate the integration with your Microsoft 365 environment and help you plan the optimal configuration.