Skip to content

Commit 1f133eb

Browse files
adiBiranguywi-ms
andauthored
Update articles/azure-monitor/logs/restore.md
Co-authored-by: Guy Wild <[email protected]>
1 parent de221b6 commit 1f133eb

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-monitor/logs/restore.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -140,7 +140,7 @@ You can:
140140
- Run only one active restore on a specific table at a given time. Executing a second restore on a table that already has an active restore will fail.
141141

142142
## Pricing model
143-
Maintaining restored logs incurs a pro-rated cost per day and per GB based on the time the data is kept restored and the amount of data restored (subject to the minimal restore duration and data volume). There is no charge for querying against restored logs.
143+
The charge for maintaining restored logs is calculated based on the volume of data you restore, in GB, and the number or days for which you restore the data. Charges are prorated and subject to the minimum restore duration and data volume. There is no charge for querying against restored logs.
144144

145145
For example, if your table holds 500 GB a day and you restore 10 days of data, you will be charged for 5000 GB a day until you dismiss the restored data.
146146

0 commit comments

Comments
 (0)