You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/cost-management-billing/scope-level/create-sql-license-assignments.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Create SQL Server license assignments for Azure Hybrid Benefit
3
3
description: This article explains how to create SQL Server license assignments for Azure Hybrid Benefit.
4
4
author: bandersmsft
5
5
ms.author: banders
6
-
ms.date: 04/18/2023
6
+
ms.date: 04/20/2023
7
7
ms.topic: how-to
8
8
ms.service: cost-management-billing
9
9
ms.subservice: ahb
@@ -25,7 +25,7 @@ The following prerequisites must be met to create SQL Server license assignments
25
25
- Your organization has a supported agreement type and supported offer.
26
26
- You're a member of a role that has permissions to assign SQL licenses.
27
27
- Your organization has SQL Server core licenses with Software Assurance or core subscription licenses available to assign to Azure.
28
-
- Your organization is enrolled to automatic registration of the Azure SQL VMs with the IaaS extension. To learn more, see [Automatic registration with SQL IaaS Agent extension](/azure/azure-sql/virtual-machines/windows/sql-agent-extension-automatic-registration-all-vms).
28
+
- Your organization is already enrolled to automatic registration of the Azure SQL VMs with the IaaS extension. To learn more, see [SQL IaaS extension registration options for Cost Management administrators](sql-iaas-extension-registration.md).
29
29
> [!IMPORTANT]
30
30
> Failure to meet this prerequisite will cause Azure to produce incomplete data about your current Azure Hybrid Benefit usage. This situation could lead to incorrect license assignments and might result in unnecessary pay-as-you-go charges for SQL Server licenses.
Copy file name to clipboardExpand all lines: articles/cost-management-billing/scope-level/overview-azure-hybrid-benefit-scope.md
+4-6Lines changed: 4 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: Azure Hybrid Benefit is a licensing benefit that lets you bring you
4
4
keywords:
5
5
author: bandersmsft
6
6
ms.author: banders
7
-
ms.date: 04/19/2023
7
+
ms.date: 04/20/2023
8
8
ms.topic: overview
9
9
ms.service: cost-management-billing
10
10
ms.subservice: ahb
@@ -79,7 +79,7 @@ Resource-level Azure Hybrid Benefit management can cover all of those points, to
79
79
You get the following benefits:
80
80
81
81
-**A simpler, more scalable approach with better control** - The billing administrator directly assigns available licenses to one or more Azure scopes. The original approach, at a large scale, involves coordinating Azure Hybrid Benefit usage across many resources and DevOps owners.
82
-
-**An easy-to-use way to optimize costs** - An Administrator can monitor Azure Hybrid Benefit utilization and directly adjust licenses assigned to Azure. Track SQL Server license utilization and optimize costs with tools and resources to proactively identify other licensesto maximize savings and receive notifications when licenses agreements need to be refreshed. For example, an administrator might see an opportunity to save more money by assigning more licenses to Azure. Then they speak with their procurement department to confirm license availability. Finally, they can easily assign the licenses to Azure and start saving.
82
+
-**An easy-to-use way to optimize costs** - An Administrator can monitor Azure Hybrid Benefit utilization and directly adjust licenses assigned to Azure. Track SQL Server license utilization and optimize costs to proactively identify other licenses. It helps to maximize savings and receive notifications when license agreements need to be refreshed. For example, an administrator might see an opportunity to save more money by assigning more licenses to Azure. Then they speak with their procurement department to confirm license availability. Finally, they can easily assign the licenses to Azure and start saving.
83
83
-**A better method to manage costs during usage spikes** - You can easily scale up the same resource or add more resources during temporary spikes. You don't need to assign more SQL Server licenses (for example, closing periods or increased holiday shopping). For short-lived workload spikes, pay-as-you-go charges for the extra capacity might cost less than acquiring more licenses to use Azure Hybrid Benefit for the capacity. When you manage the benefit at a scope, rather than at a resource-level, helps you to decide based on aggregate usage.
84
84
-**Clear separation of duties to sustain compliance** - In the resource-level Azure Hybrid Benefit model, resource owners might select Azure Hybrid Benefit when there are no licenses available. Or, they might *not* select the benefit when there *are* licenses available. Scope-level management of Azure Hybrid Benefit solves this situation. The billing admins that manage the benefit centrally are positioned to confirm with procurement and software asset management departments how many licenses are available to assign to Azure. The following diagram illustrates the point.
85
85
@@ -91,9 +91,7 @@ Both SQL Server Enterprise (core) and SQL Server Standard (core) licenses with S
91
91
92
92
One rule to understand: One SQL Server Enterprise Edition license has the same coverage as _four_ SQL Server Standard Edition licenses, across all qualified Azure SQL resource types.
93
93
94
-
To explain how it works further, the term _normalized core_ or NC is used. In alignment with the rule, one SQL Server Standard core license produces one NC. One SQL Server Enterprise core license produces four NCs. For example, if you assign four SQL Server Enterprise core licenses and seven SQL Server Standard core licenses, your total coverage and Azure Hybrid Benefit discounting power is equal to 23 NCs (4\*4+7\*1).
95
-
96
-
The following table summarizes how many NCs you need to fully discount the SQL Server license cost for different resource types. Scope-level management of Azure Hybrid Benefit strictly applies the rules in the product terms, summarized as follows.
94
+
The following table summarizes how many normalized cores (NCs) you need to fully discount the SQL Server license cost for different resource types. Scope-level management of Azure Hybrid Benefit strictly applies the rules in the product terms, summarized as follows.
97
95
98
96
|**Azure Data Service**|**Service tier**|**Required number of NCs**|
99
97
| --- | --- | --- |
@@ -109,7 +107,7 @@ The following table summarizes how many NCs you need to fully discount the SQL S
109
107
110
108
¹ *Azure Hybrid Benefit isn't available in the serverless compute tier of Azure SQL Database.*
111
109
112
-
² *Subject to a minimum of four vCores per Virtual Machine, which translates to four NC if Standard edition is used, and 16 NC if Enterprise edition is used.*
110
+
² *Subject to a minimum of four vCores per Virtual Machine, which translates to four NCs if Standard edition is used, and 16 NCs if Enterprise edition is used.*
Copy file name to clipboardExpand all lines: articles/cost-management-billing/scope-level/sql-iaas-extension-registration.md
+28-12Lines changed: 28 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: This article explains the SQL IaaS extension registration options a
4
4
keywords:
5
5
author: bandersmsft
6
6
ms.author: banders
7
-
ms.date: 04/19/2023
7
+
ms.date: 04/20/2023
8
8
ms.topic: conceptual
9
9
ms.service: cost-management-billing
10
10
ms.subservice: ahb
@@ -13,9 +13,18 @@ ms.reviewer: chrisrin
13
13
14
14
# SQL IaaS extension registration options for Cost Management administrators
15
15
16
+
This article helps Cost Management administrators understand and address the SQL IaaS registration requirement before they use centrally managed Azure Hybrid Benefit for SQL Server. The article explains the steps that you, or someone in your organization, uses to complete to register SQL Server with the SQL IaaS Agent extension. Here’s the order of steps that you follow. We cover the steps with more detail later in the article.
17
+
18
+
1. Determine whether you already have the required Azure permissions needed. You attempt to check to verify that registration is already done.
19
+
1. If you don't have the required permissions, you must find someone in your organization that has the required permissions to help you.
20
+
1. Complete the check to verify whether registration is already done for your subscriptions. If registration is done, you can go ahead to use centrally managed Azure Hybrid Benefit.
21
+
1. If registration isn’t complete, then you or the person assisting you need to choose one of the options to complete the registration.
22
+
23
+
## Before you begin
24
+
16
25
Normally, you can use the Azure portal to view Azure VMs that are running SQL Server on the [SQL virtual machines page](https://portal.azure.com/#blade/HubsExtension/BrowseResource/resourceType/Microsoft.SqlVirtualMachine%2FSqlVirtualMachines). However, there are some situations where Azure can't detect that SQL Server is running in a virtual machine. The most common situation is when SQL Server VMs are created using custom images that run SQL Server 2014 or earlier. Or if the [SQL CEIP service](/sql/sql-server/usage-and-diagnostic-data-configuration-for-sql-server) is disabled or blocked.
17
26
18
-
When the Azure portal doesn't detect SQL Server running on your VMs, it's a problem because you can't fully manage Azure SQL. In this situation, you can't verify that you have enough licenses needed to cover your SQL Server usage. Microsoft provides a way to resolve this problem, with _SQL IaaS Agent extension registration_. At a high level, SQL IaaS Agent extension registration works in the following manner:
27
+
When the Azure portal doesn't detect SQL Server running on your VMs, it's a problem because you can't fully manage Azure SQL. In this situation, you can't verify that you have enough licenses needed to cover your SQL Server usage. Microsoft provides a way to resolve this problem with _SQL IaaS Agent extension registration_. At a high level, SQL IaaS Agent extension registration works in the following manner:
19
28
20
29
1. You give Microsoft authorization to detect SQL VMs that aren't detected by default.
21
30
2. The registration process runs at a subscription level or overall customer level. When registration completes, all current and future SQL VMs in the registration scope become visible.
@@ -27,18 +36,23 @@ You must complete SQL IaaS Agent extension registration before you can use [cent
27
36
28
37
## Scenarios and options
29
38
30
-
The following sections help Cost Management users understand how SQL IaaS Agent extension registration relates to centralized Azure Hybrid Benefit. Your first step is to determine whether your SQL Server VMs are already registered. Then, you register your SQL Server VMs.
39
+
The following sections help Cost Management users understand their options and the detailed steps for how to complete SQL IaaS Agent extension registration.
31
40
32
-
### Required permissions
41
+
##Determine your permissions
33
42
34
43
You must have client credentials used to view or register your virtual machines with any of the following Azure roles:
44
+
35
45
-**Virtual Machine contributor**
36
46
-**Contributor**
37
47
-**Owner**
38
48
39
-
The permissions are required to perform the following procedure. If you don't have the required permission, contact someone that has the required roles.
49
+
The permissions are required to perform the following procedure.
40
50
41
-
### Determine if SQL Server VMs are already registered
51
+
## Inadequate permission
52
+
53
+
If you don’t have the required permission, get assistance from someone that has one of the required roles.
54
+
55
+
## Complete the registration check
42
56
43
57
1. Navigate to the [SQL virtual machines](https://portal.azure.com/#blade/HubsExtension/BrowseResource/resourceType/Microsoft.SqlVirtualMachine%2FSqlVirtualMachines) page in the Azure portal.
44
58
2. Select **Automatic SQL Server VM registration** to open the **Automatic registration** page.
@@ -47,14 +61,16 @@ The permissions are required to perform the following procedure. If you don't ha
47
61
48
62
Alternatively, you can run a PowerShell script to determine if there are any unregistered SQL Servers in your environment. You can download the script from the [azure-hybrid-benefit](https://github.com/microsoft/sql-server-samples/tree/master/samples/manage/azure-hybrid-benefit) page on GitHub.
49
63
64
+
## Options to complete registration
65
+
50
66
If you determine that you have unregistered SQL Server VMs, use one of the two following methods to complete the registration:
51
67
52
-
- Register with the help of your Microsoft account team
53
-
- Turn on SQL IaaS Agent extension automatic registration
68
+
-[Register with the help of your Microsoft account team](register-with-the-help-of-your-microsoft-account-team)
69
+
-[Turn on SQL IaaS Agent extension automatic registration](turn-ons-sql-iaas-agent-extension-automatic-registration)
54
70
55
71
### Register with the help of your Microsoft account team
56
72
57
-
The most comprehensive way to register is at the overall customer level. For both of the following options, contact your Microsoft account team.
73
+
The most comprehensive way to register is at the overall customer level. For both of the following situations, contact your Microsoft account team.
58
74
59
75
- Your Microsoft account team can help you add a small amendment that accomplishes the authorization in an overarching way if:
60
76
- If you have an Enterprise Agreement that's renewing soon
@@ -73,11 +89,11 @@ You can enable automatic registration in the Azure portal for a single subscript
73
89
74
90
## Registration duration and verification
75
91
76
-
After you enable automatic registration, it can take up to 48 hours to detect all your SQL Servers. When complete, all your SQL Server virtual machines should be visible on the [SQL virtual machines](https://portal.azure.com/#blade/HubsExtension/BrowseResource/resourceType/Microsoft.SqlVirtualMachine%2FSqlVirtualMachines) page in the Azure portal.
92
+
After you complete either of the preceding automatic registration options, it can take up to 48 hours to detect all your SQL Servers. When complete, all your SQL Server virtual machines should be visible on the [SQL virtual machines](https://portal.azure.com/#blade/HubsExtension/BrowseResource/resourceType/Microsoft.SqlVirtualMachine%2FSqlVirtualMachines) page in the Azure portal.
77
93
78
-
## After registration completes
94
+
## When registration completes
79
95
80
-
After SQL IaaS Extension registration is complete, we recommended you use Azure Hybrid Benefit for centralized management.
96
+
After you complete the SQL IaaS Extension registration, we recommended you use Azure Hybrid Benefit for centralized management. If you're unsure whether registration is finished, you can use the steps in [Complete the Registration Check](complete-the-registration-check).
0 commit comments