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
title: License SQL Server, Windows Server, and Linux in Azure VMware Solution
3
-
description: This article provides licensing considerations for running SQL Server, Windows Server, and Linux in VMs in Azure VMware Solution. It provides details around utilizing Azure Hybrid Benefits and steps on how to register your SQL Server licenses in the tooling.
3
+
description: Learn about licensing considerations for running SQL Server, Windows Server, and Linux in VMs in Azure VMware Solution and how to utilize Azure Hybrid Benefits and register your SQL Server licenses.
4
4
author: MikeWeiner-Microsoft
5
5
ms.author: michwe
6
6
ms.service: azure-vmware
7
7
ms.topic: how-to
8
8
ms.date: 04/29/2024
9
9
---
10
10
11
-
# License SQL Server, Windows Server, and Linux in Azure VMware Solution
11
+
# License SQL Server, Windows Server, and Linux in Azure VMware Solution
12
12
13
-
This article provides licensing considerations and tooling integration for running SQL Server, Windows Server, and Linux within Azure VMware Solution.
13
+
This article provides licensing considerations and tooling integration for running SQL Server, Windows Server, and Linux within Azure VMware Solution.
14
14
15
-
Included in the pricing of Azure VMware Solution is infrastructure, hosts, and storage along with many VMware licensing components including NSX-T, vSphere, vSAN, and HCX Advanced. There's no added charge in the pricing for any software running in your guest virtual machines(VMs).
15
+
Included in the pricing of Azure VMware Solution is infrastructure, hosts, storage, and many VMware licensing components. These components include NSX-T, vSphere, vSAN, and HCX Advanced. There's no added charge in the pricing for any software running in your guest virtual machines(VMs).
16
16
17
-
To remain compliant, you do need to license the software running in the VMs. For SQL Server, Windows Server, and Linux subscriptions you can use your existing licenses investment to apply them in Azure VMware Solution.
17
+
To remain compliant, you need to license the software running in the VMs. For SQL Server, Windows Server, and Linux subscriptions, you can use your existing licenses and apply them in Azure VMware Solution.
18
18
19
-
In addition, with [Software Assurance](https://www.microsoft.com/Licensing/licensing-programs/software-assurance-by-benefits) or an active Linux subscription you can take advantage of [Azure Hybrid Benefit](https://azure.microsoft.com/pricing/hybrid-benefit/)not only allowing for you to use any existing licenses, but including another benefits around migration and unlimited virtualization.
19
+
With [Software Assurance](https://www.microsoft.com/Licensing/licensing-programs/software-assurance-by-benefits) or an active Linux subscription, you can also take advantage of [Azure Hybrid Benefit](https://azure.microsoft.com/pricing/hybrid-benefit/) for other benefits around migration and unlimited virtualization.
20
20
21
21
> [!NOTE]
22
-
> If you do not have Software Assurance you need to apply the terms around licensing provided in:[Updated Microsoft licensing terms for dedicated hosted cloud services](https://www.microsoft.com/en-us/licensing/news/updated-licensing-rights-for-dedicated-cloud). This will limit the licenses which can be applied based on terms applied after October 1st, 2019 along with additional migration and virtualization benefits.
22
+
> If you don't have Software Assurance, you need to apply the terms for licensing that are provided in [Updated Microsoft licensing terms for dedicated hosted cloud services](https://www.microsoft.com/en-us/licensing/news/updated-licensing-rights-for-dedicated-cloud). These terms limit the licenses that can be applied based on terms applied after October 1, 2019, and other migration and virtualization benefits.
23
23
24
-
The rest of this article discusses SQL Server and Windows Server licensing considerations in Azure VMware Solution with Software Assurance and Azure Hybrid Benefit applied.
24
+
The remainder of this article discusses SQL Server and Windows Server licensing considerations in Azure VMware Solution with Software Assurance and Azure Hybrid Benefit applied.
25
25
26
26
> [!IMPORTANT]
27
-
> The Microsoft Product Terms for specific programs and software take precedent over this article and may contain more detailed content specific to that product. For more information, select your specific program under:
27
+
> The Microsoft Product Terms for specific programs and software take precedence over this article and might contain more content specific to that product. For more information, select your specific program under:
28
28
>
29
29
>-[SQL Server Product Terms](https://www.microsoft.com/licensing/terms/productoffering/SQLServer/EAEAS)
30
30
>
@@ -33,73 +33,73 @@ The rest of this article discusses SQL Server and Windows Server licensing consi
You can use the following licenses for SQL Server and Windows Server to apply to software running in Azure VMware Solution.
36
+
You can use the following licenses for SQL Server and Windows Server to apply to software running in Azure VMware Solution:
37
37
38
-
-****Windows Server**** - Standard or Datacenter core licenses OR Standard/Datacenter processor licenses, where each processor license is equivalent to 16 core licenses.
38
+
-**Windows Server**: Standard or Datacenter core licenses or Standard/Datacenter processor licenses, where each processor license is equivalent to 16 core licenses.
39
+
-**SQL Server**: Standard or Enterprise core licenses.
39
40
40
-
-****SQL Server**** - Standard or Enterprise core licenses.
41
+
## Dual-use rights for Azure Migration
42
+
Migration to Azure VMware Solution is usually executed over an extended time-frame instead of at a single point in time. To give you flexibility around your migration timelines, you can continue to use your licenses outside of Azure for 180 days from the time when the licenses are allocated within Azure VMware Solution. This dual-use rights benefit applies to SQL Server and Windows Server.
41
43
42
-
## Dual Use Rights for Azure Migration
43
-
Migration to Azure VMware Solution is usually executed over an extended timeframe instead of at a single point-in-time. To give you flexibility around your migration timelines, you can continue to use your licenses outside of Azure for 180 days from when the licenses are allocated within Azure VMware Solution. This dual use rights benefit applies to SQL Server and Windows Server.
44
+
For more information and other considerations for dual-use rights outside of migration, see [Azure Product Terms](https://www.microsoft.com/licensing/terms/productoffering/MicrosoftAzure/EAEAS).
44
45
45
-
For more information and other considerations for dual use rights outside of migration, see [Azure Product Terms](https://www.microsoft.com/licensing/terms/productoffering/MicrosoftAzure/EAEAS).
46
+
## License the host physical cores by using unlimited virtualization rights
47
+
Unlimited virtualization allows you to license the physical cores on the host and run as many VMs with Windows Server or SQL Server as you can. You're limited only by host capacity. Unlimited virtualization can provide licensing cost optimization for the following scenarios:
46
48
47
-
## License the host physical cores - Unlimited Virtualization Rights
48
-
Unlimited virtualization allows you to license the physical cores on the host and run as many VMs with Windows Server and/or SQL Server as you can, limited only by host capacity. It can provide licensing cost optimization for environments with scenarios such as:
49
-
- The host contains a high density of VMs
50
-
- The host contains dynamic provisioning or deprovisioning of VMs
49
+
- The host contains a high density of VMs.
50
+
- The host contains dynamic provisioning or deprovisioning of VMs.
51
51
52
-
By applying existing SQL Server Enterprise and/or Windows Server Datacenter licenses to cover the physical cores of any host you can achieve unlimited virtualization of that host. Each host is required to have licenses applied to all the physical cores.
52
+
By applying existing SQL Server Enterprise or Windows Server Datacenter licenses to cover the physical cores of any host, you can achieve unlimited virtualization of that host. Each host is required to have licenses applied to all the physical cores.
53
53
54
-
While Standard licenses for SQL Server and Windows Server can't be used for unlimited virtualization, they can be applied to license an individual VM discussed in the next section.
54
+
Standard licenses for SQL Server and Windows Server can't be used for unlimited virtualization, but they can be applied to license an individual VM. This use is discussed in the next section.
55
55
56
-
## License a Virtual Machine virtual cores
57
-
You need to license each machine individually applying licenses based on the number of virtual cores (v-Core) associated with the VM.
56
+
## License a virtual machine based on virtual cores
57
+
You need to license each machine individually by applying licenses based on the number of virtual cores associated with the VM.
58
58
59
-
Either Enterprise or Standard licenses can be applied for SQL Server and either Standard and Datacenter licenses for Windows.
59
+
Either Enterprise or Standard licenses can be applied for SQL Server. Standard and Datacenter licenses can be applied for Windows.
60
60
61
-
Applying licenses at the VM scope could fit your needs for scenarios such as
62
-
- The hosts aren't densely packed with VMs running the respective software. The overall licensing cost in this case could be more cost effective than licensing an entire host.
63
-
- You are running Standard editions of SQL Server and/or Windows Server and therefore have these existing licenses to apply.
61
+
Applying licenses at the VM scope could meet your needs for the following scenarios:
64
62
65
-
Each VM does require a minimum number of licenses to be applied:
63
+
- The hosts aren't densely packed with VMs running the respective software. The overall licensing cost in this case could be more cost effective than licensing an entire host.
64
+
- You're running Standard editions of SQL Server or Windows Server, so you have these existing licenses to apply.
66
65
67
-
-****Windows Server**** - You need a minimum of 8 core licenses (Datacenter or Standard) per VM. For example, 8 core licenses are still required if you run a 4-core VM. You may also run VMs larger than 8 cores by allocating licenses equal to the core size of the VM. For example, 12 core licenses are required for a 12-core VM.
66
+
Each VM requires a minimum number of licenses to be applied:
68
67
69
-
-****SQL Server**** - A minimum of 4 core licenses (Enterprise or Standard) per VM.
68
+
-**Windows Server**: You need a minimum of 8 core licenses (Datacenter or Standard) per VM. For example, 8 core licenses are still required if you run a 4-core VM. You might also run VMs larger than 8 cores by allocating licenses equal to the core size of the VM. For example, 12 core licenses are required for a 12-core VM.
69
+
-**SQL Server**: A minimum of 4 core licenses (Enterprise or Standard) per VM.
70
70
71
-
### How to register licenses in Azure VMware Solution
71
+
### Register licenses in Azure VMware Solution
72
72
#### SQL Server
73
-
##### License the host - Unlimited Virtualization
74
-
You can enable Azure Hybrid Benefit for SQL Server and achieve unlimited virtualization through an Azure VMware Solution placement policy. The details on how to create the VM-Host placement policy are located here: [Enable Unlimited Virtualization with Azure Hybrid Benefit for SQL Server in Azure VMware Solution.](https://learn.microsoft.com/azure/azure-vmware/enable-sql-azure-hybrid-benefit)
73
+
##### License the host by using unlimited virtualization
74
+
You can enable Azure Hybrid Benefit for SQL Server and achieve unlimited virtualization through an Azure VMware Solution placement policy. For information on how to create the VM-Host placement policy, see [Enable unlimited virtualization with Azure Hybrid Benefit for SQL Server in Azure VMware Solution](https://learn.microsoft.com/azure/azure-vmware/enable-sql-azure-hybrid-benefit).
75
75
76
76
##### License a virtual machine
77
-
SQL Server licenses can be registered and applied to VMs running SQL Server in Azure VMware Solution by registering through Azure Arc, through these steps:
78
-
1. Azure VMware Solution must be Arc-enabled: [Deploy Arc-enabled VMware vSphere for Azure VMware Solution](https://learn.microsoft.com/azure/azure-vmware/deploy-arc-for-azure-vmware-solution?tabs=windows). You can Arc-enable the virtual machines and get the Azure Extension for SQL Server applied to that VM by following the steps provided in the section titled *Enable guest management and extension installation*.
79
-
2. When Guest Management is configured, the Azure Extension for SQL Server should be installed on that VM. The extension install enables you to configure the License Type for the SQL Server instance running in the VM.
80
-
3. Once enabled you can configure the License Type and other SQL Server configuration settings from the Azure portal, PowerShell or CLI for a specific Arc-enabled server. To configure from the Azure portal, VMware vSphere in Azure VMware Solution experience, follow the steps:
77
+
You can register SQL Server licenses and apply them to VMs running SQL Server in Azure VMware Solution by registering through Azure Arc:
78
+
1. Azure VMware Solution must be Azure Arc-enabled. For more information, see [Deploy Azure Arc-enabled VMware vSphere for Azure VMware Solution](https://learn.microsoft.com/azure/azure-vmware/deploy-arc-for-azure-vmware-solution?tabs=windows). You can Azure Arc-enable the VMs and get the Azure Extension for SQL Server applied to that VM by following the steps provided in the section titled "Enable guest management and extension installation."
79
+
1. When **Guest Management** is configured, the Azure Extension for SQL Server should be installed on that VM. The extension installation enables you to configure the license type for the SQL Server instance running in the VM.
80
+
1. Now you can configure the license type and other SQL Server configuration settings by using the Azure portal, PowerShell, or the Azure CLI for a specific Azure Arc-enabled server. To configure from the Azure portal with VMware vSphere in the Azure VMware Solution experience, follow these steps:
81
81
82
-
1. In the Azure VMware Solution portal, go to **vCenter Server Inventory** and **Virtual Machines** clicking through one of the Arc-enabled VMs. Here you see the Machine-Azure Arc (AVS) page.
83
-
2. In the left pane, expand Operations and you should see the SQL Server Configuration
84
-
3. You can now apply and save your License Type for the VM along with other server configurations
82
+
1. In the Azure VMware Solution portal, go to **vCenter Server Inventory** and **Virtual Machines**by clicking through one of the Azure Arc-enabled VMs. The **Machine-Azure Arc (AVS)** page appears.
83
+
1. On the left pane, under **Operations**, select **SQL Server Configuration**.
84
+
1. You can now apply and save your license type for the VM along with other server configurations.
85
85
86
-
You can also configure these setting within the Azure Arc portal experience and from PowerShell or CLI. The Azure Arc portal experience and code to update the configuration values is provided here: [Configure SQL Server enabled by Azure Arc.](https://learn.microsoft.com/sql/sql-server/azure-arc/manage-configuration?view=sql-server-ver16&tabs=azure)
86
+
You can also configure these settings within the Azure Arc portal experience and by using PowerShell or the Azure CLI. To access the Azure Arc portal experience and code to update the configuration values, see [Configure SQL Server enabled by Azure Arc](https://learn.microsoft.com/sql/sql-server/azure-arc/manage-configuration?view=sql-server-ver16&tabs=azure).
87
87
88
88
> [!NOTE]
89
-
>At this time Azure VMware Solution does not integrate with the **SQLServerLicense** resource type.
89
+
>At this time, Azure VMware Solution doesn't integrate with the `SQLServerLicense` resource type.
90
90
91
-
##### Managing the environment
92
-
Once the Azure Extension for SQL Server is installed, you can query the SQL Server configuration settings and track your SQL Server license inventory for each VM. Sample queries are provided here: [Query SQL Server configuration](https://learn.microsoft.com/sql/sql-server/azure-arc/manage-configuration?view=sql-server-ver16&tabs=azure#query-sql-server-configuration)
91
+
##### Manage the environment
92
+
After the Azure Extension for SQL Server is installed, you can query the SQL Server configuration settings and track your SQL Server license inventory for each VM. For sample queries, see [Query SQL Server configuration](https://learn.microsoft.com/sql/sql-server/azure-arc/manage-configuration?view=sql-server-ver16&tabs=azure#query-sql-server-configuration).
93
93
94
94
#### Windows Server
95
-
Currently there is no way to register your Windows licenses in Azure VMware Solution.
95
+
Currently, there's no way to register your Windows licenses in Azure VMware Solution.
96
96
97
97
### Other cost savings for SQL Server and Windows Server
98
-
In addition to taking advantage of Azure Hybrid Benefit for SQL Server, Windows Server and Linux subscription more cost savings can be realized in Azure VMware Solution through:
99
-
-[Extended Security Updates (ESU) for Windows Server and SQL Server - Azure VMware Solution](https://learn.microsoft.com/azure/azure-vmware/extended-security-updates-windows-sql-server)
100
-
-[Save costs with a reserved instance](https://learn.microsoft.com/azure/azure-vmware/reserved-instance)
98
+
For more cost savings with Azure VMware Solution, see:
-[Extended Security Updates (ESUs) for Windows Server and SQL Server - Azure VMware Solution](https://learn.microsoft.com/azure/azure-vmware/extended-security-updates-windows-sql-server)
101
+
-[Save costs with a reserved instance](https://learn.microsoft.com/azure/azure-vmware/reserved-instance)
0 commit comments