Skip to content

Commit 2e6237f

Browse files
committed
Billing changes
1 parent b36a8c0 commit 2e6237f

File tree

1 file changed

+9
-1
lines changed

1 file changed

+9
-1
lines changed

azure-local/concepts/billing.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: alkohli
55
ms.author: alkohli
66
ms.topic: conceptual
77
ms.service: azure-local
8-
ms.date: 01/28/2025
8+
ms.date: 04/28/2025
99
---
1010

1111
# Azure Local billing and payment
@@ -37,6 +37,14 @@ To determine how many cores are present in a system, Azure Local periodically ch
3737

3838
To manually upload core data to Azure, use the **`Sync-AzureStackHCI`** cmdlet.
3939

40+
## Billing changes for 12.2504.1001.20 and later
41+
42+
For any new deployments running solution version 12.2504.1001.20 and later, the usage record originates from the Azure Local resource in Azure directly.
43+
44+
If you shut down or decommission your system without deleting the Azure Local resource in Azure, billing continues until the Azure Local resource in Azure is in a disconnected state for over 31 days.
45+
46+
To avoid unexpected charges, you must delete the Azure Local resource in Azure when you decide to decommission the cluster. If you need to deploy the service again, you must go through the Azure Local deployment process. For more information, see [Deploy Azure Local](../deploy/deploy-via-portal.md).
47+
4048
## FAQ
4149

4250
- If I already have an Azure subscription, can I use it for Azure Local? **Yes**

0 commit comments

Comments
 (0)