Documentation menu
Deploy a fleet with confidence
A guided path from a first reporting agent to repeatable monitoring coverage.
Build one working measurement path before expanding the fleet. Keep the first deployment small enough to inspect each part: identity, configuration, delivery and the result.
Establish one reporting vantage
Follow the agent installation guide, then open the agent in the portal. Confirm its identity, network scope and last reported configuration. The Reporting identity section shows its server lease separately from enrollment status and uptime.
Ready to continue: the expected agent reports and its identity belongs to the intended machine. If it does not, use agent troubleshooting before cloning or reinstalling anything.
Create a focused check
Choose one target and one test type in test creation. Check the selected agents, interval and scope before saving. Start with a measurement you can explain and verify.
Ready to continue: a returned sample appears in test results. Inspect the sample time and vantage, then use the record detail export if you need to retain investigation context.
Make the rollout repeatable
Use network scopes to keep devices with overlapping IP addresses separate. Keep per-installation identity separate from pool membership. For temporary machines, follow the VDI lifecycle guide before preparing a golden image. Never include an enrolled credential, generated installation ID or queued spool in that image.
Ready to continue: replacing a VM creates a distinct installation while preserving the intended test placement.
Define what deserves attention
Build a dashboard around the signals your team checks regularly. Configure alert rules and their notification channels. Review baseline learning requirements before relying on a learned threshold.
Ready to continue: your team can identify the affected vantage and open the evidence behind a finding.
Establish a budget and operating routine
Review Usage & budget after the usage backend is deployed. Observe actual runtime and accepted data before enabling account-wide limits. Use the budget guide to distinguish a planning reserve, a reporting cap and an invoice.
Assign responsibility for agent upgrades, access reviews and investigating delivery gaps. Continue with the incident investigation journey to practice the response path before an incident.