Loading

SAM on Snow Atlas

Skip Feed
  1. Release notification: Enhanced application and computer reporting

     

    We are pleased to introduce enhancements to the Applications per computer and user and Applications per computer reports in Snow Atlas, providing greater flexibility and more detailed information for reporting and analysis. The enhancements include:

     

    1. More detailed application version information: The application Full version is now available as an optional report column in both reports, helping customers identify installed application versions more precisely for reporting and compliance analysis.
    2. More reliable computer identification: The Computer GUID is now available as an optional report column in both reports, providing a unique identifier to reliably correlate software records with computer and organizational data, even when computer names are not unique.

     

    Summary:

    Release domain: SAM on Snow Atlas

    Release tier: Minor release

    Release date: 13 November 2026

    Expand Post

  2. Upcoming GA release: Modernized Administration pages in SAM Core - November 12th

     

    We’ve modernized the Administration area in SAM Core as part of our ongoing investment in the Snow Atlas experience and platform.

     

    The updated experience covers key administration capabilities, including:

    • Action Log
    • Application allowlist and denylist
    • Compliance exclusions
    • Computer Standards
    • Custom fields
    • License Policies
    • Manufacturers and vendors
    • Notification Definitions
    • Oracle Computer Model Mapping

    These pages now run on our newer platform architecture, aligning them with the modernization approach already introduced for other pages in SAM Core.

     

    SAM Core Administration page 

    Customer impact

    No change to the core administration capabilities is expected. Administrators can continue managing these settings from the familiar SAM Core > Administration area. This update modernizes the underlying platform and provides a stronger foundation for future enhancements.

     

    Release details

    The new pages will be generally available on November 12th in all clusters.

    Expand Post

  3. GA Release notification: Snow Atlas – Data Visibility Restrictions for Application Registrations

    We’re pleased to announce that administrators can now apply Data Visibility restrictions to application registrations in Snow Atlas, now generally available.

     

    Release summary

    Administrators can now set Data Visibility restrictions on application registrations (API clients) from the Snow Atlas UI. They do this by selecting organization nodes, the same way they grant access to users. Third-party tools and scripts that use Snow Atlas APIs can now only access data permitted by the restrictions applied to them. This closes the final use case of the Data Visibility initiative.

     

    What’s included?

    • Assign Data Visibility restrictions to application registrations directly in the Snow Atlas UI
    • Use the same restriction model already used for users
    • Make sure API clients only access data within their permitted organizational scope

     

    Why this matters?

    Customers register unattended applications in Snow Atlas to get client credentials and access Snow Atlas APIs for reporting and visualization. Until now, Data Visibility restrictions could be applied to users but not to application registrations, and they couldn’t be configured in the UI. As a result:

    • API clients couldn’t be limited to the data that users in the same organization were permitted to see
    • Enterprise customers couldn’t fully meet legal, regulatory and confidentiality requirements (e.g. GDPR) for non-user access
    • MSPs couldn’t restrict API access per customer in line with their contractual obligations
    • Customers had raised this repeatedly as an escalation

     

    Release info:

    • Release date: 05th November 2026
    • Product domain: SAM on Snow Atlas
    • Release availability: General Availability (GA)

     

    Learn More:

     

    Expand Post

  4. GA Release notification: Snow Atlas – Data Visibility Restrictions for Application Registrations

    We’re pleased to announce that administrators can now apply Data Visibility restrictions to application registrations in Snow Atlas, now generally available.

     

    Release summary

    Administrators can now set Data Visibility restrictions on application registrations (API clients) from the Snow Atlas UI. They do this by selecting organization nodes, the same way they grant access to users. Third-party tools and scripts that use Snow Atlas APIs can now only access data permitted by the restrictions applied to them. This closes the final use case of the Data Visibility initiative.

     

    What’s included?

    • Assign Data Visibility restrictions to application registrations directly in the Snow Atlas UI
    • Use the same restriction model already used for users
    • Make sure API clients only access data within their permitted organizational scope

     

    Why this matters?

    Customers register unattended applications in Snow Atlas to get client credentials and access Snow Atlas APIs for reporting and visualization. Until now, Data Visibility restrictions could be applied to users but not to application registrations, and they couldn’t be configured in the UI. As a result:

    • API clients couldn’t be limited to the data that users in the same organization were permitted to see
    • Enterprise customers couldn’t fully meet legal, regulatory and confidentiality requirements (e.g. GDPR) for non-user access
    • MSPs couldn’t restrict API access per customer in line with their contractual obligations
    • Customers had raised this repeatedly as an escalation

     

    Release info:

    • Release date: 05th November 2026
    • Product domain: SAM on Snow Atlas
    • Release availability: General Availability (GA)

     

    Learn More:

     

     

     

    Expand Post

  5. Early Access (EA) pre-release notification: Edit of multiple computers (standard and custom fields) in SAM on Snow Atlas

     

    We would like to announce the Early Access availability of Computers Multi-Edit in SAM Core on Snow Atlas.

     

    Release summary: Edit of multiple computers is now live in SAM on Snow Atlas. This enhancement enables you to update standard fields and custom fields on multiple computers in a single operation, directly from the Computers list, eliminating repetitive manual updates and reducing reliance on APIs, imports, or technical support.

     

    Release info:

    • Release date (EA): Planned - 5th November 2026 (afternoon) -
    • Product domain: SAM on Snow Atlas
    • Release availability: Early Access (EA) - enabled per tenant, on request behind a feature flag.

     

    What's included? 

    • Multi-editing capability: Select and update up to 10,000 computers in a single operation from the Computers list.
    • Standard field updates: Update Status, Automatic quarantine management, Organization and Auto editing across all selected computers.
    • Custom field updates: Update, clear or remove custom field values across all selected computers, including text, number, decimal, date, currency, Yes/No and list fields.
    • Review before saving: A Confirm changes summary shows exactly which fields will be updated, and for how many computers, before anything is saved.
    • Background processing: Large updates run in the background, with a progress banner on the Computers list and a clear success or failure message when the update completes.
    • Safe updates: Each computer is updated as a whole. If an update cannot be completed for a computer, none of its changes are applied, so no record is left half-updated.
    • In-app experience: Perform all updates directly from the Computers list without APIs, imports, or external tools.
    • Permission consistency: Use existing edit permissions with no additional configuration required.
    • Audit log support: Multi-edit updates are recorded in the audit log, providing visibility into changes made across computers.

     

    For each computer value or setting: Only changed values are updated. Every field stays grey until it is modified; once modified it turns dark and is marked Modified. Anything still grey will not be written. If the selected computers share the same value, it appears in the edit view. If the selected computers have different values before the change, you will see "Values differ" in the edit view. If every selected computer is blank, you will see "No value". To undo a change to a custom field before saving, remove the field and add it back; it returns to its original value.

     

    Why this matters? 

    • Restores a capability customers lost: multi-edit of computers existed in SLM and has not existed in Atlas since the legacy Search for Computers page was hidden. 
    • Simplifies organizational changes: Move hundreds of computers to a new organization node after mergers, acquisitions, restructures, or team changes. 
    • Keeps the estate accurate: Set the status of many computers at once, for example marking retired or unused devices as Inactive, and manage quarantine and auto editing settings consistently. 
    • Maintains custom metadata at scale: Update fields such as warranty dates, departments or cost information across many computers without editing each record. 
    • Accelerates data cleanup initiatives: Correct outdated or inconsistent computer information across large numbers of computers in one operation. 
    • Reduces technical dependency: Enables users to perform large-scale updates directly in the product without relying on APIs, imports, or technical teams. 
    • Saves significant time: Activities that previously required numerous manual updates can now be completed in a single operation, freeing teams to focus on compliance and optimization.

     

    Scope: Multi-edit applies one value across a selection. If you need to perform different values per record, operations above 10,000 records, and scheduled or automated updates, continue to use imports and write API's work.

     

    Known improvements required: 

    • We are working on improving the performance on shared tenants to allow parallel editing. Larger values of 10000 computers and include custom fields may experience timeouts during EA. For testing purposes, please aim to reduce selected computers quantity in a single edit until GA.
    • Improve the refresh of edited data to fully sync. Users on EA may be required to manually use the "update data" button on the bottom of the Computers list page.

     

    Activities before GA:

    • Plan: Release to only selected EA customers who notify their Flexera representatives of wishing to try this feature. 
    • Monitoring: Tracking of edits are in place to understand and monitor usage, as well as frontend monitoring of user behaviour to ensure we can provide the best experience possible.
    • Feedback required for validation: We want your EA feedback before going GA. What works well, what is still missing, further improvements, or perhaps a need for utilising features in other parts of the product?
    • Concurrent multi-tenant performance: Operations close to the 10,000 cap running concurrently across tenants have been observed to have degraded performance, hence the limited selection of EA tenants.

     

    What's next? 

    • Edit of multiple applications (including custom fields). 
    • Edit of multiple licenses (including custom fields). 
    • Edit of multiple users (including custom fields). 
    • Edit of multiple agreements: extension to include custom fields.

     

    How customers get access: Early Access is enabled per tenant on request. We do not switch it on for anyone who has not asked. If you would like to have this added to your tenant, please reach out to your CSM representative, Account Manager, or Support.

     

     

    Expand Post

    KellyBywater likes this.

  6. EA Release notification: Edit of multiple licenses (standard fields) in SAM on Snow Atlas

     

    Release summary:

    We are excited to introduce Edit of multiple licenses (standard fields) in SAM on Snow Atlas. This enhancement enables you to update multiple licenses in a single operation, directly from the Licenses list, eliminating repetitive manual updates and reducing reliance on APIs, imports, or technical support.

     

    What’s included?

    • Multi-editing capability: Select and update up to 10,000 licenses across different license metrics and assignment types, updating only the fields that are applicable to the selected licenses.
    • Standard field updates: Modify key license attributes across multiple records simultaneously.
    • In-app experience: Perform all updates directly from the Licenses list without APIs, imports, or external tools.
    • Permission consistency: Use existing edit permissions with no additional configuration required.
    • Audit log support: Multi-edit updates are recorded in the audit log, providing visibility into changes made across licenses.
    • For each license value or setting:
      • Only changed values are updated.
      • If the selected licenses share the same value, it appears in the edit view.
      • If the selected licenses have different values before the change, you will see "Values differ" in the edit view.

     

    Why this matters?

    • Simplifies organizational changes: Update ownership, cost center, department, or other standard fields across hundreds of licenses after mergers, acquisitions, restructures, or team changes.
    • Supports mixed license estates: Apply updates across licenses with different license metrics and assignment types in a single operation, reducing the effort required to maintain diverse software portfolios.
    • Accelerates data cleanup initiatives: Correct outdated or inconsistent license information across large numbers of licenses without editing each record individually.
    • Improves data consistency: Ensure common attributes remain aligned across the license estate, reducing errors and improving reporting accuracy.
    • Reduces technical dependency: Enables users to perform large-scale updates directly in the product without relying on APIs, imports, or technical teams.
    • Saves significant time: Activities that previously required numerous manual updates can now be completed in a single operation, freeing teams to focus on compliance, optimization, and vendor management.

     

    What’s next?

    • Support for editing of custom fields for licenses is planned for Q4 and is currently in development.

     

    Release info:

    • Release date: 08th October 2026
    • Product domain: SAM on Snow Atlas
    • Release availability: Early Access (EA)

     

    Expand Post

  7. Correction Release: SharePoint scheduled report exports no longer fail due to duplicate file names

     

    What was happening?

    A scheduled report export to SharePoint could fail with a "Name already exists" error when a file with the same name already existed in the target location or when multiple users generated the same report simultaneously. In these situations, SharePoint rejected the upload and the report was not delivered.

     

    What has been changed?

    Every export now receives a unique file name. Export file names have been updated to include additional identifiers, helping prevent conflicts when files with the same name are generated or uploaded concurrently:

    • Milliseconds in the timestamp
    • A 6-character unique ID (GUID) suffix (Example : AdobeCC_20260930123000001_2e0d0c)

     

    What this means for you?

    • Scheduled exports should no longer fail due to duplicate file names.
    • Reports scheduled for SharePoint delivery should arrive more reliably.
    • Exported file names will look slightly different because they now include a more precise timestamp and a unique ID suffix.

     

    Is any action required?

    Existing schedules will continue to run without interruption, and the update is applied automatically. If downstream integrations, such as Power BI, depend on the exported files, review and update any file name references as needed to ensure those integrations continue to operate correctly.

     

    Release Info:

    Product: SAM on Snow Atlas(Report export to SharePoint)

    Type: Correction

    Release date: 21 September 2026

    Expand Post

  8. Release notification: Edit of multiple agreements (standard fields) in SAM on Snow Atlas

     

    Release summary:

    We are excited to introduce Edit of multiple agreements (standard fields) in SAM on Snow Atlas. This enhancement enables you to update multiple agreements in a single operation, directly from the Agreements list, eliminating repetitive manual updates and reducing reliance on APIs or technical support.

     

    What’s included?

    • Multi-editing capability: Select and update up to 1,000 agreements of the same type in one action.
    • Standard field updates: Modify key agreement attributes across multiple records simultaneously.
    • In-app experience: Perform all updates directly from the Agreements list without APIs, imports or external tools.
    • Permission consistency: Uses existing edit permissions with no additional configuration required.
    • Audit log support: Multi-edit updates are recorded in the audit log, providing visibility into changes made across agreements.
    • For each agreement value or setting:
      • Only changed values are updated.
      • If the selected agreements share the same value, it appears in the edit view.
      • If the selected agreements have different values before the change, you will see "Values differ" in the edit view.

     

    Why this matters?

    • Removes repetitive work: Eliminates the need to update agreements one by one.
    • Saves significant time: Multi-editing that previously took time can now be completed in seconds.
    • Improves data consistency: Apply changes across multiple agreements simultaneously, reducing the risk of errors.
    • Reduces technical dependency: Enables users to perform multi-editing without relying on APIs, imports, or technical teams.
    • Frees up time for strategic work: Allows teams to focus on higher-value activities such as compliance, optimization, and vendor management.

     

    What’s next?

    • Support for editing custom fields for agreements is currently in development and testing, with an EA release planned for early Q4.
    • The improved performance and new backend architecture will also allow users to edit up to 10,000 agreements of the same type in a single action.

     

    Release Info:

    ·      Release date: September 24, 2026

    ·      Product domain: SAM on Snow Atlas

    ·      Release availability: General Availability (GA)

    ·      Documentation: https://docs.flexera.com/snow-atlas/sam-core/sam-core-user-interface/agreements/manage-agreements

     

    Expand Post

End of Feed
End of Feed
8 Chatter Feed Items
ALL CONVERSATIONS
UNSOLVED
ARTICLES
4 Followers
149 Posts
214 Articles
6 members are discussing this topic.
Loading
SAM on Snow Atlas | Flexera