Skip to content

Commit 3e05e7e

Browse files
authored
Acrolinx and list style fix
1 parent aed7776 commit 3e05e7e

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/sql-server/azure-arc/manage-pay-as-you-go-transition.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -20,9 +20,9 @@ This article explains how to transition the SQL Server instances to pay-as-you-g
2020

2121
If your SQL Server instances are covered by a license with Software assurance or a subscription license, typically you want to transition to a pay-as-you-go Azure subscription immediately after the expiration time. At that point you want to make sure that:
2222

23-
1. All Arc SQL deployments are switched to pay-as-you-go billing.
24-
1. All Azure SQL deployments (PaaS and IaaS) are switched to pay-as-you-go billing.
25-
1. The transition tasks are executed immediately after the license agreement expiration for continuous compliance and accurate billing.
23+
- All Arc SQL deployments are switched to pay-as-you-go billing.
24+
- All Azure SQL deployments (PaaS and IaaS) are switched to pay-as-you-go billing.
25+
- The transition tasks are executed immediately after the license agreement expiration for continuous compliance and accurate billing.
2626

2727
To manage the transition follow these steps.
2828

@@ -86,7 +86,7 @@ These charges use separate recurring pay-as-you-go (`PAYG`) meters to track usag
8686

8787
### Intermittent use of SQL Server
8888

89-
If you an application is infrequently used and can be offline longer than 30 days, it will trigger recurring billing because the SQL Arc service cannot tell if the disconnection is intentional or not. To prevent billing, disconnect the SQL Server instance from Azure Arc. When the VM is up and running, you will need to onboard it to Arc again using any of the supported methods. For details, review [Disconnect SQL Server instances from Azure Arc](delete-from-azure-arc.md).
89+
If you have an application that's infrequently used and can be offline longer than 30 days, it will trigger recurring billing because the SQL Arc service cannot tell if the disconnection is intentional or not. To prevent billing, disconnect the SQL Server instance from Azure Arc. When the VM is up and running, you will need to onboard it to Arc again using any of the supported methods. For details, review [Disconnect SQL Server instances from Azure Arc](delete-from-azure-arc.md).
9090

9191
### Solution overview
9292

0 commit comments

Comments
 (0)