> ## Documentation Index
> Fetch the complete documentation index at: https://help.nops.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Move Azure Log Analytics Workspace to a Commitment Tier

> Move a Log Analytics workspace from pay-as-you-go to a commitment tier that costs less for its daily ingestion.

Log Analytics bills ingested data per GB on pay-as-you-go. Commitment tiers charge a fixed daily price for a set volume (starting at 100 GB a day) at a lower price per GB. Azure Advisor recommends a commitment tier when a workspace's ingestion would cost less on one. nOps imports these recommendations, checks them against your bill, and shows the estimated monthly saving.

| | |
| - | - |
| **Cloud** | Microsoft Azure |
| **Category** | Management and governance |
| **Service** | Log Analytics |
| **Action** | Modify |
| **Effort** | Low |
| **Restart needed** | No |
| **Can be rolled back** | Yes |
| **Analysis window** | Last 7 days |
| **Source** | Azure Advisor |

## Why it matters

Workspaces that ingest steadily above the first tier pay noticeably more per GB on pay-as-you-go.

## How nOps finds it

This recommendation comes from Azure Advisor, which looks at the workspace's recent daily ingestion and recommends a pricing tier. nOps imports Advisor's recommendations daily and checks each one against your own Azure bill for the last 7 complete days: the resource must still be billed in the last 3 days of that window, and Advisor's estimate is capped at what the resource actually cost (Advisor prices at pay-as-you-go rates, so you may pay less through discounts, reservations or savings plans). Recommendations worth less than \$1 a month are left out.

## Before you start

Permission to change the workspace pricing tier, and an idea of how ingestion will change in the coming weeks.

## How to implement

1. Check the workspace's daily ingestion trend in **Usage and estimated costs**.
2. In the Azure portal, open the workspace, go to **Usage and estimated costs → Pricing tier**, and choose the commitment tier shown in the recommendation.
3. Or use `az monitor log-analytics workspace update --resource-group RESOURCE_GROUP --workspace-name WORKSPACE --sku CapacityReservation --capacity-reservation-level GB_PER_DAY`.
4. Update Terraform, Bicep or ARM templates so a later deployment does not change it back.

## Risks and considerations

* You pay the full tier every day, even on days you ingest less. Ingestion above the tier is billed at the tier's per-GB rate.
* After choosing a tier, you cannot lower it or go back to pay-as-you-go for 31 days.
* If several workspaces in one region together ingest a lot, a dedicated cluster commitment tier may save more.

## Related

* [Use a Log Analytics Dedicated Cluster Commitment Tier](https://help.nops.io/inform/supported-recommendations/use-a-log-analytics-dedicated-cluster-commitment-tier)
* [Move Older Log Analytics Data to Long-Term Retention](https://help.nops.io/inform/supported-recommendations/move-older-log-analytics-data-to-long-term-retention)
* [Supported recommendations](https://help.nops.io/inform/supported-recommendations.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.