Overview
The orchestrator hasn't produced a summary yet. Try Run AI Analysis from the source view.
See roadmapPosted by you · 6/3/2026, 7:28:19 PM · cloud: unknown
No inventory row matched the hint — across the 4-tier federated search (exact external-id, suffix on external-id, exact name, substring on name). The investigation can still run on the free-text body — but evidence-gathering tied to a specific Resource (topology, identity reach, flow logs) will be skipped until you either re-submit with a different hint or grant the SP broader scope so discovery indexes the missing resource.
Run an Investigation against this issue. We'll gather deterministic evidence — topology / blast radius, identity bindings, change events in the last 30 days, and related findings on graph neighbours — and persist them on a new Investigation row so the 12-tab workspace renders against real data. Read-only; no cloud writes. Note: no resource resolved yet, so evidence will be limited to the free-text body. Adding a resource hint or external id sharpens the result.
The orchestrator hasn't produced a summary yet. Try Run AI Analysis from the source view.
See roadmapManual issue posted 6/3/2026
View manual issue detail →The subject isn't tied to a resolved resource yet. Federated cloud search (M3) lights this up.
See roadmapNeo4j topology mirror not yet populated for this resource. Native for Azure VM/AKS/NSG/PE today; AWS/GCP arrive in M6/M8.
See roadmapEffective rules + observed flow logs land with M3 (live config) + M10 (live traffic).
See roadmapIAM / RBAC bindings touching this resource will appear here once the IdentityRoleBinding ingest finishes the relevant scopes.
See roadmapLog Analytics / CloudWatch / Cloud Logging queries scoped to this resource. Azure shipped; AWS/GCP wait for M6/M8.
See roadmapBlast radius (1-hop + 2-hop) + business services derived from Neo4j topology. Available for Azure resources; AWS/GCP next.
See roadmapRecommendation bundle generator (Phase A item #3) populates primary / safer-but-slower / phased / blocked here once the orchestrator runs.
See roadmapPer-style code blocks (Portal / CLI / PowerShell / Terraform / CloudFormation / gcloud / kubectl / yaml) populate here once a bundle-aware playbook fires. 24 / 24 shipped playbooks now emit this shape.
See roadmapEach recommendation gets pre-check + during + post-check + rollback steps. Populated once the bundle-aware playbook fires.
See roadmapThe orchestrator hasn't flagged any unknowns for this investigation. That's either good (full evidence) or bad (the orchestrator hasn't run yet).
See roadmap