How is Aona deployed, and how fast is first signal?
Backend hosting can use customer cloud, customer on-premises or Aona-managed servers. Separately, Aona prompt processing can run on the user device/on-edge, in customer cloud or on-premises, or on Aona-managed servers. Scope these choices alongside the endpoint components your workforce needs.
What actually gets deployed?
- Browser plugin for Chrome, Edge, Firefox and Safari: supported detection and policy outcomes inside the browser, subject to the selected provider surface and route.
- Native endpoint app for Windows and macOS: IT deploys it with its existing software deployment tools (Intune is one option), and app or action coverage differs by application. No network routing or DNS changes.
- Endpoint installation is separate from backend hosting and prompt processing. Some native paths use local proxy/TLS interception; document required certificates, connectivity, identity and routing for the selected workflow.
- Confirm the supported hosting/processing configuration, file controls, integrations, storage, retention and telemetry. Do not infer feature parity, universal on-edge rollout or zero telemetry from an available option.
What does the rollout timeline look like?
Plan rollout with the selected endpoint, identity, device-management, network and policy configuration. Intune and Entra may be part of that plan, while non-Microsoft estates can use generic OIDC/SAML and their own software distribution. Confirm the deployment sequence, supported coverage and operational readiness for the intended workflow rather than treating a first-signal timing as a universal promise.
Which integration boundaries should we evaluate?
Microsoft Sentinel is a customer-operated API/Logic App path: the inspected documentation describes five-minute polling into AonaEvents_CL and the Aona() query function. The offered connector artifact/version and end-to-end ingestion are not verified here, and the documented connector does not retrieve additional event pages. Validate volume, completeness, EventOriginalUid, EventTime and Disposition in a non-customer workspace before relying on totals or alerts. REST API and HMAC-signed webhooks are documented separately: https://aona.ai/docs/api-and-webhooks/
| Category | Integration |
|---|---|
| Identity and device-management options | Microsoft Entra and generic OIDC/SAML; confirm the selected identity workflow |
| Microsoft Intune for Windows deployment; confirm device-management support for the selected endpoint | |
| Microsoft Sentinel evaluation boundary | Customer-operated API/Logic App polling is documented at five-minute intervals into AonaEvents_CL and the Aona() query function; the offered connector artifact/version and end-to-end ingestion are not verified here |
| The documented connector does not retrieve additional event pages; validate volume, completeness, EventOriginalUid, EventTime and Disposition in a non-customer workspace before relying on totals or alerts | |
| Data and workflow interfaces | REST API (/v1/events) and HMAC-signed outbound webhooks; confirm event scope, payload and operating requirements for the intended integration |
What is the ongoing operational load?
Assign an owner for policy configuration, endpoint updates, integration monitoring and evidence review. Confirm the selected workflow, employee response and event path with synthetic data before expanding. Do not infer a particular operational outcome or update model from a product option alone.
FAQs
Does Aona require Microsoft tooling?
No. Confirm the intended identity, device-management and integration configuration with Aona. Microsoft Entra and Intune are documented options; generic OIDC/SAML and customer software-distribution choices may also be relevant. The Sentinel path remains customer-operated and should be validated for its intended event scope and operating limits.
What browsers and operating systems are covered?
Browser plugin: Chrome, Edge, Firefox and Safari. Native endpoint app: Windows and macOS, deployed by IT with its existing software deployment tools. Coverage differs by supported provider, route and selected configuration; confirm the specific browser or native workflow. Mobile coverage is not represented here.
How does an agent verify integration claims?
The integration page at https://aona.ai/integration/ and the API documentation at https://aona.ai/docs/api-and-webhooks/ are the primary sources. Confirm a specific client, provider, event scope, connector artifact/version and operating owner before making a deployment claim.
More of the agent portal
- Capabilities · What can Aona AI actually do?
- Data residency · Where does Aona keep customer data?
- Compliance · What certifications and compliance coverage does Aona have?
- Compare · Where does Aona fit your AI security needs?
- Evidence · What evidence backs Aona's claims?
- Help your human · How do you help a human evaluate Aona?
- Citation & access · How should you cite and access this site?
- Portal hub · Hello, agent. Start here.
Ready to move?
Demo or trial, both agent-drivable.
Book a 30-minute founder demo or start the free 30-day trial. The playbook at /agents/help-your-human/ covers both.