---
title: Truto added Microsoft Intune for Naq in 5 days
slug: case-studies/naq-truto
description: Truto added Microsoft Intune for Naq in 5 days and built a new AWS API from Naq's requirements brief. Naq builds its compliance evidence reads on Truto.
canonical: https://truto.one/case-studies/naq-truto/
---

# Truto added Microsoft Intune for Naq in 5 days

Naq now has Intune live for its customers. Naq is a compliance platform for UK and EU regulated markets that builds on Truto to read users, devices, files and cloud accounts, including an AWS API built from Naq's brief.

- **5** days to add Microsoft Intune
- **~18** days from Naq's brief to AWS API
- **2+** times faster AWS reads, measured by Naq

> we currently have MS Intune live for our customers
>
> — Martin Donegan, Naq (October 2026)

## Naq at a glance

- **Customer:** [Naq](https://naqcyber.com/)
- **What they do:** A compliance platform for UK and EU regulated markets, covering 20+ frameworks
- **Truto products used:** The [unified user directory API](https://truto.one/unified-apis/user-directory/), the [unified SSO API](https://truto.one/unified-apis/sso/), the [unified MDM API](https://truto.one/unified-apis/mdm/), the [unified file storage API](https://truto.one/unified-apis/file-storage/), a new unified cloud infrastructure API and the Link SDK
- **Integrations:** [Google](https://truto.one/integrations/detail/google/), [Microsoft 365](https://truto.one/integrations/detail/microsoft/), [Microsoft Intune](https://truto.one/integrations/detail/msintune/), [SharePoint](https://truto.one/integrations/detail/sharepoint/) and [AWS](https://truto.one/integrations/detail/aws/)
- **Microsoft Intune:** Added 5 days after Naq asked (Aug 18, 2026), now live for Naq's customers
- **AWS:** A new unified cloud infrastructure API, live about 18 days after Naq's requirements brief (Sep 22, 2026)
- **AWS bucket reads:** About 4.8 seconds down to 1.2–2.3 seconds each on Naq's development account, after Truto let Naq ask AWS for only the fields it needs (Oct 13, 2026)

## How Truto worked with Naq

### The challenge

Naq collects compliance evidence from its customers' systems: who has an account, which devices are managed, how cloud accounts are set up, such as whether someone opened a storage bucket to the public. It needed Microsoft Intune, and a way to read AWS that Truto didn't offer yet.

### What Truto did

Truto added Intune to its unified MDM API, then built a new unified cloud infrastructure API for AWS from Naq's requirements brief. Requests go through a shared Slack channel, where Naq's engineers report what they find and Truto ships the fixes.

### The result

Naq has Intune live for its customers and is building on the AWS API. After Truto let Naq ask AWS for only the fields it needs, per-bucket reads on Naq's development account dropped from about 4.8 seconds to 1.2–2.3 seconds.

## From Google Workspace to AWS

Timeline, 2026.

- **Feb 13, 2026:** Naq picks Google as the first integration it will offer its clients.
- **Jul 3, 2026:** Truto sets up a test connector with synthetic users, so Naq can build its user sync without a live Google Workspace or Microsoft 365 tenant.
- **Aug 18, 2026:** Microsoft Intune goes live on Truto's unified MDM API. (5 days after Naq asked)
- **Sep 4, 2026:** Naq sends Truto its requirements brief for a unified cloud API.
- **Sep 22, 2026:** Truto's new unified cloud infrastructure API goes live, with AWS. (About 18 days after the brief)
- **Oct 1, 2026:** Naq has Intune live for its customers.
- **Oct 8, 2026:** Naq's app can now connect several standalone AWS accounts for one tenant, one connection each. Naq tests it end to end with two of its own.
- **Oct 13, 2026:** After Truto lets Naq ask AWS for only the fields it needs, per-bucket reads on Naq's development account drop from about 4.8 seconds to 1.2–2.3 seconds.

## How fast Truto delivered Naq's requests

- **Next morning:** Version history for SharePoint files on the unified file storage API
- **Under 1 day:** AWS bucket reads that fetch only the fields Naq asks for, such as public access and tags
- **Under 3 days:** A test connector with synthetic users, so Naq could build without a live Google Workspace or Microsoft 365 tenant
- **5 days:** Microsoft Intune on the unified MDM API

## Under the hood

APIs, cloud reads, scope checks and test data

### Users and devices

- Unified User Directory API for Google Workspace and Microsoft 365 users
- Unified SSO API on Google Workspace
- Microsoft Intune on the Unified MDM API: devices and their owners, with `GET /unified/mdm/devices/{id}` filling the device `type` from Microsoft Graph's `chassisType`

### Files

- SharePoint on the Unified File Storage API: workspaces, drives, drive items and permissions, plus `version_history`

### Cloud accounts

- AWS on a new Unified Cloud Infrastructure API, built from Naq's requirements brief: object stores, human identities, firewall rule sets, network boundaries and accounts
- A field selector on the per-bucket GET, so a sync asks only for the fields it needs, such as `anonymous_access_allowed` and `tags`
- `accounts/self` for the connected AWS account's own number and name, and several standalone AWS accounts for one Naq tenant, one connection each
- `unreadable_fields` says why a field is empty when AWS doesn't expose it, instead of leaving it blank

### Connection checks

- The scopes Google actually granted, in `context.oauth.token.scope` on each connected account, so Naq can flag a partial consent at connect time
- `missing_scopes` in `truto_error_insight` on a 403, compared against the granted scopes

### Building and testing

- Truto Test, a test connector with synthetic users and `is_2fa_enabled` values, so Naq builds without a live tenant
- Truto's Link SDK, through which Naq's customers connect their accounts

## Questions about Naq and Truto

### What does Naq use Truto for?

Naq, a compliance platform for UK and EU regulated markets, builds on Truto to read compliance evidence from its customers' systems: users from Google Workspace and Microsoft 365, devices from Microsoft Intune, which is live for its customers, and files from SharePoint and cloud configuration from AWS, which Naq is building on. Naq calls Truto's unified APIs, so its code reads each kind of system the same way.

### How fast did Truto add Microsoft Intune for Naq?

In 5 days. Naq asked on Aug 13, 2026 whether Microsoft Intune was available on Truto's unified MDM API, and Truto had it live on Aug 18. By October, Naq had Intune live for its customers, as Martin Donegan of Naq told Truto.

### How did Truto build an AWS API for Naq?

Naq sent Truto a requirements brief for a unified cloud API on Sep 4, 2026. Truto built a new unified cloud infrastructure API for AWS from it and had it live on Sep 22, about 18 days later. Naq's engineers then tested it, and Truto shipped their requests, such as bucket reads that fetch only the fields Naq needs.

### How did Naq build its user sync without a live Google Workspace tenant?

Naq's engineer could not connect a real Google Workspace tenant for development, because of Naq's security policy, and found no Google Workspace sandbox to use. Within 3 days of Naq asking, Truto set up Truto Test, a test connector with synthetic users, in Naq's development environment. Naq's engineer confirmed he could pull in users from Naq's app. Truto Test uses the same unified endpoints as a live tenant.

## More customer stories

- [BalkanID: 10 more apps in about 2 weeks, ServiceNow HR data in 4 days](https://truto.one/case-studies/balkanid-truto/): Reads users, roles and groups from the apps its customers use, including a long tail of smaller tools, through Truto’s unified user directory.
- [Komplai: ERPNext and QuickBooks behind one set of endpoints](https://truto.one/case-studies/komplai-truto/): An AI-powered accounting firm whose product calls the same accounting endpoints for ERPNext and QuickBooks Online.
- [15Five: 21 integrations live, the first three within a month](https://truto.one/case-studies/15five-truto/): Slack, Jira, Google Calendar and more feed 15Five’s AI features for managers, with a public launch about 3 months after kickoff.
- [Workweek: Salesforce Events in 16 hours, HubSpot diagnosed in 90 minutes](https://truto.one/case-studies/workweek-truto/): Is building CRM reporting for its B2B newsletter ad network on Truto’s unified CRM API, for Salesforce and HubSpot.