Content Comparison

We are excited pleased to announce a significant improvement to our Microsoft ESD Asset license notification system: Grouped ESD Notification Emails now seamlessly integrates with Parallel Provisioning! Customers used to receive separate emails for each Microsoft ESD license, resulting in cluttered inboxes. The Grouped ESD Notifications feature now consolidates license information into a single email per order. This improved feature is compatible with the platform's Parallel Provisioning capabilities.

Image Removed

💎 Value: The improved Grouped ESD Notifications feature streamlines ESD license delivery for our customers by consolidating all license information, including ESD tokens and download links, into a single email per order, even when utilizing Parallel Provisioning. This reduces email clutter, simplifies license management, and provides a more efficient and user-friendly experience when purchasing multiple ESD licenses.

🚀 Activation: This feature is available on demand. To activate Grouped ESD Notifications for your organization, simply create a support ticket with our teaman enhancement to the invoicing process for Microsoft ESD orders. This improvement aims to provide a smoother experience for our distributors by ensuring that all ESD order items within the same BSS order are assigned the same Purchase Order (PO) number. As a result, Microsoft can now consolidate all items from a single BSS order into one invoice.

💎 Value: Distributors will now receive a single invoice from Microsoft for all ESD items within a single BSS order, eliminating the need to process multiple invoices for the same order. This simplifies accounting, reduces administrative overhead, improves clarity, and streamlines reconciliation, ultimately making it easier and more efficient for distributors to manage their ESD purchases.

⚙️How it works: In the past, distributors received multiple invoices from Microsoft when a single BSS order included more than one ESD order item. For example, if there were five ESD order items, distributors would receive five separate invoices from Microsoft. Now, the system automatically assigns the same purchase order (PO) number to all ESD order items that belong to the same BSS order. This consistent PO number enables Microsoft to group these items together and issue them under a single invoice.

🚀 Activation: You do not need to take any action. This update has been automatically applied to this release.

The following issues were addressed, with fixes applied where necessary:

1. Issue with Reducing Add-On Quantity Before Auto-Renewal Managed Renewal Synchronization - Issue Resolved: We have resolved an issue where users encountered errors when trying to reduce the add-on quantity before auto-renewal. Customers were being prevented from decreasing the quantity from 1500 to 1000, even when all conditions were met. The fix involves adding extra validations for product type quantity limits during the subscription management renewal process. This ensures that add-on quantity changes or cancellations at the end of the billing cycle are now processed correctly, without errorsmanaged renewals for subscriptions with scheduled quantity changes were not processing in the correct month due to timezone differences. This led to discrepancies between our system and Microsoft's subscription quantities. Actions on our platform that conflicted with the billing cycles have now been restricted to prevent unintended changes. This fix ensures synchronization and accuracy between interworks and the Microsoft Partner Center billing cycles, enhancing overall system reliability.

2. Issue with Invoice Accessibility in Public API - Issue Resolved: We have fixed an issue that prevented access to invoices through the API V3 using the GET/api/Invoices call. This problem mainly affected invoices with an exchange rate of 0, which typically occurred in imported subscriptions. We have identified and resolved the root cause, so all relevant invoices are now accessible.

3. Manage Renewal Error in BSS - Issue Resolved: We have resolved an issue that occurred when scheduling subscription quantity changes during Manage Renewal via BSS. The issue caused incorrect information to be sent to the Microsoft Partner Center, leading to errors. With the fix in place, the process now functions correctly and ensures accurate data is transmitted going forward.