Audit an Enterprise Fleet
A 5-step recipe with Google Android. We can help you get access.
Recipe · 5 steps
Audit an Enterprise Fleet
with Google Android · Information Technology Management
Produce a read-only inventory of an enterprise, its devices, and its policies.
- List the enterprises bound to this project so the audit is scoped to enterprises the caller actually owns.
- Read the enterprise under audit to capture its display name and which notification types are enabled — a fleet with notifications off is a common source of stale device state.
- Collect the device fleet, including each device's state, applied state, and last status report time, which together reveal silent or drifted devices.
- Collect every policy defined for the enterprise so device policy assignments can be reconciled against policies that actually exist.
- Read in full the policy the first device reports it is on, so the audit records the actual settings the fleet is running rather than just a name.
What you'll need to have ready
- projectId: The Google Cloud project id that owns the enterprises.
- enterpriseName: The enterprise resource name to audit (e.g. enterprises/LC0123abcd).
- pageSize: How many records to request per page.
For your developer
Arazzo workflow google-android:audit-fleet-inventory, 5 operations: listEnterprises → getEnterprise → listDevices → listPolicies → getPolicy. Specs on APIs.io.