Prepare Now for Chocolatey Deprecation

JumpCloud is deprecating the public Chocolatey Community Repository as a Windows Software Management application source. Starting January 1, 2027, you cannot create new public Chocolatey configurations or use existing ones to deploy or manage applications on additional devices.

This change does not uninstall applications previously deployed through Chocolatey. Existing public Chocolatey configurations remain visible in the JumpCloud Admin Portal in a read-only state so you can reference prior configuration and assignments while you migrate.

Begin moving applications to JumpCloud App Catalog, Microsoft Store where supported through JumpCloud, or JumpCloud Private Repo, depending on the application.

Considerations

• Applies only to the public Chocolatey Community Repository path in JumpCloud.
• Chocolatey is not being discontinued, and the Chocolatey Community Repository is not being shut down.
• JumpCloud does not automatically convert existing Chocolatey configurations to App Catalog, Microsoft Store, or Private Repo.
• JumpCloud may retire and clean up these legacy configuration records in a later phase. You will receive advance communication before cleanup.

Key Points (January 1, 2027)

• Public Chocolatey as a Windows application source is deprecated.
• You cannot create new public Chocolatey configurations. The public Chocolatey option is no longer available when creating new Windows Software Management configurations.
• Existing public Chocolatey configurations remain visible in the Admin Portal in a read-only state.
• You cannot edit existing configurations or use them to bind additional devices.
• You cannot newly target devices, directly or through device group membership, using an existing public Chocolatey configuration.
• JumpCloud no longer performs new installs, reinstalls, remediation, or Chocolatey-based updates through these configurations.
• Applications already installed on endpoints are not uninstalled. They remain available for end users.
• You can still refer to the existing configuration and its historical or current assignment information while you transition to another supported source.

Why JumpCloud Is Making This Change

Chocolatey has announced changes effective January 1, 2027 that affect direct organizational and vendor use of the Chocolatey Community Repository.

JumpCloud's public Chocolatey integration relies on that repository for Windows application packages, so JumpCloud is retiring this application source. The change also aligns with JumpCloud's Software Management strategy for supported, predictable delivery through:

• JumpCloud App Catalog
• Microsoft Store
• JumpCloud Private Repo

This change affects only JumpCloud's use of the public Community Repository as a Windows application source.

Who Is Affected

You are affected if your organization has Windows Software Management applications configured with Chocolatey as the public application source.

This deprecation does not affect applications you already manage through JumpCloud App Catalog, Microsoft Store, JumpCloud Private Repo, or other supported JumpCloud software sources.

Existing Chocolatey Configurations

JumpCloud does not immediately delete existing public Chocolatey configurations. They remain in the Admin Portal in a read-only state as a migration and reference record.

You can still view:

• The Chocolatey application or package that was configured
• Configuration details
• Previously associated devices and device groups
• Existing deployment or status information available in JumpCloud

Use that information to understand your Chocolatey deployment and choose a replacement source. While you cannot edit configurations or add new device or group assignments, you can still remove existing bindings and delete the legacy configuration once you have completed your migration.

You cannot use these configurations to:

• Change the Chocolatey package configuration
• Create new public Chocolatey configurations
• Add new individual device or device group assignments
• Deploy the application to additional devices
• Trigger new installs or reinstalls through the public Chocolatey repository
• Continue Chocolatey-managed application updates

If a device later joins a device group that was previously assigned a Chocolatey application, the retired configuration does not install the application on that device.

Applications Already Installed on Devices

JumpCloud does not uninstall applications previously installed through a public Chocolatey configuration. If an application is already on an endpoint, it stays installed and usable.

The deprecation affects JumpCloud's ongoing management through the public Chocolatey source, not removal of the application.

After the deprecation, JumpCloud does not:

• Perform a new Chocolatey installation
• Deploy the application to a newly targeted device
• Reinstall the application through Chocolatey if it is later removed from the endpoint
• Perform Chocolatey-based application updates through the retired configuration

Some applications have vendor-provided update mechanisms and may continue to update independently of JumpCloud, depending on the application's behavior and configuration.

Why Configurations and Applications Are Not Removed Immediately

JumpCloud intends this transition to be non-disruptive. Immediately deleting configurations would remove information you may need for migration planning. Automatically uninstalling applications could disrupt end users.

Keeping configurations visible and read-only lets you:

• Understand what you previously deployed through Chocolatey
• Review affected devices and groups
• Determine an appropriate replacement deployment method
• Transition applications on your own migration schedule

Migrating Your Chocolatey Applications

There is not one migration path for every application. Evaluate these supported options.

JumpCloud App Catalog

Where an equivalent application is available, JumpCloud App Catalog is the preferred path. The App Catalog provides curated applications that JumpCloud supports for software deployment and management.

1. Search for the application in the JumpCloud App Catalog.
2. Create the replacement application configuration.
3. Configure the required delivery and update behavior.
4. Assign the appropriate devices or device groups.
5. Validate the new deployment before you finish transitioning away from the Chocolatey configuration.

Microsoft Store

Some Windows applications can be deployed using the Microsoft Store source in JumpCloud. If an application is not in the JumpCloud App Catalog, check whether an equivalent is available through JumpCloud's supported Microsoft Store deployment experience.

note

Not every application listed in the Microsoft Store is currently deployable through JumpCloud. Public Microsoft Store availability does not mean the application is supported through JumpCloud's Microsoft Store integration.

JumpCloud Private Repo

For applications not available through the App Catalog or supported Microsoft Store deployment, consider JumpCloud Private Repo. Private Repo can fit:

• Custom or internally packaged applications
• Vendor installers that are not available in the App Catalog
• Applications for which your organization wants to manage the installer or package directly

Choosing a Migration Path

1. If the application is in the JumpCloud App Catalog, migrate to App Catalog.
2. If not, check whether it is deployable through JumpCloud using Microsoft Store.
3. If a supported Microsoft Store version is available, migrate to the Microsoft Store source.
4. If not, evaluate JumpCloud Private Repo or another supported deployment method.
5. If none of these options meets your business requirements, contact your JumpCloud Customer Success Manager or JumpCloud Support.

JumpCloud does not automatically convert existing Chocolatey configurations to App Catalog, Microsoft Store, or Private Repo configurations. Plan to create the replacement configuration and assign the required devices or device groups. That is intentional: the replacement may use a different package, source, configuration model, or deployment behavior than the Chocolatey package.

If an Application Is Not in the JumpCloud App Catalog

Not every Chocolatey package will be added to the JumpCloud App Catalog. The App Catalog is curated and does not provide a one-to-one equivalent for every Chocolatey package. JumpCloud is reviewing current Chocolatey usage and application demand to help prioritize important catalog gaps.

If your application is not available:

1. Check whether it can be deployed through JumpCloud's Microsoft Store integration.
2. Evaluate JumpCloud Private Repo.
3. If neither option meets your requirements, contact your Customer Success Manager or JumpCloud Support.

For business-critical applications, provide the application name and why the available migration methods do not meet your requirements. That helps JumpCloud evaluate customer impact and prioritization.

What to Do Now

If you use the public Chocolatey source, begin planning your transition before January 1, 2027.

1. Review the Chocolatey applications currently configured in your JumpCloud organization.
2. Determine which applications are still required.
3. Search for an equivalent in the JumpCloud App Catalog.
4. For applications not available there, evaluate Microsoft Store where supported.
5. Evaluate JumpCloud Private Repo for applications without an appropriate catalog-based path.
6. Create and test the replacement application configuration.
7. Transition your device and device group assignments to the replacement configuration.
8. Complete migration away from the public Chocolatey source.

Begin this work before the deprecation date rather than waiting until January 1, 2027.

Frequently Asked Questions

Is Chocolatey being discontinued?

No. Chocolatey and the Chocolatey Community Repository are not being discontinued. JumpCloud is deprecating its use of the public Chocolatey Community Repository as a Windows Software Management source.

When will JumpCloud stop supporting the public Chocolatey source?

The public Chocolatey source is deprecated effective January 1, 2027. Complete your migration planning before this date.

Will my existing Chocolatey applications be uninstalled?

No. JumpCloud does not uninstall applications from endpoints as part of this deprecation. Already-installed applications remain on devices.

Will the application stop working on January 1, 2027?

No. The deprecation does not intentionally disable or remove the installed application. What changes is JumpCloud's ability to continue actively managing the application through the retired public Chocolatey configuration.

Will Chocolatey automatic updates continue?

JumpCloud no longer performs updates through the retired public Chocolatey configuration. An application may have its own independent self-update functionality. If so, that behavior is controlled by the application or vendor, not by the retired JumpCloud Chocolatey configuration.

What happens if an end user uninstalls the application after January 1, 2027?

JumpCloud does not reinstall or remediate the application using the retired public Chocolatey configuration. Migrate required applications to another supported JumpCloud deployment source if you want JumpCloud to continue managing the application's presence.

What happens if I add a new device to a device group that was previously assigned a Chocolatey application?

The retired public Chocolatey configuration does not cause a new installation on that device. Existing assignments remain visible for reference, but they no longer result in new deployments.

Can I create a new Chocolatey configuration after January 1, 2027?

No. New configurations using the public Chocolatey Community Repository are no longer supported.

Will my old Chocolatey configurations disappear?

No, not immediately. Existing configurations remain visible in a read-only state so you can review previous deployment and assignment information while you migrate. JumpCloud may remove legacy configuration records in a later cleanup phase. Advance notice will be provided before that occurs.

Can JumpCloud automatically convert my Chocolatey configuration to an App Catalog configuration?

No automatic migration is currently planned. Because application sources and configuration models can differ, create and validate the replacement configuration before transitioning assignments.

Is every Chocolatey application available in the JumpCloud App Catalog?

No. JumpCloud's App Catalog is curated and does not provide a one-to-one equivalent for every Chocolatey package. Where an equivalent is unavailable, evaluate Microsoft Store or JumpCloud Private Repo.

Are customer-managed or private Chocolatey repositories affected?

No. This deprecation strictly impacts JumpCloud's integration with the public Chocolatey Community Repository. Custom internal feeds or private Chocolatey repositories maintained independently by your organization are not affected.

Is every application in Microsoft Store deployable through JumpCloud?

No. Some applications in Microsoft's public Store are not currently supported by JumpCloud's Microsoft Store deployment integration. Confirm availability through the JumpCloud Admin Portal before treating Microsoft Store as the replacement path.

Getting Help

If you need help identifying the migration path for a business-critical application, contact your JumpCloud Customer Success Manager or JumpCloud Support. Provide the application name and the business requirement.