Chapter 4 of 6 · Decisions and boundaries

Continuous evaluation and Foundry platform alerts

Optional module · Draft 3.5 hours

Chapter 4 of 6

Decisions and stop conditions#

Resolve every __REQUIRED_*__ value before a state change. Use team aliases and role names, not personal data.

GateContinue whenStop when
ScopeTargetScope, the Bicep parameter file, and the evaluation decision record name the same approved Foundry account and project boundaryThe account, project, workspace, action route, or resource group differs from the approved scope
Diagnostic settingThe workspace is the approved Log Analytics destination and allLogs is acceptable for the data classificationThe workspace has the wrong retention, access model, region decision, or owner
AlertsThresholds come from baseline telemetry and the action group owner can receive notificationsA threshold lacks an owner, uses the legacy Latency metric, or treats token volume as billed cost
Throttling dimensionThe owner confirms the StatusCode value used for 429 throttling in Metrics ExplorerThe value is unknown, or the alert would split on user, prompt, response, or free text
Continuous evaluationThe evaluator list, maxHourlyRuns, and owner roles are recordedThe project managed identity lacks the Foundry User role, the sampling cap is unresolved, or evaluator names are unapproved
PreviewThe what-if preview contains only the diagnostic setting, action group, and three module-owned alert rulesThe preview changes unrelated resources or targets the wrong group

Do not weaken thresholds or disable sampling to make a result look healthy. Adjust thresholds only after the service owner and AI quality owner review live behavior.

Optional module

Continuous evaluation and Foundry platform alerts slide deck