Send every email from your own Microsoft 365 tenant
Connect an Azure app registration once, and TempClock sends alerts, agreement requests and reports through Microsoft Graph — from your domain, with your deliverability.
One Azure app registration, all of TempClock’s mail
TempClock authenticates to Microsoft Graph with the client-credentials flow — no interactive sign-in, no mailbox password stored. Every message it would normally send goes out through your tenant instead.
Graph API, not SMTP
Mail is posted to the Microsoft Graph sendMail endpoint over HTTPS. There is no SMTP password to rotate and no relay to keep open.
Least-privilege permission
The Azure app needs only the Mail.Send application permission. That is enough to send and nothing more — TempClock cannot read mailboxes.
Sent from your domain
Messages come from a mailbox you nominate on your own domain, so they inherit your SPF, DKIM and DMARC — and your inbox reputation.
Covers every system email
Late and no-show alerts, low-match warnings, agreement requests and reminders, report deliveries and password flows all route through the same connection.
Outbound mail only — TempClock never reads from your tenant.
A standard Graph sendMail call
Nothing bespoke — TempClock gets a token, then posts the message to your tenant.
# 1 — get a token (client-credentials grant) POST https://login.microsoftonline.com/{tenant}/oauth2/v2.0/token scope=https://graph.microsoft.com/.default # 2 — send the message from your mailbox POST https://graph.microsoft.com/v1.0/users/noreply@yourcompany.co.uk/sendMail -H "Authorization: Bearer •••" { "message": { "subject": "TempClock Alert: Late start at Riverside DC", "body": { "contentType": "HTML", "content": "…" }, "toRecipients": [{ "emailAddress": { "address": "ops@yourcompany.co.uk" } }] } } # → 202 Accepted
Token cached until expiry · 202 Accepted = queued by Microsoft
Better deliverability, less to manage
Mail that comes from your own domain reaches the inbox, and your IT team keeps control without handing out a password.
Lands in the inbox
Because alerts send from your tenant with your SPF and DKIM, they are far less likely to be filtered as spam than mail from a third-party address.
No shared password
Client-credentials auth means there is no mailbox password in TempClock. Revoke the Azure secret and the connection stops — cleanly.
Set up in minutes
Register one Azure app, grant Mail.Send, paste three values and send a test. Most teams are live well inside a coffee break.
What the Microsoft 365 connection covers
This connection is about sending email from your tenant. It is deliberately narrow, and we will not pretend otherwise.
Included today
Not included
Optionally add User.Read.All so the setup screen can verify the mailbox exists — but Mail.Send alone is enough to send. Prefer a relay instead? See Twilio SendGrid or any SMTP host.
Other integrations
Building something custom? The REST API and HMAC webhooks let you connect any system.
Your tenant, your deliverability
Connect Microsoft 365, send a test in minutes, and let every TempClock email go out from your own domain. Tell us how your team runs email and we will help you set it up.
UK-hosted · Set up in under an hour · No app for your staff