What the assessment uses
Resource configuration, observed CPU and memory behavior, and workload context support an assessment. Observation times and gaps matter. This description is not an exhaustive inventory of stored fields or telemetry.
What to confirm before granting access
- The data fields collected, stored, and displayed for your environment.
- Hosting and processing locations, subprocessors, and applicable contractual terms.
- Retention for raw telemetry, assessment history, decisions, support records, and backups.
- The process and timing for access withdrawal, account closure, and data deletion.
These policy details remain unresolved for launch. No retention period, deletion deadline, residency guarantee, security certification, or compliance status is promised in this guide.
Revocation is different from deletion
Removing Azure role assignments changes future access. It does not itself delete historical assessments or cancel a subscription. Use the access-withdrawal checklist and request the applicable data-deletion process separately.
Share less when asking for help
Send the error, time, and action with identifying details redacted. Never send credentials, keys, tokens, or unredacted telemetry logs. Confirm the approved data-handling notice and verified contact route before sharing sensitive operational material.