Skip to content

Commit 52b4f68

Browse files
authored
acrolinx and empty heading
1 parent fbc62fe commit 52b4f68

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/reliability/migrate-monitor-log-analytics.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ This guide describes how to migrate Log Analytics workspaces from non-availabili
1515

1616
> [!NOTE]
1717
> Application Insights resources can also use availability zones, but only if they are workspace-based and the workspace uses a dedicated cluster. Classic (non-workspace-based) Application Insights resources cannot use availability zones.
18-
> ##
18+
1919

2020
## Dedicated clusters
2121

@@ -47,7 +47,7 @@ Transitioning to a new cluster can be a gradual process. Don't remove the previo
4747
Any queries against your workspace queries both clusters as required to provide you with a single, unified result set. As a result, all Azure Monitor features that rely on the workspace, such as workbooks and dashboards, continue to receive the full, unified result set based on data from both clusters.
4848

4949
## Billing
50-
[Dedicated clustrs](../azure-monitor/logs/logs-dedicated-clusters.md#create-a-dedicated-cluster) require a commitment tier starting at 100 GB per day.
50+
[Dedicated clusters](../azure-monitor/logs/logs-dedicated-clusters.md#create-a-dedicated-cluster) require a commitment tier starting at 100 GB per day.
5151

5252
The new cluster isn’t billed during its first day to avoid double billing during configuration. Only the data ingested before the migration completes would still be billed on the date of migration.
5353

0 commit comments

Comments
 (0)