Truto added Microsoft Intune for Naq in 5 days

• 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

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

• 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

• 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

• 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

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.

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.

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.

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.