Skip to main content
When you restore data from long-term retention in a Log Analytics workspace, Azure creates a restored table and bills it per GB for every day it exists, whether or not anyone queries it. Restores are often made for a one-off investigation and then forgotten. nOps finds workspaces that have paid for restored data every day for at least a week and estimates the saving from dismissing the restore.

Why it matters

A forgotten restore keeps billing every day at the same rate, and nothing in the workspace reminds you it is there. Dismissing it does not delete any data: the data stays in long-term retention.

How nOps finds it

nOps reads your pay-as-you-go Log Analytics billing. A workspace is flagged when it was billed for restored data on all of the last 7 complete days and the restore was first billed at least 7 days ago. The saving is what the restore cost over those 7 days, scaled to a month, and must be at least $5 a month. Workspaces whose costs are mostly covered by credits or commitments are left out.

Before you start

Permission to delete tables in the workspace (for example Log Analytics Contributor), and confirmation from the person who ran the restore that the investigation is finished.

How to implement

  1. In the Azure portal, open the Log Analytics workspace and go to Tables. Restored tables end in _RST.
  2. Check with the investigation owner that nobody still queries the restored data.
  3. Delete the restored table from the Tables page, or run az monitor log-analytics workspace table delete --resource-group MY_RG --workspace-name MY_WORKSPACE --name MYTABLE_RST.
  4. Check the next few days of billing to confirm the data restore charge has stopped.

Risks and considerations

  • Deleting a restored table removes it from interactive queries. The original data stays in long-term retention.
  • If you need the data again, you can run a new restore, which is billed again and has a minimum size and duration per restore.
  • nOps cannot see from billing whether the restored data is still being queried, so confirm before deleting.

FAQs

No. Dismissing a restore deletes only the restored copy. The data stays in long-term retention until its total retention period ends.