This page covers the most frequently asked questions (FAQ) about licensing forthe following Microsoft workloads on Google Cloud:

• Windows Server FAQ
• SQL Server FAQ
• Windows Desktop OS FAQ
• Microsoft Office FAQ

Windows Server on Google Cloud FAQ

What are my options for running Windows Server on Google Cloud?

Windows Server is available using on-demand licenses available on prebuiltimages in Compute Engine, or as an attached license string to custom imagesduring image import. Additionally, you might be able to bring your own license(BYOL) of a Windows Server if it meets the eligibility requirements. For moreinformation, seeBYOL Windows Server FAQ.

On-demand Windows Server FAQ

How do I use on-demand licensing on my Windows Server instances?

There are two primary ways to enable on-demand licensing for your instances:

• Prebuilt images from Google Cloud: When you use a prebuilt Windows Server,or SQL Server image from theCompute Engine image catalog, or fromGoogle Cloud Marketplace,Google provides an on-demand license and attaches it to the image. Google Cloudmanages the reporting and compliance requirements so that you can get startedwith these Microsoft products quickly.
• Custom images: When you bring your own Windows Server or SQL Server image,you can attach a Google-provided on-demand license during theimport ormigrationprocess. TheLicense section of theOperating system details page forWindows Server andSQL Server contains licensestrings for each software version. If you use Google-provided on-demandlicenses for SQL Server on Windows Server, you must attach a license stringfor each software.

How does billing for on-demand Windows Server instances work?

When you create a Windows Server or SQL Server instance that includes on-demandlicensing, Microsoft Windows Server license stock-keeping units (SKUs) are added alongside the base Compute Engineresource SKUs. A core license is charged for each virtual CPU enabled in theinstance. Reducing the number of virtual CPUs in your instance bydisabling simultaneous multithreading (SMT) ordisabling cores, or both, reduces the virtual CPU counton which licenses will be charged.

Who is responsible for the compliance and reporting of on-demand Windows Server licensing?

If you use on-demand licenses from Google, Google ensures compliance with thelicensing requirements and manages the reporting of license usage.

Do I need to purchase user client access licenses (CALs) when I use an on-demand license for Windows Server?

No, the CALs and their cost are included with the OS image. You don't need toseparately purchase user CALs. Active Directory domain controller instancesrunning in a Managed Microsoft Active Directory domain, or any Windows instancesthat are domain-joined to such a domain also don't require any additional CALs.For more information, seeManaged Service for Microsoft Active Directory.

Are Remote Desktop Services (RDS) CALs required for on-demand instances?

No, RDS CALs are not required for on-demand Windows Servers unless you need morethan two concurrent remote desktop sessions for administrative purposes. If youneed more than two concurrent remote desktop sessions, you must purchaseadditional RDS CALs. For more information, seelicense your RDS deployment with CALs.

BYOL Windows Server FAQ

How do I know if my license for Windows Server is eligible for use on Google Cloud (BYOL)?

Your Windows Server license might beeligible for use on Google Cloud usingOutsourcing Software Management Rights if it meets the followingconditions, provided that you are not otherwise prevented from outsourcing themanagement of your software:

• Products released in 2019 or earlier: The license covers a Microsoftproduct version released before October 1, 2019, which was the date thatMicrosoft announced a change to their license. For example, Windows 2019 mightbe eligible for BYOL with Outsourcing Management Rights, but Windows Server2022 is not eligible.
• Acquired or effective before October 1, 2019: You acquired the Microsoftlicense under an enrollment effective before October 1, 2019, OR you acquiredthe Microsoft license after October 1, 2019 under aMicrosoft's Enterprise Agreement True-up (PDF download), for an enrollmentwith an effective date before October 1, 2019. This includes both the serverlicenses and any CALs.
• Sole-tenant nodes (dedicated hardware) are required: You can only usesoftware brought using Outsourcing Software Management Rights with dedicatedservers such assole-tenant nodes.Microsoft doesn't allow the use of Outsourcing Software Management Rights in amulti-tenant environment, and therefore you cannot use the software with thedefault tenancy for Compute Engine instances.

Is Windows Server covered by Software Assurance with License Mobility?

No, Windows server is not covered under License Mobility because LicenseMobility only applies to server applications, not the underlying operatingsystem. For more information, seeMicrosoft License Mobility.

What if I am eligible to run an earlier version of Windows Server on sole-tenant nodes, but later upgrade to version of Windows Server that was released after October 1, 2019?

When you upgrade to a version of Windows Server that was released after October1, 2019, you are subject to Microsoft's licensing terms for that version. Underthese conditions, your new license might not be eligible for BYOL to Google Cloud.

Are an instance' licenses altered when updating the tenancy of an instance?

When youmodify the tenancy of aninstance, Compute Engine does not alter its license. For any license that youbring to Google Cloud (BYOL), you are responsible for ensuring that the instanceis using a tenancy model (sole-tenant or multi-tenant) that is compliant withyour licensing agreement.

If I bring my own BYOL Windows Server license, do I need CALs?

Yes. If you bring your own Windows Server license, you are responsible forpurchasing any required CALs. Depending on how you configure and use WindowsServer, you might need additional CALs for Rights Management Services when theyare used over RDP. For more information, seeLicense your RDS deployment with CALs.

If I bring my own BYOL Windows Server license to Compute Engine, how do I activate it?

If you import an image to Compute Engine that requires an existing license,you are responsible for activating the license. For more information, seeBringing your own licenses. Ifyou use anon-demand image, Google managesthe license for you.

What am I responsible for if I bring my own license (BYOL)?

If you bring your own licenses to Compute Engine, you are responsible forensuring compliance with Microsoft under your licensing terms.

If I bring my own Windows Server license, can I apply my license by the core?

If your Windows Server license is eligible for BYOL, then you might be able touse the license by the core as long as you meet the following criteria:

• Per core licensing of Windows Server is only available on sole-tenant nodes.
• For both Standard and Data center editions, the number of core licensesrequired equals the number of physical cores on the licensed server, subjectto a minimum of 8 core licenses per physical processor, and a minimum of 16core licenses per server. Core licenses are sold in 2-packs. For moreinformation, seeMicrosoft licensing brief.

A Windows Server Standard license grants you the right to host two instances onthe physical host, while the Datacenter license with per-core licensing grantsyou the right to host an unlimited number of instances on the physical host.

SQL Server on Google Cloud FAQ

What are my options for running SQL Server on Google Cloud?

There are several ways to run SQL Server workloads on Google Cloud:

• On-demand SQL Server images from Google:Prebuilt SQL Server images are available directly from Compute Engine inthe Google Cloud console. These images are built on top of Windows Server and thelicensing costs for both Windows Server and SQL Server are added as licenseSKUs alongside the base instance resource SKUs. For more information onthe on-demand pricing model and getting started, seeOn-demand Windows Server FAQ.
• Bring Your Own License (BYOL) SQL Server:If you have an existing SQL Server license for on-premise use, you might beable to bring this license to Google Cloud in the following scenarios:
  • If you have Software Assurance with License Mobility, your SQL Serverlicense might be eligible to run on default multi-tenant instances as longas the underlying operating system does not require the use of sole-tenantnodes.
  • If you don't have Software Assurance with License Mobility, then you canonly bring your SQL Server license to Google Cloud on sole-tenant nodes, andonly if your license meets the criteria forOutsourcing Software Management Rights.
• Google-managed SQL Server:Other options for running SQL Server includeCloud SQL,our Google-managed SQL Server offering, andGoogle Cloud VMware Engine.

On-demand SQL Server FAQ

How many SQL Server core licenses are charged for my instance?

Microsoft SQL Server licensing requires a core license to be assigned to eachvirtual CPU (vCPU) available to the guest operating system, with a minimum offour core licenses always being charged. Reducing the number of virtual CPUsavailable to the guest operating system bydisabling SMTordisabling cores, or both,reduces the number of core licenses that will be charged.

For example, a c4-standard-8 instance with default settings presents eight vCPUsto the guest operating system, and you are charged for eight core licenses.

If you set visible cores to three (with one core disabled), six vCPUs arepresented to the guest operating system, and therefore, you are charged for sixcore licenses. If you next set threads per core to one (with SMT disabled), onlythree vCPUs are presented to the guest operating system. However, you arecharged for four core licenses, as you will always be charged for a minimum offour core licenses.

In addition to the license charges, you are billed for the c4-standard-8Compute Engine instance resources.

How are SQL Server failover clusters licensed?

When you use on-demand licenses for SQL Server, you must license all instancesin the failover cluster, including passive instances.

Can I remove a SQL Server license from an existing instance?

Once you create or import a instance, you can't edit or delete the instance'smetadata. Therefore, you can't remove SQL Server licenses that are attached tothe instance.

BYOL SQL Server FAQ

Is SQL Server covered by Software Assurance with License Mobility?

Yes, SQL Server is usually covered by License Mobility through SoftwareAssurance. This means that if you have an active Software Assurance contract foryour SQL Server licenses, you can move them to Google Cloud.

If I don't have Software Assurance with License Mobility, can I still bring my own SQL Server license (BYOL) to Google Cloud?

Without Software Assurance with License Mobility, you might be able to use yourown SQL Server license (BYOL) if it meets the following requirements:

• Products released in 2019 or earlier: The license covers a Microsoftproduct version released before October 1, 2019. For example, Windows 2019might be eligible for BYOL with Outsourcing Management Rights, but WindowsServer 2022 is not eligible.
• Acquired or effective before October 1, 2019: You acquired the Microsoftlicense under an enrollment effective before October 1, 2019, OR you acquiredthe Microsoft license after October 1, 2019 under aMicrosoft's Enterprise Agreement True-up (PDF download), for an enrollmentwith an effective date before October 1, 2019. This includes both the serverlicenses and any CALs.
• Sole-tenant nodes (dedicated hardware) are required: You can only usesoftware brought using Outsourcing Software Management Rights with dedicatedservers such assole-tenant nodes.Microsoft doesn't allow the use of Outsourcing Software Management Rights in amulti-tenant environment, and therefore you cannot use the software with thedefault tenancy for Compute Engine instances.

If I use License Mobility to bring my SQL Server workload to Google Cloud, does the instance need to run on dedicated hardware like sole-tenant nodes?

Workloads covered by License Mobility don't necessarily need to be placed onsole-tenant nodes, provided that:

• The instance is solely dedicated to your use
• The underlying operating system does not require a sole-tenant node

For example, a instance running BYOL SQL Server brought with License Mobility runningon an on-demand Windows Server image from Google doesn't require sole-tenantnodes.

However, a instance running BYOL SQL Server brought with License Mobility running on aBYOL Windows Server image requires sole-tenancy. This is because the WindowsServer operating system is not eligible for License Mobility and is subject tothe restrictions ofOutsourcing Software Management Rights.

The following table lists tenancy options depending on how you bring your SQLServer to Google Cloud.

For more information, seeMicrosoft License Mobility.

Can I use my own SQL Server license (BYOL) in an instance with a Google provided operating system?

If your SQL Server license meets the criteria for running on Google Cloud, youcan install SQL Server yourself on a Windows Server or Linux image provided byGoogle. Costs for apremium image such as Windows Serverare charged appropriately.

How do I activate License Mobility for the Microsoft Workloads I bring to Google Cloud?

To use License Mobility, you must complete the license verification process,during which Microsoft ensures that your licenses are eligible for LicenseMobility. You can submit your License Mobility information for verificationthrough Google or directly to Microsoft. Microsoft provides confirmation to youand to Google after verification is complete.

For specific information about your License Agreement, including how todetermine your Microsoft Agreement Identifying Number, seeMicrosoft's License Summary FAQ.

• Submit License Mobility information through Google:

  Use theLicense Mobility verification form to submit your License Mobility information through Google. You can accessthis form directly or when you are creating a instance in the Google Cloud console.

• Submit License Mobility information directly to Microsoft as follows:

  • VisitMicrosoft's Volume Licensing Service Center.
  • Read theLicense Mobility through Software Assurance Verification Guide for Customers (PDF download).

  • Specify Google as the Authorized Mobility Partner by using the followinginformation:

    • Authorized Mobility Partner Name: Google LLC
    • Authorized Mobility Partner Website URL: https://cloud.google.com
    • Authorized Mobility Partner Email Address: google-ms-license-mobility@google.com

If I license my SQL Server license by the core, am I required to license a minimum number of cores?

Yes, a minimum of four core licenses are required for each physical processor onthe server. When running SQL Server in a physical operating system environment,all physical cores on the server must be licensed. Software partitioning doesn'treduce the number of core licenses required, except when licensing individualinstances. For more information, seeMicrosoft licensing brief.

Are passive failover rights provided when I use License Mobility through Software Assurance?

Rights for one failover instance (HA or DR) are provided by BYOL licenses thatuse License Mobility through Software Assurance. The failover instance musthave the same or fewer virtual CPUs as the primary, and both instances must runon Google Cloud. If you want to use an Always On Availability Group secondaryreplica, it must be set to not-read.

If I use my own BYOL SQL Server license on sole-tenant nodes, are CALs required?

CALs are required if you bring your own server licenses. CALs are not requiredfor bringing your own Core licenses.

If I use my own BYOL SQL Server license, can I upgrade to a later version of SQL Server?

If you use your Outsourcing Software Management Rights to bring your own SQLServer licenses to sole-tenant nodes, you cannot upgrade to a version releasedafter October 1, 2019.

If you use License Mobility through Software Assurance to assign a SQL Serverlicense to an instance on Google Cloud, there are no upgrade restrictions.

What licensing models are supported for SQL Server deployments running on sole-tenant nodes?

If you use your Outsourcing Software Management Rights to assign licenses tosole-tenant nodes, they can be licensed as follows:

• Per-core
• Per-processor
• Per-server or per-CAL

Can I uninstall or reinstall SQL Server on a SQL Server instance with my existing license?

Yes, you can uninstall or reinstall SQL Server on a SQL Server instance withyour existing license. The installation media for SQL Server is located atC:\sql_server_install.

Note that uninstalling SQL Server won't stop the SQL Server licensing charges.

Can I use my SQL Enterprise licenses for unlimited virtualization with License Mobility?

No. While SQL Enterprise per-core licenses can be used to license an unlimitednumber of SQL Servers instances on a licensed server, that right does not extendto SQL Server instances covered by license mobility. Each instance must becovered individually.

Windows Desktop OS FAQ

Windows Desktop OS is also known as Windows Client or Windows Enterprise. Somecommon versions include Windows 7, Windows 8, Windows 10, and Windows 11.

What are my options for running Windows Desktop operating systems on Google Cloud?

Your existing Windows Desktop OS license might be eligible for use on Google Cloudas long as you have an active Windows Enterprise VDA E3 or E5 subscription fromMicrosoft, and the instances run on sole-tenant nodes.

Can I purchase on-demand Windows Desktop OS licenses directly from Google Cloud?

No, Google Cloud does not provide Windows Desktop OS licenses.

Am I required to run my Windows Desktop OS instance on a sole-tenant node?

Yes, your instances with Windows Desktop OS can only run on dedicated hardwaresuch as sole-tenant nodes.

Is Windows Desktop OS subject to the same Outsourcing Software Management restrictions as BYOL Windows Server?

No, the requirements for BYOL Windows Desktop OS are different from BYOL WindowsServer. You are allowed to use your own Windows Desktop OS license onGoogle Cloud as long as you have an active Windows Enterprise VDA E3 or E5subscriptions, and place the instance on a sole-tenant node.

Microsoft Office FAQ

Can I bring my own Microsoft Office licenses to instances on Google Cloud?

Perpetual versions of Microsoft Office (Microsoft Office 2019 and earlier) areeligible for BYOL to Google Cloud, however these licenses are subject to theOutsourcing Software Management Rights requirements:

• Products released in 2019 or earlier: The license covers a Microsoftproduct version released before October 1, 2019. For example, Windows 2019might be eligible for BYOL with Outsourcing Management Rights, but WindowsServer 2022 is not eligible.
• Acquired or effective before October 1, 2019: You acquired the Microsoftlicense under an enrollment effective before October 1, 2019, OR you acquiredthe Microsoft license after October 1, 2019 under aMicrosoft's Enterprise Agreement True-up (PDF download), for an enrollmentwith an effective date before October 1, 2019. This includes both the serverlicenses and any CALs.
• Sole-tenant nodes (dedicated hardware) are required: You can only usesoftware brought using Outsourcing Software Management Rights with dedicatedservers such assole-tenant nodes.Microsoft doesn't allow the use of Outsourcing Software Management Rights in amulti-tenant environment, and therefore you cannot use the software with thedefault tenancy for Compute Engine instances.

End of support FAQ

My instance is running an end of support version of Windows Server. Can I configure this instance to receive Extended Security Updates (ESUs) provided by Microsoft?

Yes. You will need to purchase the ESUs from Microsoft, but once purchased youcan configure your Windows instances to receive ESUs to protect them againstcritical security vulnerabilities.

Image Import FAQ

Can I customize the image import workflows?

Yes. You can customize the image import workflow. The image import workflows areavailable on GitHub.

Can I import images that are already running?

Yes. You can import images from instances that are online and running.

After I import my BYOL image, can I share it?

Yes. After importing your BYOL image, you can share it with users outside yourproject or organization. Then, they can access the shared images from theirproject. For more information, seeManaging access to custom images.

What's next

• Learn about thelicensing options for Microsoft softwareon Compute Engine.

• Learn more aboutsole-tenant nodes.

• Learn more about theoperating system images thatCompute Engine provides.