Release Notes

Latest release

Final: 756 — October 29, 2026 · Preview: 757 — October 23, 2026 · See all October releases.

AppDirect release notes are produced each week and describe new customer features, enhancements to existing features, behavior changes, API updates, and updates to the documentation. Features are associated with a release number when they are released to production.

How the weekly release works

AppDirect follows a weekly release cadence:

• Production deployment (Tuesday) — Code for the weekly release is deployed to production.
• Sandbox enablement (Wednesday) — After validation, eligible features may be enabled on sandbox marketplaces so customers can try them before production marketplace enablement. Features in this window are listed under Features in Sandbox.
• Production marketplace enablement (following Wednesday) — After further validation, features are enabled on production marketplaces for eligible customers and graduate into the versioned release notes for that release number.

Release notes for a given release number cover features that are part of that production release. If a feature is delayed, it remains under Features in Sandbox (with an updated expected production date when known) or is included in a subsequent release. The notes are updated accordingly.

Whether a feature is visible on your marketplace also depends on its product lifecycle phase, feature enablement, and (for some Major Upgrades) enterprise rollout timing, described below.

Features in Sandbox

Features in Sandbox replaces the former Preview release notes. Features listed there are present after deployment and are being enabled or validated on sandbox marketplaces. They are not yet announced as part of a numbered production release.

• Treat Features in Sandbox as validation in progress, not as a commitment that a feature will ship in a specific production release on a fixed date.
• When known, the Sandbox index shows an expected production release number and date. Dates can move if validation or other release gates do not succeed.
• When sandbox validation succeeds and production marketplace enablement proceeds for release N, the feature moves into the N release notes and is removed from Features in Sandbox.

📝 Note: This is different from Preview as a product lifecycle phase (selected customers, testing only). Features in Sandbox is a publishing and validation stage before a feature is tied to a production release number.

See Features in Sandbox.

Stay updated

• This page — The "Latest release" box above is updated whenever a new release is published. Bookmark this page and check back, or use the sidebar to browse by year and month.
• Features in Sandbox — Check the Features in Sandbox section for features currently in sandbox validation.
• RSS — Subscribe to the release notes RSS feed in any RSS reader (e.g. Feedly, Inoreader, NetNewsWire). New releases appear in your reader automatically when they're published.

Product lifecycle phase

Release notes may indicate which product lifecycle phase a feature is in. Examples include Preview, Early Availability (EA), and General Availability (GA). Lifecycle phase describes the feature’s maturity and the support, commercial-use, and documentation expectations that apply.

Common phases you will see in release notes:

• Preview — Limited rollout for testing; not for commercial use; limited support.
• Early Availability — Limited rollout for specific use cases; commercial use allowed for those cases; full support and SLA for that scope.
• General Availability — Intended for all eligible customers, with full support and documentation. GA does not always mean the feature is already on for your marketplace. See feature enablement, setting enablement, and Major upgrades and enterprise rollout.

For full phase definitions, including Deprecated, Retired, and Decommissioned, see Product lifecycle phases.

Prerequisites, feature enablement, and setting enablement

All release notes include short sections that describe what must be true before a feature is visible or usable. Read them together. They answer different questions:

Section	Question it answers	Does not mean
Prerequisites	What platform, product, or integration dependencies must already be in place?	A feature flag or marketplace on/off setting
Feature enablement	Who is entitled to use this feature? Must AppDirect enable it for your marketplace?	The feature is turned on or visible to end users
Setting enablement	Once entitled, what is the default state, and how do Marketplace Managers configure it?	AppDirect has granted access to your marketplace

Use this order when reviewing a note:

1. Prerequisites — Do we already have the required platform or product dependencies?
2. Feature enablement — Is the marketplace eligible? Do we need AppDirect to enable a flag?
3. Setting enablement — Once entitled, is the feature already on, or do we need to configure a marketplace setting?

These sections describe the customer-facing production behavior of the feature. Sandbox timing (expected release number or date, validation status) belongs on the Features in Sandbox index. It does not belong inside the enablement sections of the note.

Prerequisites

Prerequisites are platform, product, or integration dependencies that must already be in place. They are not feature flags (feature enablement) and not marketplace on/off settings (setting enablement).

Examples: Checkout V2 enabled, a Microsoft tenant linked, another connector provisioned, or a minimum component version.

When dependencies exist, the release note lists them specifically. When there are none, the note may omit the section or state None. If you need help meeting a prerequisite, contact your AppDirect technical representative or follow links in the note to related documentation.

Feature enablement

Feature enablement describes entitlement. It covers who can use the feature and whether AppDirect must enable it for the marketplace (for example, through a feature flag). It does not describe the product lifecycle phase, the default on/off state in the product, or any marketplace setting.

A note typically covers:

• Who is entitled — marketplace type, role, or lifecycle phase restrictions when relevant (for example, Direct CSP only, or Preview participants only).
• Whether AppDirect action is required — whether a feature flag or similar control must be enabled before the marketplace can use the feature.
• How to request access — when entitlement requires AppDirect, partners should contact their AppDirect technical representative.

Common patterns

• Enabled by default (all entitled marketplaces): This feature is enabled by default for all marketplaces.
• Not enabled by default (request from AppDirect): This feature is not enabled by default. Contact your AppDirect technical representative to request it.
• Preview or EA — selective enablement only: This feature is not enabled by default. During Preview, it is available only to marketplaces participating in the preview program with AppDirect. Contact your AppDirect technical representative for more information.
• No feature enablement required: No feature enablement is required.

For Major Upgrades on enterprise marketplaces, “not enabled by default” often reflects the enterprise testing window described in Major upgrades and enterprise rollout, even when the feature is already GA.

Setting enablement (activation)

Setting enablement describes activation. It covers the default state for an entitled marketplace, and what Marketplace Managers (or other roles) must configure in marketplace settings or other UI. It does not grant marketplace access; that is covered under feature enablement.

A note typically covers:

• Default state — on by default, off by default, or on with no configuration.
• Who configures — typically Marketplace Manager; other in-product roles when the control is not a marketplace setting.
• Where to configure — navigation path and setting name.

Common patterns

• On by default; Marketplace Manager can disable (opt-out): On by default. Marketplace Managers can disable **[Setting name]** at Manage > Marketplace > Settings > [path] (default: On).
• Off by default; Marketplace Manager must enable (opt-in): Off by default. Marketplace Managers must enable **[Setting name]** at Manage > Marketplace > Settings > [path].
• No setting — works once feature enablement is satisfied: No setting enablement is required.

When setting enablement is required, the release note also indicates whether action is needed (for example, no action if you want the default, or configure the setting to change it).

Major upgrades and enterprise rollout

A Major Upgrade is a change with significant impact on the customer or end-user experience, or on core platform functionality. Examples include a major UI redesign or an entirely new capability.

Major Upgrades are rolled out to customers on the same weekly release path as other features, with one important exception for enterprise customers:

• For most marketplaces, a Major Upgrade that is Generally Available (GA) follows the standard enablement described in the release note.
• For enterprise marketplaces, the feature is typically not enabled by default when it first reaches GA.

That delay provides an approximately eight-week window after the feature is announced so that:

• Enterprise customers can validate the change in sandbox and production-ready environments before it is turned on.
• AppDirect technical contacts (TCs) can brief customers on the change, impact, and any required preparation.

During this window, enterprise customers may see the feature described as GA in the release notes but not yet visible in their marketplace. That is expected. Work with your AppDirect technical representative if you want the feature enabled earlier, or for guidance on timing and readiness.

After the enterprise testing and communication window, the feature is enabled according to the standard rollout plan (unless your release note states a different enablement requirement).

Configuration update type

Each release note indicates the type or extent of changes to a feature. The change type appears immediately after the release note heading. This information is included starting with release 700.

The following are the types of configuration updates:

• Emergency Update - An Emergency Update is a critical update to existing features or functionalities that must be addressed immediately. Such updates are required when issues prevent, or are likely to prevent, access to platform services. Examples include security threats or issues that significantly impact platform or marketplace stability.

• Major Upgrade - A Major Upgrade is an update that has a significant impact on the customer or end-user experience, or on core platform functionality. Examples include a complete redesign of the platform's user interface or the addition of an entirely new feature. See Major upgrades and enterprise rollout for how GA Major Upgrades are enabled for enterprise customers.

• Moderate Upgrade - A Moderate Upgrade is an update that has a minor impact on the customer or end-user experience. For example, it may involve moving the location of frequently used buttons or menus in the user interface. These updates are often managed through the supplier's product lifecycle phase process and are typically released behind a feature flag or setting.

• Minor Upgrade - A Minor Upgrade is a small change that does not affect the customer or end-user experience or the core functions of the marketplace or platform. Examples include text or graphic updates.