Page Comparison

In this release, we are introducing the "Microsoft NCE Migration Failures" tool. This tool is designed to inform BSS users about failed auto-migrations from Legacy to New Commerce Experience (NCE) subscriptions before the auto-migration process even begins (before the validation step) within our platform.
Therefore, the functionality of this tool is to log auto-migrations that failed to be initialized automatically and be migrated to our platform. Specifically, this tool monitors the stages of receiving, logging, queuing, and processing events, as well as locating Microsoft Tenants and subscriptions in our databases. If during this gathering of information, there is an error, the tool will record as much information as possible and depict them in detail inside its list, allowing BSS users to export these details to an Excel file. This information can then be communicated to our support team to help resolve such migration issues, streamlining the identification and resolution of migration issues.

We’re excited to introduce a new enhancement to the credit invoice creation process!

Now, when manually creating a new credit invoice with custom items using the Insert from Invoice option, you can easily edit the billing period for each item. This update allows you to deliver clearer billing details, ensuring that any necessary adjustments (e.g., cancellations or changes in usage periods) are accurately reflected.

To edit the billing period, the user selects an existing debit invoice and edits the fields in the pop-up window that appears. Then, you can update the billing period’s start and end dates by selecting the desired dates from the calendar.

In this release, we have made significant improvements to the loading times of the Microsoft Subscription view pages, in the BSS portal, reducing them by up to 50%. This improvement applies to many more Service Managers in our platform. Previously, users experienced longer loading times when viewing a Microsoft subscription page that contains features requiring communication with Microsoft’s systems to fully load. With the first of two phases of BSS improvements, we have enhanced the experience for new and existing BSS users by reducing transition times and addressing problem areas. This initial improvement has resulted in a 13-second reduction in loading times, making the overall user experience faster than ever.
In the upcoming releases, we will introduce the second and final of the two related BSS portal improvements, which will further reduce loading times, especially for the Microsoft Service Manager.

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

1. Wrong Pricing Display for NCE Products with Monthly Billing - Issue Resolved: We have resolved an erratic issue where end customers of Standard Resellers were seeing the reseller’s cost price instead of the correct price when ordering Microsoft 365 Business Premium (New Commerce) with a monthly billing plan. The system now correctly calculates and displays the price, including the reseller’s markup, based on the billing frequency. This fix ensures that the correct installment price is shown in the cart, reflecting the appropriate markup.

2. Azure Plan Order Execution Error When End Customer Purchases the Same Product from Two Different Resellers - Issue Resolved: We have resolved an issue where Azure Plan orders could not be executed due to the error message “Object reference not set to an instance of an object.” This occurred when an end customer, connected to the same tenant in a multitenancy setup, attempted to purchase an Azure Plan from two different resellers. The error was due to a service initialization issue, which has now been corrected, ensuring smooth order processing from both resellers.

3. Improved Microsoft ID Link Loading Time in the Subscription Validation Tool: We have addressed an issue where clicking the ‘Microsoft ID’ link in the Subscription Validation Tool caused a 5-7 second delay before opening the Microsoft Partner Center (MPC) subscription link. This delay was due to the process of handling custom requests. As a temporary solution, we now fetch the URL directly from the database, significantly reducing the delay. This change ensures a smoother and faster user experience while we continue to investigate a permanent fix.