Skip to content

Commit 59643ae

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

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/azure-monitor/logs/restore.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -127,9 +127,9 @@ You can:
127127
- Perform up to four restores per table per week.
128128
129129
## Pricing model
130-
The charge for restored logs is calculated based on the volume of data you restore, in GB, and the duration for which you keep the restored data.
131-
- Charges subject to a minimum of restore data volume.
132-
- Charges are prorated hourly and subject to a minimum of restore duration.
130+
The charge for restored logs is based on the volume of data you restore, in GB, and the duration for which you keep the restored data.
131+
- Charges are subject to a minimum restored data volume.
132+
- Charges are prorated hourly and subject to a minimum restore duration.
133133
- For more information, see [Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor/).
134134
135135
For example, if your table holds 500 GB a day and you restore 10 days of data, you'll be charged for 5000 GB a day until you [dismiss the restored data](#dismiss-restored-data).

0 commit comments

Comments
 (0)