[FEATURE] Azure - Unused Bastion instacces

[aflatto]

Feature Description

Check for unsued Bastion instances ( Azure)

Problem It Solves

Bastion is a service that is brought up and forgotten but costs around $160/Month.

Proposed Solution

Check for the connections to the bastion, if 0 in the last 30 days, flag it.

Cloud Provider

• AWS

• Azure

• GCP

• Multi-cloud

• Provider-agnostic

  Priority (your perspective)

• Critical (blocking my workflow)

• High (would significantly improve my workflow)

• Medium (nice to have)

• Low (minor improvement)

[sureshcsdp]

Hi @aflatto

Thanks - this is a really good hygiene rule suggestion.

Idle Azure Bastion hosts are definitely one of those "forgotten but still billing" resources, especially given the monthly baseline cost.

The proposed logic of:

• detecting Bastion resources
• checking connection/session activity over a period (for example 30 days)
• flagging instances with no activity

makes sense from a hygiene perspective.

One thing I need to validate is the reliability and availability of Bastion connection metrics across different configurations/SKUs, since CleanCloud tries to keep rules deterministic and low-noise.

I'll investigate what telemetry Azure exposes here and whether this can be implemented in a trustable/read-only way.