Loading help…
Sign in with your EntraID account to access the Cloud Maturity Assessment.
Loading internal data...
Computing correlations...
Computing histograms...
CMA scores subscriptions by combining data from 4 sources: Wiz (resources), ITAM (app ownership), Cloudability (costs), and CMDB (metadata). When a source is missing data for a subscription, it creates a quality gap — the issue categories below explain what's missing and what it means for your scores.
my-team-prod (abc123-def456) exists in Wiz with 50 resources, but Cloudability shows $0 spend — likely the account isn't onboarded to Cloudability yet.014543646807 has 20 Lambda functions and 5 EC2 instances in Wiz. CMA estimates CN score as ~80% (20 cloud-native / 25 total) × confidence factor — but the real cost split might be different (EC2 could be 90% of spend).my-sandbox-123 is in Wiz and ITAM, scored at L3 (62%). But no APM application claims it — so it doesn't appear under any app in the Management view. It's counted in subscription-level averages but missing from app-level reporting.APM-00012345 "Customer Portal" is registered as a cloud app in ITAM, but nobody has linked its Azure subscriptions or AWS accounts to it yet. CMA shows it with a dash (—) instead of a maturity score.xyz-789 is scored and linked to an app, but CMA can't determine if it's AWS, Azure, or GCP. Provider-filtered views won't include it, and the provider distribution chart is inaccurate."Production Web Tier", the dashboard shows "a1b2c3d4-e5f6-7890-abcd-ef1234567890". Users can't easily identify which team or workload this belongs to.Loading checks data...
Read-only integrity checks over the whole data lake after an ETL load —
freshness, volume drift, referential integrity, score invariants, uniqueness
and JSON-export parity. Click any check to see what it verifies, its impact
and how to read it; failing checks list the affected subscriptions /
applications (click one to open its detail view).
PASS = healthy ·
WARN = advisory / usually
self-heals on the next full run ·
FAIL = needs attention.
Loading management data...
First request may take a few seconds to warm up
Loading scoring configuration...
| Metric | Weight | % | Target | Status | L5 | L4 | L3 | L2 | L1 |
|---|
| Level | Label | Min Score | Color | Description |
|---|
Four metrics — Database, ARM, OSS and Container — score a simple good ÷ (good + bad) ratio. For example, Cloud Database is managed ÷ (managed + self-hosted). Each of these has a penalty weight parameter that lets you make the “bad” side count for more or less, without changing anything else:
| weight = 1.0 | Neutral — the default. Today's scores are unchanged until you edit this. |
| weight > 1.0 | Stricter — the “bad” side is penalised more, so the score goes down. |
| weight < 1.0 | Tolerant — the “bad” side is penalised less, so the score goes up. |
| Version | Updated By | Updated At | Changes |
|---|
Configure prompts and parameters for the AI Deep Dive analysis. Select a prompt when triggering an analysis, or define custom prompts below.
Agent name is sent to the AI Hub. Change only if you have been given a different agent version.
The prompt marked as default will be pre-selected when triggering AI Deep Dive. You can always choose a different prompt at invocation time.
| Business Unit | Role | Layout | Access Filter | AI Quota | Last Login | Created By | Created |
|---|
IT IPS *, CYS *. Semicolons are also accepted. Wildcards: IT IPS * matches all IT IPS sub-units; * = unrestricted. When enabled but empty, the user sees nothing. Unchecked = unrestricted. Admins always see everything.
Remove from the user store? This does not affect the env-var allow-lists used for live gating.
Loading help…
⚠️ Additional Costs May Apply
Running an AI Deep Dive analysis will incur additional costs in the AI backend infrastructure. This includes API calls, processing time, and storage for the analysis results.
Future Changes: The cost will be charged individually to your cost center.