Frequently asked questions for Configuration Manager branches and licensing

The current branch is the production-ready build of Configuration Manager that provides an active servicing model. This servicing model is like the experience with Windows. This approach supports customers who are moving at a cloud cadence and wish to innovate more quickly. With the current branch servicing model, you continue to receive new features and functionality. For this reason, only customers with active Software Assurance on Configuration Manager licenses, or with equivalent subscription rights, may install and use the current branch of Configuration Manager.

The LTSB is a production-ready build of Configuration Manager. It's intended for customers who allow Software Assurance or equivalent subscription rights to expire. When compared to the current branch, the LTSB has reduced functionality. Customers who allow Software Assurance or equivalent subscription rights to expire must uninstall the current branch of Configuration Manager. Customers who have perpetual license rights to Configuration Manager may then install and use the LTSB build of the Configuration Manager version that's current at the time of expiration.

Both Software Assurance (SA) and License and Software Assurance (L&SA) are license options that grant rights to use Configuration Manager. SA is an option for a customer that's renewing SA coverage from a prior agreement. L&SA is an option for a customer buying a new license and SA coverage.

• Software Assurance (SA): Customers must have active SA on Configuration Manager licenses, or equivalent subscription rights, in order to install and use the current branch option of Configuration Manager.

  While SA is optional for some Microsoft products, the only way to get rights to use Configuration Manager current branch is with SA or equivalent subscription rights. For more information, see the Software Assurance FAQ.

• Microsoft License and Software Assurance (L&SA): Customers buying new licenses for Configuration Manager must acquire L&SA (the license and SA coverage).

  • The SA grants rights to use the current branch.

  • If your SA expires, and you still have a license for Configuration Manager, you can no longer use the current branch. For more information, see the FAQ If my SA expires and I had L&SA, what do I get?

For more information about license offerings, see Ways to buy and Licensing Product Terms.

Equivalent subscriptions refer to programs like Enterprise Mobility + Security (EMS) or Microsoft 365 Enterprise. There can be others, but these programs are the most common. The Microsoft Volume Licensing Product Terms refers to these programs as Management License Equivalent Licenses.

Configuration Manager is included in the following plans:

• Intune user subscription license (USL)
• EMS E3
• EMS E5
• Microsoft 365 E3
• Microsoft 365 E5
• Microsoft 365 F3 (formerly Microsoft 365 F1)

The co-management license lets Configuration Manager customers with Software Assurance get Intune PC management rights without having to purchase and assign individual Intune licenses to users. This license makes it easier for you to manage Windows devices with Microsoft Intune and Configuration Manager.

• Devices already managed by Configuration Manager that you enroll to Intune for co-management have almost the same rights as an Intune standalone-managed PC. If you reset Windows on this device, you can't provision it with Windows Autopilot. Autopilot requires a full Intune license.

• If you enroll a Windows device to Intune by other means, it still requires a full Intune license. For example, you use Autopilot to provision a device, or a user manually does self-service enrollment.

• For existing Configuration Manager-managed devices to enroll into Intune for co-management at scale without user interaction, co-management uses an Azure Active Directory (Azure AD) feature called Windows auto-enrollment. Auto-enrollment with co-management requires licenses for both Microsoft Entra ID P1 or P2 (AADP1) and Intune. Starting on December 1, 2019, you no longer need to assign individual Intune licenses for this scenario. Microsoft Intune and Configuration Manager each include the licenses for co-management. The separate AADP1 licensing requirement remains the same for this scenario to work. You still need to assign Intune licenses for other enrollment scenarios.

• If you want to use Intune for managing iOS, Android, or macOS devices, then you need the appropriate Intune subscription through a standalone Intune license, Enterprise Mobility + Security (EMS), or Microsoft 365.

• If you don't have any Intune-related subscription plan, to support co-management you need to purchase at least one Intune license. This license is for an administrator to activate the subscription plan and get access to the Microsoft Intune admin center.

• If you use the Microsoft 365 built-in Basic Mobility and Security, you can't use the new co-management license for a user that also has devices managed by Basic Mobility and Security. To use the co-management license for the user's Configuration Manager-managed device, do one of the following actions:

  • Assign a full Intune license to the user, and manage their devices through Intune.
  • Unenroll the devices from Basic Mobility and Security.

• The licensing that you previously had for System Center Configuration Manager still applies to Microsoft Configuration Manager. If installing a new site, use existing product keys.

For more information, see the following articles:

• Co-management prerequisites
• Windows Autopilot requirements
• Tenant attach prerequisites
• Endpoint analytics licensing prerequisites
• Use conditional access with Intune
• TeamViewer prerequisites

EMS grants rights to use Configuration Manager current branch and long-term service branch. When these rights expire, you no longer have rights to use either branch and must uninstall.

If your SA expired after October 1, 2016, depending on what program you acquired L&SA under, you could retain a perpetual license to use the LTSB. If you currently use the current branch, you must uninstall it, and then install the LTSB. There's no support to migrate or convert to the LTSB from the current branch.

If your SA expired before October 1, 2016, and you retained a perpetual license to Configuration Manager, then your only option for ongoing use is to install and use System Center 2012 R2 Configuration Manager and its available service packs. You're required to uninstall the current branch when your SA expires, and reinstall that earlier version of the product. There's no support to migrate to or downgrade from Configuration Manager current branch to prior versions of Configuration Manager.

If you use System Center Endpoint Protection, and your SA expires, you must uninstall it. System Center Endpoint Protection offers no L (License) rights, and no perpetual rights.

No. You're licensed to use the current branch while you have active SA. For example, via L&SA, when SA expires, you then have only L (License) rights, which don't include rights to use the current branch. If your L provides perpetual rights, you can use the Configuration Manager LTSB in place of the current branch. If your SA expired prior to October 1, 2016, you can also use System Center 2012 R2 Configuration Manager.

No. The only way to get rights to use Configuration Manager is to acquire a license with SA or through an equivalent subscription. There are developer programs like MSDN where Configuration Manager is offered for development and test purposes, but not production usage.

• If you use the same current branch software as your production environment, you need an explicit license. Check with your account team to determine if your specific license agreement covers multiple instances in multiple environments.

• Some developer programs like MSDN offer products like Configuration Manager for development and test, but not production use.

• For a temporary environment, you can use the evaluation version for 180 days.

• For a lab environment, you can use the technical preview branch. Technical preview has the same functionality as current branch, but has some limitations in terms of scale and supported platforms.

If you have active SA, you do have rights.

If you don't have active SA, uninstall the current branch, and then install the LTSB of Configuration Manager. The LTSB doesn't receive updates for incremental versions of Configuration Manager, but does receive security updates based on the Support Lifecycle.

Yes, you have rights to use Configuration Manager to manage clients covered by the EMS license. First download and install the evaluation software. Then contact your CSP partner to obtain the license key from the Microsoft Partner Center support team, specifically CSP. When your CSP partner talks with Microsoft Support, they should ask them to reference the internal article ID 4033838.

If SA or your subscription is active, you have use rights for Configuration Manager current branch. An active subscription is equivalent of having active SA, but no perpetual "L" (license). Once your subscription is over, uninstall the current branch. At this time, you don't have rights to use the LTSB.

Configuration Manager includes SQL Server technology. Microsoft's licensing terms for this product allows your use of SQL Server technology only to support Configuration Manager components. SQL Server client access licenses are not required for that use.

Approved use rights for the SQL Server capabilities with Configuration Manager include:

• Site database role
• Windows Server Update Services (WSUS) for software update point role
• SQL Server Reporting Services (SSRS) for reporting point role
• Data warehouse service point role
• Database replicas for management point roles

The SQL Server license that's included with Configuration Manager supports each instance of SQL Server that you install to host a database for Configuration Manager. However, only databases for Configuration Manager in the preceding list can run on that SQL Server when you use this license. If a database for any additional Microsoft or third-party product shares the SQL Server, you must have a separate license for that SQL Server instance.

No. An Intune connection isn't required for new on-premises MDM deployments. Your organization still requires Intune licenses to use this feature. For more information, see the Intune support blog post.