Using WordPress? Every integration here is also available as a plugin. Browse the plugin store →
Microsoft 365, on the website you already have
WPIntegrate puts live Microsoft 365 data — Bookings, Calendar, SharePoint documents, Persons, Forms and Power BI — on any website, delivered either as an embeddable web component or as a WordPress plugin.
No Azure app registration and no Graph code. Your IT approves once — or never, if you route Graph through your own proxy.
One element on a customer’s page
Rendered on the customer’s page, in the customer’s brand. WPIntegrate styling stops at the boundary of our own properties.
managed, where we hold the Azure credentials — or proxy, where you do and we never see a token.See it working
Three released components, drawn as they appear on somebody else’s website. Switch between them — the frame, the host page and the markup all change together.
<script src="https://cdn.wpintegrate.com/v1/bookings.js"></script>
<wpi-bookings embed-key="your-embed-key"></wpi-bookings>Availability is read from Microsoft at the moment the visitor looks, and the confirmed appointment lands in Bookings as if it had been made on Microsoft’s own page.
<script src="https://cdn.wpintegrate.com/v1/documents.js"></script>
<wpi-documents embed-key="your-embed-key"></wpi-documents>Folder navigation, search, preview and download — with no Microsoft sign-in for the visitor, because access is resolved on our side rather than theirs.
<script src="https://cdn.wpintegrate.com/v1/persons.js"></script>
<wpi-persons embed-key="your-embed-key"></wpi-persons>The people come from an Entra ID group, so a joiner or a leaver changes the page without anyone editing it. Email, phone and LinkedIn stay off by default.
The catalogue
Each one reads a Microsoft 365 source through Graph, is configured per instance, and ships as a single custom element. 8 of the 12 are released today; the other 4 are built and in testing.
<wpi-bookings>
Bookings shows your live Microsoft Bookings services, staff and open time slots on your own website, and writes the confirmed appointment straight back into Microsoft 365.
<wpi-calendar>
Calendar publishes events from Outlook, a SharePoint Events list, an ICS feed or a JSON API on your site as a month grid, an agenda list or a grid of event cards.
<wpi-documents>
Documents puts a SharePoint library or a OneDrive folder on your website as a browsable, searchable file list, with folder navigation, in-page previews and downloads.
<wpi-video-gallery>
Video Gallery gathers videos from SharePoint, OneDrive, YouTube, Vimeo and direct links into one grid on your site, with playback in the page.
<wpi-persons>
Persons publishes a staff directory on your website from Entra ID, a Microsoft 365 group or a SharePoint list, with photos, job titles and whichever contact details you choose to show.
<wpi-form>
Form Builder makes multi-step forms and quote calculators that deliver each submission to your inbox or a webhook, embedded inline or behind a floating button.
Web component only
<wpi-outlook-booking>
Outlook Booking takes appointments and room reservations directly against Outlook calendars and room mailboxes, with no Microsoft Bookings licence required.
<wpi-powerbi>
Power BI embeds a report, dashboard or single tile on your website — either a Publish-to-web link, or a secured token-based embed of a private report that visitors need no licence to see.
Built, in testing, not yet released. No dates announced.
A WordPress plugin doing a similar job exists for 7 of these, and the plugin is the one you can buy today.
See the full product catalogueWhere it runs
A component is a script tag and a custom element. There is no build step, no framework requirement and nothing to install on the page — so the place your site is built is not a question you have to answer first.
Named as examples of places HTML can be pasted. No partnership or endorsement is implied, and none of these are customers. WordPress is the one that gets more than an embed: the same jobs also ship as plugins with a Gutenberg block.
What you are actually installing
The embed
A script tag and one custom element carrying an embed key. Everything the widget needs — which Microsoft 365 source, which layout, which colours — resolves from that key at boot, so changing any of it later never means editing the page again.
<script src="https://cdn.wpintegrate.com/v1/calendar.js"></script>
<wpi-calendar embed-key="your-embed-key"></wpi-calendar>cdn.wpintegrate.com stands in for the real bundle host.The builder
Layout, source, fields shown, locale, clock, colours and corner radius are settings on the instance. A marketing lead changing the arrangement of a team page does not become a deployment.
Layout
Accent
Fields shown
White label
A tenant sets a brand theme once and every instance inherits it; any single instance can override it again. We supply defaults, never mandates — the widget is not a badge for us on somebody else’s site.
Live data
The library, the calendar and the directory stay where your team already maintains them. A file added in SharePoint or a leaver removed from a group shows up on the site without anyone touching the page.
Host page
The widget boots
and asks for its configuration by embed key.
WPIntegrate
Our API answers
after checking the subscription, then reads Graph.
Microsoft 365
The source of record
returns only what the consented scopes allow.
Licensing
Every configuration request is checked against the subscription before it returns, and an embed key only renders on the domains you list. A copied snippet does not work somewhere else.
→ GET /api/config/<embed-key>
← { "licensed": true, "config": { … } }
Refused for a domain that is not on the allowlist, and for a subscription that has lapsed.
Graph access
Every tenant runs in one mode or the other, and the choice belongs to the customer’s IT rather than to us. It is the reason this works inside organisations that will not delegate Graph access to a vendor.
managed
We hold the credentials
WPIntegrate runs the client-credentials flow per tenant. Your IT administrator grants consent once and is not asked for anything again.
Host page
The customer’s website
WPIntegrate
Our API calls Graph with our Azure credentials
Microsoft
Graph returns what the consented scopes allow
proxy
You hold the credentials
You supply a base URL and an API key for your own gateway. We store that key encrypted at rest and never hold a Graph token at all.
Host page
Identical embed — nothing on the page changes
WPIntegrate
Our API forwards to your gateway
Yours
Your perimeter, your credentials, your audit log
Microsoft
Graph traffic never leaves your network
Two front doors
Both lines are permanent and neither is a funnel for the other. Pick the one that matches the stack you already run.
Web component
A script tag and a custom element that behaves the same in Astro, Next.js, Webflow, a static HTML file or a WordPress page.
In pre-launch — not yet on sale.
Tell us what you needWordPress plugin
A mature line of Office 365 plugins sold through our store. Install, activate, drop in the block or the shortcode.
plugins.wpintegrate.com.api.wpintegrate.com.On sale today.
Browse the plugin storePlaceholder — not yet published
This section is built and deliberately hidden. The three cards below are layout placeholders, not customers, and stay that way until a named person has given a real quote we are allowed to print.
[Placeholder quote one. Replace with a real, attributable sentence from a named person who has agreed to be quoted.]
Placeholder — no customer Role and organisation go here
[Placeholder quote two. Replace with a real, attributable sentence from a named person who has agreed to be quoted.]
Placeholder — no customer Role and organisation go here
[Placeholder quote three. Replace with a real, attributable sentence from a named person who has agreed to be quoted.]
Placeholder — no customer Role and organisation go here
Ratings markup is deliberately absent as well as the quotes. Review and AggregateRating structured data gets wired up when there is something true to put in it, and not before.
Questions
Two lines: a script tag pointing at the component bundle, and one custom element carrying an embed key. Everything else — the Microsoft 365 source, the layout, the theme — is configured against that key, so changing any of it never means editing the page again.
No. In managed mode WPIntegrate holds the Azure credentials and your IT administrator grants consent once. In proxy mode you supply your own gateway base URL and API key, and Microsoft Graph traffic never leaves your perimeter.
Only if you want it to. Widgets are white-labelled: a tenant sets a brand theme and any single instance can override it. The design system supplies defaults rather than mandates, and WPIntegrate branding stops at the boundary of our own properties.
Yes. A custom element runs in any framework or in plain HTML with no build step, so the same embed works in Astro, Next.js, Webflow, Squarespace or a static file you edit by hand.
No. Both lines are permanent and neither is a funnel for the other. The plugins are for teams who live inside WordPress; the components are for everyone else, including WordPress sites that would rather embed.
Nowhere new. Components read Microsoft 365 at request time rather than keeping a copy, so what is on the page is what is in SharePoint, Outlook or Entra ID. Form and booking submissions are held for seven days so they can be exported, then deleted.
Not yet. The component platform is in pre-launch, so the channel open today is the WordPress plugin store at plugins.wpintegrate.com. If you want a component rather than a plugin, say so through the contact page and we will come back to you.
Yes. Installed plugins call api.wpintegrate.com for update metadata and licence checks, and that stays live. Nothing we ship is allowed to quietly break a site that has not upgraded.
The store sells the WordPress line today, with the same Microsoft 365 jobs behind it. If a web component is what you need instead, tell us and we will come back to you.