Skip to content

Commit d7fb495

Browse files
committed
remove CSP per Pri
1 parent 845008d commit d7fb495

File tree

1 file changed

+0
-2
lines changed

1 file changed

+0
-2
lines changed

articles/cost-management-billing/scope-level/faq-azure-hybrid-benefit-scope.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -80,8 +80,6 @@ sections:
8080
- Notifications are sent to the EA notification contacts, EA admin, reservation owners, and the reservation administrator.
8181
- Customers with Microsoft Customer Agreement (Azure Plan)
8282
- Notifications are sent to the reservation owners and the reservation administrator.
83-
- Cloud Solution Provider and new commerce partners
84-
- Emails are sent to the partner notification contact.
8583
- question: Can I use the new experience with self-installed SQL Server in Azure virtual machines?
8684
answer: |
8785
The new approach of centrally managing Azure Hybrid Benefit at a scope-level supports SQL Server in Azure Virtual machines. However, it’s essential that you have enabled automatic registration of the self-installed SQL server images with the IaaS extension *before* you assign SQL licenses. The experience includes a feature that informs you about current usage of Azure Hybrid Benefit. And, the usage of SQL licenses that aren’t discounted. Assigning the number of SQL Server licenses at the level of the current usage ensures that you don't experience unexpected pay-as-you-go charges. Because the unregistered SQL VMs aren’t recognized as SQL resources, registering them with the IaaS extension *after* you begin assigning licenses at a scope-level could lead to the license assignments being insufficient to cover the newly recognized SQL VMs. In that case, those *new* SQL VMs from registration might incur unexpected pay-as-you-go charges.

0 commit comments

Comments
 (0)