Knowledge Base
Workloads, scope, and coverage
Use these distinctions while the updated interface awaits verification.
← Knowledge BaseInventory is not readiness
A discovered workload is an inventory entry. Selection or inclusion in an assessment scope is a separate question. Neither proves complete telemetry or a published recommendation.
Coverage is not a savings claim
Use the deployed interface’s definitions for scope and coverage. Do not interpret a workload count as evidence that all workloads are actively optimized. Detailed denominator, pooling, capacity, and selection behavior will be documented after deployment verification.
Microsoft-managed workloads
Do not assume an enforced protection or exclusion from a label. Confirm the workload owner and the deployed policy before considering a change. This guide does not promise that RATIVERA prevents recommendations or changes for Microsoft-managed workloads.
Review support availability
One Problem at a Time · Episode 3 · 1:14
Do you know which AKS workloads are consuming your capacity?
Read workload inventory and organization-wide coverage without confusing selection with optimization.
Recorded test-environment figures dated November 4, 2026. The place-count explanation applies to fixed-place subscriptions. Unlimited plans do not count places, and Trials do not have a purchased-place pool. The illustrated 50-place allowance and workload counts are examples, not a plan offer or Trial limit. A Microsoft-managed SYSTEM workload uses a place only when explicitly selected under a fixed-place subscription; RATIVERA offers no changes for it. This is not a workload-protection guarantee.
English captions are burned into the video. An optional English caption track and transcript are also available. Use fullscreen for small screen details.
Workloads and coverage · Supported capability boundaries
Episode page & transcript · Download MP4
