Healthcare
Microsoft 365 components for clinics and healthcare practices
Take the appointment on your own website, in your own branding, and let it land in the Microsoft 365 calendar your reception team already works from.
Dental practices, physiotherapy and chiropractic clinics, veterinary surgeries, opticians, private consultants, and the group practices running several sites out of one Microsoft 365 tenant.
What it reads, what the builder controls, and the markup it produces — on one page, with no signup in the way.
Bookings A drawing of the component, not a screenshot
In figures
The things a practice manager checks first.
-
Two
ways we reach your tenant
Managed, where your administrator consents once — or proxy, where you hold the credentials and Graph traffic never leaves your perimeter.
-
Zero
Microsoft sign-ins for the patient
Authorisation happens server-side, so no Graph token ever reaches the browser and no visitor is asked to sign in.
-
Seven days
before a submission is deleted
Form and booking answers are listed in the dashboard for a week, then removed. The permanent copy belongs in a mailbox or system you already own.
-
One
script tag on the page
A script tag and a custom element. The same two lines whichever component you embed, and the embed key only renders on domains you list.
The gap
The appointment you lose is the one that happens somewhere else.
Microsoft Bookings already gives a practice a working scheduling engine, a service list, staff and a booking page. That page lives on a Microsoft URL, in Microsoft’s styling, away from the page the patient was reading. Every hop between reading about a treatment and booking it is somewhere a patient stops.
The usual fix is a second booking system bolted onto the website, which means two diaries, two sets of opening hours and a reception team reconciling them. Reading the Microsoft calendar instead means there is one diary, and it is the one staff already have open in Outlook.
The components
What a practice puts on its own pages.
Every one of these reads a source the organisation already maintains, and each is configured per instance in a builder before it goes on the page. All of them are released today.
-
Bookings
<wpi-bookings>Works with Microsoft Bookings · Microsoft Graph
Your treatments, your practitioners and your genuinely open slots, on your own page. Availability is read from Microsoft at the moment the patient looks, and the confirmed appointment lands in Bookings — so reception sees it in Outlook exactly as they would from Microsoft’s own page.
-
Outlook Booking
<wpi-outlook-booking>Works with Outlook user calendars · Exchange room and resource mailboxes
For a practice with no Bookings licence: appointments taken straight against a clinician’s Outlook calendar. Slot length, working days, a minimum notice period and buffers between patients are all set in the builder rather than inherited from a Bookings business.
-
Form Builder
<wpi-form>Works with A Microsoft 365 mailbox with Mail.Send, for email delivery · Webhook endpoints · Your own SMTP server
New-patient registration, referral details and pre-appointment questionnaires. Branching rules mean a patient only sees the questions their answers make relevant, and the submission is delivered to a mailbox or a webhook rather than accumulating in the website’s database.
-
Persons
<wpi-persons>Works with Entra ID directory users · Microsoft 365 group membership · SharePoint lists
The practitioner page — names, roles and photos read from your Microsoft 365 directory or a SharePoint list. A clinician who joins the tenant appears on the site without anyone editing a page, and contact fields stay off unless you switch them on.
-
Documents
<wpi-documents>Works with SharePoint document libraries · OneDrive for Business
Aftercare leaflets, consent forms and price lists published straight from the SharePoint library the practice already keeps them in. The newest version in SharePoint is the version on the site, because there is no second copy.
No Bookings licence? There is a second route.
Outlook Booking takes the appointment straight against a clinician’s own Outlook calendar — no Microsoft Bookings business, no extra licence, and the availability rules set in the builder rather than inherited.
The details
The things a clinic has to get right before it can take a booking online.
None of these are the headline feature, and every one of them is why a practice abandons an online diary in the first month.
- Notice, and the gap between patients
- A minimum notice period in hours removes slots that are too close to now, and separate buffers before and after each appointment stop back-to-back bookings. Slot length runs from fifteen minutes to two hours.
- The hours are written in one timezone and read in another
- The timezone your working hours are authored in is a separate setting from the visitor’s own, so somebody booking from another region is shown the right time rather than a shifted one.
- Only the questions you are entitled to ask
- Name, phone, address and notes can each be hidden, or given a default that submits invisibly. Email is always collected, because Microsoft Bookings needs it to confirm the appointment — that one is not ours to switch off.
- What happens after they book
- A thank-you message, a redirect to a page of your own, or cancel, reschedule and book-again controls on the confirmation step. Every string on the widget can be reworded or translated.
- Where the widget is allowed to run
- An embed key renders only on the domains you list, so a copied snippet does not work on somebody else’s site. reCAPTCHA can gate submission, with the secret key held server-side.
Tell us which diary it has to sit beside.
The component platform is in pre-launch, so there is no signup for it yet and interest arrives as email that somebody reads. The WordPress plugin store is open today and sells the same Microsoft 365 jobs inside WordPress.
Questions
What people ask before they commit to this.
Do patients need a Microsoft account to book?
No. Requests are authorised server-side with your tenant’s own credentials, so a patient books without signing in to Microsoft and without ever holding a Graph token.
We do not have a Microsoft Bookings licence. Can we still take appointments?
Yes. The Outlook Booking component books directly against an ordinary Outlook calendar and needs no Bookings licence. The Bookings component is the one that drives an existing Microsoft Bookings business, with its services, staff, prices and Microsoft’s own confirmation emails.
Can we use this for patient data?
We make no HIPAA, GDPR or clinical-records claim and we do not sign a BAA today, so treat that as a no until we say otherwise in writing. What the components do is narrower: they display what you have already chosen to publish, and they hand a submission to a destination you own. Form and booking answers are deleted after seven days, Documents and Persons only ever read, and in proxy mode Graph traffic never leaves your own perimeter. Anything belonging in a clinical record belongs in the system that holds your clinical records.
Can two clinicians have different working hours?
In the Bookings component, hours and services come from the Bookings business itself, so whatever is already set there is what the widget offers. In Outlook Booking the hours are a setting on the instance, so a clinician working a different pattern is a second instance with its own embed key.
Can we stop last-minute bookings?
Yes. A minimum-notice setting in hours removes slots too close to now, and buffers before and after each appointment keep the next patient off the end of the last one.
Will it look like our practice or like your product?
Like your practice. Colours, radius, font family and type scale are per-instance settings with custom CSS beyond them, and the components carry no WPIntegrate branding — our styling stops at the boundary of our own properties.