Integration · Microsoft 365

Outlook, OneDrive and SharePoint, connected to your system.

Emails filed against the right client, bookings in the right Outlook diary, files in the right SharePoint folder, and staff signing in with the Microsoft account they already use.

Get a quote What it can do

A lot of Maltese offices run on Microsoft 365: Outlook for mail and diaries, OneDrive and SharePoint for files, and a Microsoft account for sign-in. Microsoft exposes these through one public interface, Microsoft Graph, so a custom system can read and write to them.

The aim is the same as for any mail and diary integration. Staff stay in Outlook. The system files the right messages against the right client, puts bookings into the right calendar, and keeps documents where the team expects to find them. It is the bridge between your tools and a custom CRM.

What you can automate

Microsoft 365, wired into your system.

Outlook mail on the client record

Messages to and from a client appear on their record, so anyone covering the account sees the thread. Shared mailboxes such as info@ or sales@ are a common place to begin.

Sending from the system

Quotes, invoices and reminders go out from your own address, using templates, and the sent copy is filed. The recipient sees an ordinary email from your domain, and your signature and disclaimer rules still apply. Replies come back to the same thread on the record.

Bookings in Outlook calendars

A booking appears in the right person’s Outlook calendar, and moving it there updates the system. Useful for a booking system where staff already live in their calendar.

Files in OneDrive and SharePoint

Signed quotes, contracts and job photos are saved to a client or job folder in SharePoint, and permissions follow the rules you already have. Staff open them from the record with one click.

Sign in with Microsoft

Staff use their work account to sign in, so a new starter gets access when their account is created and a leaver loses it when theirs is disabled.

Contacts and tasks both ways

Outlook contacts can feed the CRM once, at the start, so you aren’t typing in two thousand addresses. After that, the CRM is the master list, and new contacts are created once, in one place. If you are moving from a pile of spreadsheets, my guide to moving from spreadsheets to a CRM covers the first import.

How it’s built

Connected, then watched.

01
Choose the scope
Which mailboxes, calendars and sites are in, and who can see what. A shared mailbox is a modest, easy-to-explain permission. A whole organisation’s mail is a much larger one.
02
Register the app in your tenant
Access is granted through Microsoft Entra, either on behalf of a signed-in user or as the app itself. App-level access to everyone’s data can only be approved by one of your administrators, and Microsoft recommends the narrower, user-level kind whenever it will do. We choose the narrowest that works.
03
Subscribe to changes
Microsoft Graph can notify an endpoint when mail or calendar items change, but those subscriptions expire and must be renewed. The system renews them on a schedule, and a catch-up pass reads recent changes in case a notification was missed.
04
Monitor it
Expired subscriptions, revoked consent and failed calls raise an alert. If an administrator changes a policy, you hear about it from the system, not from a client asking why a booking didn’t appear.

Worth knowing

Your Microsoft 365 tenant is under your IT administrator’s control. App permissions need their approval, and some organisations have policies that block outside apps. Ask early, because it is often the slowest step. A short email to your IT administrator or provider, naming the permissions, saves a week of waiting later.
Microsoft’s licensing is per user and set by Microsoft. What you pay for Microsoft 365 is between you and Microsoft, and not part of my build price.
If your team uses Google instead, see the Google Workspace page. Mixed setups are possible, but each side needs its own connection and its own checks.

Proof

Built before, running now.

I haven’t built a Microsoft 365 connection for a named client, and none is published here. What I describe rests on Microsoft’s public Graph API and on the same mail, calendar and file building blocks running on Google in Storex.

Storage & logistics · Live · in daily useStorex

Closest match, and on Google rather than Microsoft: Gmail, Calendar and Drive connected to one system, with Google sign-in and a logistics calendar kept in step.

Read the case study

FAQ

Questions, answered.

Can emails from Outlook sync into the CRM?

Yes, for the mailboxes you choose. Messages are matched to a contact by address and filed on their record. Anything the system can’t match goes to a short review list.

Does it work with a shared mailbox?

Yes, and that is usually the best place to start. Access to one shared mailbox is usually easier to approve than access to every user’s mail.

Can staff sign in with their Microsoft account?

Yes. The system uses your work accounts for sign-in, and the system still keeps its own permissions for what each person can do inside it.

Do you need access to our whole Microsoft 365?

No. The app gets only the permissions it needs, approved by your administrator, and you can withdraw them at any time.

How long does it take?

The quote builder prices “Gmail or Outlook” at roughly 20 to 40 build hours and calendar sync at 10 to 20, on top of the 30 to 50 hours of shared groundwork. Waiting for an administrator’s approval is the part I can’t control.

Go deeper

Get a fixed quote.

The quote builder opens with Microsoft 365 already selected. Add the rest of your system and I reply with a fixed quote.

Start the quote builder Or talk to me first