Using WordPress? Every integration here is also available as a plugin. Browse the plugin store →

Automate . Measure . Build

One job, taken seriously: Microsoft 365, on the page.

WPIntegrate is the Microsoft 365 product line of Diverse Website Strategies LLC. It puts data that already lives in Bookings, Outlook, SharePoint, Entra ID and Power BI onto any website — delivered either as an embeddable web component or as a WordPress plugin, with no Microsoft Graph integration for the site owner to build or maintain.

13 components
8 released and 5 built and in testing, each reading a Microsoft 365 source through Graph and shipping as one custom element.
2 delivery models
An embeddable web component, or a WordPress plugin. Both permanent, and neither a funnel for the other.
2 Graph access modes
managed, where we hold the Azure credentials — or proxy, where you do and we never hold a token.
WCAG 2.1 AA
Self-imposed rather than contractual, and verified at token-generation time in both light and dark.

Why it exists

The data is already somewhere. It just is not on the website.

An organisation running Microsoft 365 already keeps its appointments in Bookings, its events in Outlook, its files in SharePoint and its people in Entra ID. Putting any of that on a public page has historically meant registering an Azure application, learning Graph, and owning the integration afterwards. We do that part.

The mechanism that makes this workable inside real organisations is that there are two ways for us to reach Graph, and the choice belongs to the customer’s IT rather than to us.

Every tenant runs in one mode or the other. The embed on the page is identical either way, so the decision is an infrastructure one and never a content one.

managed

We hold the credentials

WPIntegrate runs the client-credentials flow per tenant. An IT administrator grants consent once and is not asked for anything again.

proxy

You hold the credentials

You supply a gateway base URL and an API key. We store that key encrypted at rest, and Graph traffic never leaves your perimeter.

Who we build for

Three readers, and only one of them installs anything.

  • WordPress site owners and developers

    They run the site, buy the plugin and paste the shortcode. What they want is Microsoft 365 data on the page without opening the Azure portal.

  • Digital agencies

    They implement on behalf of clients, across several Microsoft 365 tenants. What they want is repeatability, and a widget that carries the client’s brand rather than ours.

  • A split buyer and implementer

    A stakeholder recognises the problem and champions the fix; a developer or an agency does the installing. These are frequently different people, so this site argues and the dashboard operates.

What we hold ourselves to

Five rules that decide arguments here.

These are the trades already made, written down so they stop being re-argued. Each one costs us something, which is how you can tell it is load-bearing.

  1. 01

    Two front doors, one product

    The WordPress store and the components platform are both permanent. Neither is a funnel for the other, and neither is allowed to look like an afterthought — which is why they get the same room in the catalogue.

  2. 02

    The buyer and the implementer are different people

    Persuasion belongs on these pages; density and precision belong in the dashboard. We do not make a stakeholder read an admin console, or make a developer wade through a pitch to find a field reference.

  3. 03

    The customer’s brand wins inside the embed

    Widgets are white-labelled. A tenant sets a brand theme, any single instance can override it, and our styling stops at the boundary of our own properties. The design system supplies defaults, never mandates.

  4. 04

    Microsoft is the context, not the costume

    People arrive from Microsoft 365 and expect its vocabulary and conventions. That is a reason to be legible to them — not a reason to impersonate Microsoft in either the interface or the paperwork.

  5. 05

    Existing installs must keep working

    Plugins already in the wild call home for update metadata and licence checks, and that endpoint stays live. Nothing we ship is allowed to quietly break a site that has not upgraded.

And one that is not negotiable at all

WCAG 2.1 AA, self-imposed. No customer audits us against it and no VPAT is required — but the widgets render inside other people’s websites, so a contrast or semantics failure we ship becomes their accessibility failure on their domain. Every foreground and background pair in the design system is checked in both light and dark before it can be generated, and a failing pair refuses to build.

Where the product lives

Three addresses, one product

wpintegrate.com This site
The front door: what the components do, what the plugins do, and which of the two fits the stack you already run.
plugins.wpintegrate.com The store
The WordPress plugin line, and where existing customers reach their downloads and licences. The only place anything can be bought today.
dash.wpintegrate.com The dashboard
Where a subscriber configures each component instance and holds its embed key. Deployed and working, and not yet offered to the public.

The widgets are a fourth surface and the only one we do not own: they render on customers’ sites, inherit the host page’s context, and carry the customer’s brand rather than ours.

The store is open. The component platform is not, yet.

The WordPress line is on sale today and does the same Microsoft 365 jobs. The components are in pre-launch, which means no signup and no purchase — but named demand is what sets the order things are released in, so tell us what you need.

Browse the plugin store Ask about components