Release Notification on SAM Core - Snow Atlas: Updated licensing compliance for VMware vSphere

To align with the latest VMware subscription model introduced by Broadcom, Snow Atlas now includes enhanced compliance logic and reporting capabilities:

• Core-based licensing compliance: License compliance is now calculated based on the latest VMware subscription model, which requires a minimum of 16 cores per CPU.
• Updated License compliance summary report: The report now reflects the core-based licensing logic, ensuring accurate tracking and reporting of VMware entitlements.
• VMware bundle categorization: SAM on Snow Atlas now identifies and categorizes VMware bundles in accordance with the latest Broadcom licensing structure.

Why this matters:

Previously SAM core did not account for the minimum requirement of 16 cores per CPU when calculating license requirements for the VMware vSphere family. This could result in incorrect "over assignment" flags for servers that actually met the licensing threshold. With this enhancement, compliance calculations now correctly apply the per-CPU minimum, giving you an accurate license position.

Quality:

This release has been validated through:

• VMware licensing logic: The updated VMware vSphere licensing rules (covering VVF, VVS, VCF, and associated bundles ) have been validated through manual functional testing to ensure that compliance calculations correctly reflect the new per-CPU core-based minimum requirements.
• Compliance reporting: The License compliance summary report has been tested end-to-end to confirm it accurately reflects the updated licensing rules.

Release info:

·       Release date: June 22, 2026

·       Product domain: SAM on Snow Atlas

·       Release availability: GA

·       Product documentation: VMware vSphere 8.0 Enterprise Plus | Snow Atlas Documentation

🌟 What’s New: Report Export Service & SharePoint Integration 

We’ve introduced several improvements to make exporting data from Snow Atlas faster, more reliable, and easier to integrate into your workflows. 

🚀 New Report Export Service 

A modernized export engine now powers all report downloads, delivering: 

• More stable exports for large datasets 
• Asynchronous processing for improved performance 
• Clearer status updates and notifications 

This new service is the foundation for future enhancements in scheduled exports and additional export destinations. 

📤 Export Directly to SharePoint 

You can now send report exports straight to a SharePoint document library. This enables: 

• Automated distribution via Microsoft 365 workflows 
• Centralized storage for reporting outputs 
• Reduced manual steps for teams using SharePoint daily 
• Reports delivered in their original file format in SharePoint 

⚠️ Export Size Limitation 

To ensure consistent performance, exports currently support up to 1,000,000 rows. We’ll continue to evaluate this threshold as usage grows.

🧪 Quality You Can Trust 

This release has been validated through: 

• Automated testing of code and product from the smallest granular functionality to the end‑to‑end use cases 
• Testing performance of reports both in terms of reliability and speed to export up to the 1M‑row limit 
• Security and compliance checks 
• Real‑world scenario testing, including SharePoint connectivity and failure‑mode handling
• Early Access program with a subset of customers, and addressing the feedback

📄 Relevant product documentation update 

• SharePoint sites | Snow Atlas Documentation 
• Reports | Snow Atlas Documentation 

🌟 What’s New: Report Export Service & SharePoint Integration 

We’ve introduced several improvements to make exporting data from Snow Atlas faster, more reliable, and easier to integrate into your workflows. 

🚀 New Report Export Service 

A modernized export engine now powers all report downloads, delivering: 

• More stable exports for large datasets 
• Asynchronous processing for improved performance 
• Clearer status updates and notifications 

This new service is the foundation for future enhancements in scheduled exports and additional export destinations. 

📤 Export Directly to SharePoint 

You can now send report exports straight to a SharePoint document library. This enables: 

• Automated distribution via Microsoft 365 workflows 
• Centralized storage for reporting outputs 
• Reduced manual steps for teams using SharePoint daily 
• Reports delivered in their original file format in SharePoint 

⚠️ Export Size Limitation 

To ensure consistent performance, exports currently support up to 1,000,000 rows. We’ll continue to evaluate this threshold as usage grows.

🧪 Quality You Can Trust 

This release has been validated through: 

• Automated testing of code and product from the smallest granular functionality to the end‑to‑end use cases 
• Testing performance of reports both in terms of reliability and speed to export up to the 1M‑row limit 
• Security and compliance checks 
• Real‑world scenario testing, including SharePoint connectivity and failure‑mode handling
• Early Access program with a subset of customers, and addressing the feedback

📄 Relevant product documentation update 

• SharePoint sites | Snow Atlas Documentation 
• Reports | Snow Atlas Documentation 

Pre-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.

·       Release date: June 18, 2026

·       Product domain: SAM on Snow Atlas

·       Release availability: Early Access (EA)

What is 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.
• Smart field behavior: Fields with identical values are pre-filled, while differing values remain empty for selective updates.
• 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.

Why it 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.

Note

• Support for editing custom fields on agreements is currently in development and will be delivered in a future iteration.
• Our teams are actively working on expanding this capability as part of ongoing improvements to multi-editing.

📢Question Roundup for this week[12th June]: Integration challenges & inventory visibility 

Hello Everyone,

It’s been a busy one in the forums, thank you again to everyone who joined our Microsoft 365 Community discussion on we hope you got some valuable insights.

We also have a number of questions that could benefit from peer responses, if you’ve come across any of the below before please take a second to reply.

Open questions

[Flexera One]

• Best practices for Datadog license creation and purchase order mapping in Flexera One
• https://community.flexera.com/s/question/0D5PL00000tgW4P0AU/optimal-methods-for-datadog-license-creation-and-po-mapping
• How to integrate Flexera One license availability data into ServiceNow
• https://community.flexera.com/s/question/0D5PL00000tfRj20AE/guidance-on-integrating-flexera-one-license-availability-into-servicenow

[FlexNet Manager Suite On-Premises]

• Resolving Microsoft Office 365 TLS validation errors
• https://community.flexera.com/s/question/0D5PL00000tjyR00AI/microsoft-office-365-is-showing-tls-validation-error-in-task-log-but-test-is-successful

[App Broker]

• App Broker reporting failed deployment via Intune despite successful software installation
• https://community.flexera.com/s/question/0D5PL00000tjkvQ0AQ/deployment-is-coming-through-intune-via-the-app-broker-we-can-see-that-the-software-is-fully-installed-on-the-client-machine-however-the-app-broker-is-still-reporting-it-as-failed

[Snow License Manager]

• Why Adobe Acrobat 2026 Professional subscription users are not uniquely identified in Snow License Manager
• https://community.flexera.com/s/question/0D5PL00000tez3c0AA/why-are-users-of-adobe-acrobat-2026-professional-subscription-not-exclusively-identified-through-snow
• Devices showing inactive and not reporting in Snow
• https://community.flexera.com/s/question/0D5PL00000tddGO0AY/hi-our-computers-are-not-reporting-in-snow-they-are-all-stating-inactive-which-is-due-to-settings-but-not-connecting-to-snow-can-you-assist-please

[Snow inventory]

• Compatible Snow client version requirements for Windows build 26200
• https://community.flexera.com/s/question/0D5PL00000tdUA80AM/what-snow-client-version-do-we-need-for-windows-26200

Thanks so much in advance for taking a look, every reply makes a difference and helps keep the community moving forward 🙏

Mercedes