Forgot to delete the resource

Problem

Recently the team were working on an issue with an internal application and they had created a database to do some performance testing.  They worked hard and resolved the performance issue.

The problem was they had not deleted the test database or scaled it down when the exercise was completed.

Analysis

In our cost review this resource flagged up as being Idle.  The database was configured with a relatively high sku so we were paying for it but the developer had been reallocated to another activity and had not cleaned up fully.  This database was left lying around and we would have paid for it until we got rid of it.

You can see below that its easy to spot the resource when the team completes their cost review.

The team can also open up the database usage metrics to validate that it is unused.

Solution

Using Turbo360 we were easily able to identify resources which are idle and we were able to delete them and stop paying for this database which was a left over from a testing activity.