Productivity · Microsoft 365 integration

Connect Outlook calendars, Teams, SharePoint libraries and Excel to the records your business software keeps.

Many firms already live in Outlook, Teams and SharePoint, and they expect any new business system to respect the calendars, libraries and groups already set up there. A Microsoft 365 connection lets those tools read from and write to your business system. Appointments land in calendars, documents are filed against the right record. Staff sign in with their work account. GullySystem scopes each flow per project and tests it in a non-production tenant where one is available.

Share your requirements

At a glance

Connecting Microsoft 365 to the rest of your business.

Staff keep appointments in Outlook, files in SharePoint and running totals in Excel, and each of those tools holds part of the same story about a client or job. The business system holds the matter, job or customer those items belong to. Without a link, each item is re-keyed or attached by hand.

The link keeps a record and its calendar entries, folders and sign-ins in agreement. Which mailboxes, sites and groups take part is set by your administrator, not assumed.

What moves

What flows between Microsoft 365 and your system.

Each flow is agreed one at a time: which record, in which direction, and what happens when it fails.

Outlook calendar entries from bookings

A booked site visit, hearing or client meeting creates an event in the assigned person’s Outlook calendar. A reschedule in the system updates the event. A decline in Outlook flags the booking for reassignment. Declines are never ignored, since a declined invitation usually means the visit or hearing needs another person, and the booking is flagged until someone is assigned. Each event carries the client name, the address or room and the matter number, so the person accepting it knows what the appointment is for.

Teams channel notices for record changes

A change of stage on a matter, project or ticket posts a card to the Teams channel for that team. The card links to the record. A short reply can be added as a note. Cards stay short. Teams posts use one card layout across every channel, so a partner skimming five channels sees the same fields in the same order.

SharePoint folders per record

When a client, case or project is created, a folder is made in a named SharePoint library with the right permissions. Files saved there appear on the record. Files uploaded in the system are filed back into the folder. Permissions follow the record. Permissions on the folder follow the record team, so a junior added to a matter gains its documents and loses them on removal.

Excel exports and imports

Finance staff download a workbook of invoices or stock from the system for analysis, with one sheet per branch and the record number kept in the first column. An agreed template can be uploaded to create or update records. Rows that fail validation come back in a separate sheet. Rejected rows are returned, not dropped.

Work-account sign-in with Entra ID

Staff open the business system through their Microsoft work account. Roles come from groups in the directory. A leaver removed there loses access to the business system as well. Leavers lose access at once, because the business system checks group membership at sign-in instead of keeping its own copy of who is allowed in. Group names in the directory are mapped to roles in the business system once during setup. An admin page shows that mapping.

How it is built

From scoping to hand-over.

1. Scope the mailboxes, sites and direction

We list which calendars, Teams channels and SharePoint libraries are involved, and which way data moves for each; anything that reads email is limited to the mailboxes you name. Mail access is opt-in, limited to the mailboxes you name. Described in writing before any permission is requested from your administrator.

2. Connect and test outside production

An app registration is made in your tenant with the narrowest permissions the flows need. Testing runs on a developer or test tenant when you have one, otherwise on a set of pilot accounts. Consent is requested, never assumed.

3. Wire sign-in, calendars and sites

Users are matched by work email, and folder names follow a pattern we agree. Duplicate events, moved files and expired consent are caught and listed for an administrator to resolve. Names follow one pattern.

4. Test sign-in rules, then hand over

Each event, folder and sign-in the sync touches appears in its log. Our handover guide covers renewing consent, adding a user and revoking the app. Renewal dates go on a list.

Industries

Trades that often use Microsoft 365.

Ready products

Products it is paired with.

Modules

Capabilities it connects to.

What we build

What we would build for Microsoft 365 projects.

Usually in this order, starting with whatever the audit ranks first.

API and System Integration

Tally, WhatsApp, payment gateways, GST portals and your own apps sharing one set of numbers.

Learn more

Data Migration and Moving Off Spreadsheets

Data migration and spreadsheet replacement covers auditing existing files, cleaning and deduplicating records, loading them into a new system and reconciling the result against known totals. A parallel run of both systems comes before cutover. The original files are kept as they were.

Learn more

Managed IT Support

Managed IT support covers the everyday technology of an office. It includes a helpdesk for staff, patched and protected laptops, Microsoft 365 and Google Workspace administration, backups with tested restores, and account handling when people join or leave.

Learn more

Common questions

Questions about connecting Microsoft 365.

Do calendar and file links work in both directions?

They can. Calendar changes and file saves can flow either way, but each direction is chosen per flow so that two systems never overwrite one another by accident. Direction is set flow by flow.

What does our Microsoft 365 licence need to allow?

Your administrator must be able to register an app and grant consent in your tenant. Some features depend on the licence tier of the mailboxes or sites, which we confirm in scoping. Licences vary, so we check.

Can we bring in existing SharePoint folders and calendar history?

Existing folders can be matched to records by a naming rule or a mapping sheet. Old calendar entries are usually left where they are, unless you ask for a one-time import. History is optional.

What if Microsoft changes how its interfaces work?

Microsoft publishes changes to its interfaces and consent rules. The connection may need updating when they apply. Support for this is agreed per project, and failures are logged, not hidden. Failures stay visible.

Every product name on this page, Microsoft 365 included, is a trademark of its owner. GullySystem is not affiliated with any of them.

Start with your requirements

Tell us how you use Microsoft 365.

Share your requirements and an engineer will read them before getting in touch.

No obligation
A reply within one business day
Your details stay private

Start with your requirements

Seven short steps that tell us what you need. An engineer reads them before getting in touch.

Share your requirements