Zia.

Microsoft 365

Microsoft 365 Developer

Custom software inside Microsoft 365 — Office add-ins across Outlook, Word, Excel, and PowerPoint, Microsoft Graph integrations, and SSO with Entra ID — built with Office.js and delivered to AppSource or your tenant.

What I build

What's included

Office add-in development services

Task panes and ribbon commands across Outlook, Word, Excel, and PowerPoint using Office.js — one codebase, all hosts.

Microsoft Graph integration

Reading and automating mail, calendar, files, users, and Teams through the Microsoft Graph API with delegated or application permissions.

SSO & Entra ID

Single sign-on with MSAL and Entra ID (Azure AD), least-privilege scopes, and admin-consent flows ready for enterprise rollout.

AppSource & deployment

Manifest authoring, Microsoft's validation, and publishing to AppSource or centralized deployment through the 365 admin center.

Problems this solves

Sound familiar?

  • Business logic that lives outside Office, so staff constantly switch apps and re-key data.
  • An add-in that has to work identically on Outlook/Excel desktop, web, and Mac.
  • Enterprise SSO and admin-consent requirements that block a naive add-in from shipping.
  • AppSource submissions bouncing on validation because the manifest or permissions are wrong.

Example use cases

What this looks like in practice

01

CRM context in Outlook

An Outlook add-in that shows the sender's deal and ticket history on the open email, pulled live via Microsoft Graph.

02

Live figures in Excel

An Excel add-in with custom functions streaming live data from an internal API straight into cells.

03

Org-wide rollout

Deployed an add-in to an entire tenant through the admin center with Entra ID SSO and no per-user install.

Tech stack

The tools I use for this

Add-ins

  • Office.js
  • React
  • TypeScript

Platform

  • Microsoft Graph
  • MSAL
  • Entra ID SSO

Hosting

  • Azure Static Web Apps
  • Azure Functions

Delivery

  • Unified manifest
  • AppSource
  • Centralized deployment

Process

How it works

01

Scope the workflow

Clarify Office apps, Graph data, permissions, and deployment target.

02

Build the add-in

Office.js + React task panes and a secure Graph backend.

03

Secure & validate

SSO, scopes, and manifest hardening against Microsoft's rules.

04

Deploy & support

AppSource or tenant deployment, with docs and handoff.

FAQ

Questions, answered

What's the difference between an Office add-in and an old VSTO plugin?
VSTO/COM plugins are Windows-only and install per machine. Modern Office add-ins are web apps built on Office.js that run in Outlook, Word, Excel, and PowerPoint across Windows, Mac, and the web — the supported, future-proof model.
Do add-ins work on desktop, web, and Mac?
Yes. A single Office.js add-in runs across Office on Windows, Mac, iPad, and the web, with capability checks where a host differs.
Can you integrate Microsoft Graph for mail, calendar, and files?
Yes — Microsoft Graph integration is central to my work, covering mail, calendar, files, users, and Teams with delegated or application permissions.
Do you set up SSO with Entra ID?
Yes. I implement single sign-on with MSAL and Entra ID (Azure AD) using least-privilege scopes suitable for enterprise environments.
Can you publish to AppSource or deploy internally?
Both. I prepare the manifest, pass Microsoft's validation, and either publish to AppSource or deploy privately via centralized deployment in your admin center.

Let's build it together

Email me with what you need — I'll reply with a clear plan and next steps. Prefer chat? WhatsApp works too.