Skip to main content
What's new - 2025

Check out recent additions and enhancements in Tackle for 2025.

Leslie avatar
Written by Leslie
Updated over 2 weeks ago

For Tackle-Salesforce integration updates and releases, see What's new - Salesforce integration.

January 2025

  • Azure Native Services listings now supported by Tackle: These SaaS listings are now supported and available for use in Tackle. This latest addition helps independent software vendors (ISVs) in the Azure Native Services program๐Ÿ”— leverage these listing types in their operations and use them at a greater scale.


    โ€‹Benefits include:

    • Listings will look and function as other SaaS-based listings in Tackle. Note: Registration is managed with Microsoft during implementation.

    • ISVs can create or import Microsoft Azure Native Services listings into Tackle, like any other SaaS listing, and will now simply select the Azure Native Services registration option.

    • Ability for ISVs to take advantage of Tackle marketplace features like Offers, Order Notifications, Metering, and reporting.

  • ISVs can see all of their users across their org in User Management: Tackle account administrators can now view all of their users and their access across an organization in all vendor accounts.

  • Administrator and User roles are now global: Tackle standard Admin and User roles are now global and give users with those roles access to all accounts in the org (this only affects multi-vendor organizations).
    โ€‹Learn more about managing Tackle for multi-vendor organizations.

  • SSO Just-In-Time (JIT) provisioning is now optional:

    • JIT provisioning, a feature which automatically creates a new account for any user that logs in for the first time via SSO, can now be optionally disabled.

    • If JIT provisioning is on, a user who signs in to Tackle via SSO will automatically have a new Tackle user created for them if they donโ€™t already have one.. If JIT provisioning is off, users can log in via SSO only if they are invited to Tackle by an admin first.

Did this answer your question?