Works with Microsoft. Entra ID, Power BI, Power Automate, Teams and Excel: the tools your site already owns.
Operator rounds and routine inspections, reported in the Microsoft tools your business already runs. Your directory decides who signs in, your reporting tools read the record on a schedule with nobody signed in, and Teams hears about readings that need attention. Each route below says plainly whether we have verified it on production or published a setup guide.
Inspection dashboards, from the round your operator walked this morning
No exporting by hand. No copying between systems. A dashboard refreshes on a schedule with nobody signed in — and reads the same record an auditor would be shown.
- Any system (REST)Verified in productionA real Entra service principal read a live production site's evidence unattended: 12 pages, 36 rows, one attributable pull — then 403 on the same token, one second after the membership was revoked.
- Microsoft Power BIVerified in productionThe Power BI service refreshed a live production site's evidence on a schedule with nobody signed in (Dataflow Gen2, 1865 rows over 2 pages, one attributable pull) — then 403 and no data once the site revoked the integration, and back on re-registration.
- Power Automate / Logic AppsVerified in productionA scheduled Power Automate flow read a live production site's evidence under its own machine identity and posted a summary to Microsoft Teams, unattended — then 403 and nothing posted once the site revoked it, and back on re-registration.
- Teams operational notificationsVerified in productionA Power Automate recipe under its own read-only identity posted readings needing attention to a Teams chat as they reached a live production site — including one recorded in airplane mode, notified on arrival with both times; revoke → 403 and nothing posted, re-register → the outage read in full; replay, a one-message catch-up and a daily heartbeat. Not walked: a channel, paging past 1000 rows, per-round grouping.
- Microsoft FabricSetup guide available
- Excel for WindowsSetup guide available
- SharePoint / TeamsAvailable via the API
- SAP PMAvailable via the API
- IBM MaximoAvailable via the API
- AVEVA PIAvailable via the API
- Excel for MacNot supportedPower Query on macOS cannot send an Authorization header, so no version of the recipe works. Stated on the tile rather than in a footnote.
No second copy of your data. Every one of these — the dashboard, the spreadsheet, the API call, the CSV an auditor is handed — reads the same versioned projection of the same record. There is no reporting database to fall behind, and no way for two of them to disagree about a reading.
Find us on Microsoft AppSource
Listed on Microsoft AppSource
Live
Amberhold is listed on Microsoft AppSource as a SaaS offer from Amberhold Ltd. Your procurement or IT team can find it there and send an enquiry with Contact me.
Amberhold on Microsoft AppSource →Microsoft verified publisher
Verified
Amberhold Ltd is a Microsoft verified publisher. The Amberhold applications in Microsoft Entra ID carry Microsoft's verified-publisher mark, so your administrators can see who published the application they are being asked to consent to.
What it works with
Identity — Microsoft Entra ID
Single sign-on with your work accounts
People sign in with the Microsoft account they already have. Your Conditional Access, MFA and device policies apply unchanged, because the sign-in happens in your tenant, not ours. No local passwords, no shared logins, no separate account list for IT to maintain.
A leaver stops here too
Disable somebody in your directory and they stop signing in to Amberhold. Signing in never grants access on its own — a membership on the site does — so access can also be ended in Amberhold immediately, and it takes effect on the next request rather than when a token expires.
Reporting and automation
Power BI
Verified in production · 12 Oct 2026
Scheduled refresh with nobody signed in, authenticated by an application identity from your own tenant. On production, the Power BI service refreshed a live site's evidence on a schedule, was refused once the site revoked the integration, and refreshed again after re-registration. Dashboards read the same versioned projection as the export, so a report, a spreadsheet and an auditor's pack cannot disagree about a reading.
Power Automate and Logic Apps
Verified in production · 12 Oct 2026
A scheduled flow reads evidence under its own machine identity and acts on it, for example posting a summary to Teams. On production, the flow ran unattended, was refused once the site revoked it, and worked again after re-registration. The HTTP action authenticates with Active Directory OAuth, so there is no token handling to write.
Teams operational notifications
Verified in production · 12 Oct 2026
Teams operational notifications are delivered periodically after evidence reaches Amberhold. They are not alarms or a safety system; your plant's alarms are unchanged. It runs in your own Microsoft tenant under its own read-only identity. Revoke it in Amberhold and the next run is refused; your IT can also switch it off in your own directory. It is a Power Automate recipe your IT team sets up from our documentation, posting readings that need attention to a Teams chat.
Excel
Setup guide available
A workbook that refreshes itself from live plant evidence instead of somebody re-exporting a spreadsheet every Monday. The column names are the same ones in the CSV export, so sheets built on exports keep working. Windows Excel; on macOS, use Power BI or Fabric.
Microsoft Fabric
Setup guide available
The same query in a Dataflow Gen2, landing in a Lakehouse for Direct Lake reporting. Browser only, with no Windows machine needed to set it up. The steps are published; we have not yet walked Fabric end to end on production.
Integration — REST, OpenAPI, OAuth
A read-only REST API
Verified in production · 18 Aug 2026
GET /api/v1/sites/{siteId}/readings returns reading evidence as JSON, with filtering, paging and a stable identifier on every row so anything can be traced back to the record it came from.
OpenAPI, published and unauthenticated
The machine-readable contract sits at /api/v1/openapi.json and needs no account to read. Your integration team can size the work up before anyone signs anything, and generate a client from it if they prefer.
Application identities rather than API keys
A system authenticates as itself using OAuth 2.0 client credentials from your Entra tenant, holding an application permission you grant. The secret stays in your tenant — you create, rotate and revoke it, and Amberhold never sees or stores it.
Every unattended read is logged
Which system, which site, when, what scope, how many rows — written to an append-only ledger the database will not let anybody edit. A refresh that took nine requests is recorded as one pull, because that is what it was.
Where this leaves your IT department
Nothing to install, nothing inbound
Amberhold runs in the browser on the tablets and phones people already carry. All traffic is outbound HTTPS — no agents, no VPN changes, no firewall inbound rules, no on-premise components.
Hosted in the UK, and your data comes back on demand
Primary infrastructure sits in the London region, with daily backups, point-in-time recovery and a rehearsed restore. A site administrator can export the complete site record from inside the product on any day, without asking us.
A question this page didn't answer?
Ask it directly — supplier questionnaires and security reviews are answered promptly, by the people who built the platform.