Assessment & Performance

Use this section to turn workload inventory and telemetry into prioritized engineering work. Assessments evaluate controls and framework mappings, Performance Profiler ranks metric bottlenecks, and FMEA records design failure modes and follow-up actions.

Assessment entry point — overall posture, pillars, and individual controls
Assessment entry point — overall posture, pillars, and individual controls. The synthetic Commerce PROD report shows a score alongside pillar results, evaluated controls, and owner/finding context. Use Assessments for this control-based view, Performance Profiler for metric bottlenecks, and FMEA for failure-mode analysis. These fixture scores and mappings are not an executed assessment, certification, or verified risk conclusion. Synthetic example data; names, identifiers and measurements do not describe a live tenant. View full-size screenshot.

In this section

Guide Use it to
Assessments Run control catalogs, interpret scores, manage waivers, and export reports.
Performance Profiler Compare Azure Monitor observations with AMBA-aligned thresholds and rank candidate bottlenecks.
FMEA Score failure modes with severity, occurrence, detection, and RPN.
  1. Confirm the workload scope and cached inventory.
  2. Run an assessment to establish a posture baseline.
  3. Use Performance Profiler when telemetry suggests capacity or latency risk.
  4. Build an FMEA from reviewed architecture memory and assign follow-up owners.
  5. Re-run periodically and compare results rather than treating one run as permanent truth.

Shared safety model

Results reflect the selected scope, available permissions, cached inventory, and source freshness. A passing control or healthy metric does not prove that a workload is risk-free. AI summaries and generated FMEA rows require human review. Exports may contain resource names and operational findings; handle them according to your organization’s data-classification policy.

The trust models differ: an assessment can finish succeeded with errored controls and provisional completeness, while profiler partial/failed attempts do not replace its latest complete-success posture. FMEA Published is a document lifecycle marker, not automated proof of reviewed controls. See the assessment catalog and limits before comparing totals or scores across these features.

Table of contents

Back to top

Azure Support Agent is open source under the MIT License.

This site uses Just the Docs, a documentation theme for Jekyll.