The “Microsoft NCE Migration Failures” tool is designed to inform BSS users for failures of retrieving all the necessary data before initializing the auto-migration process from Legacy to New Commerce Experience (NCE) subscriptions, in our platform.

Open

As you can witness from the above schema, there is a Data Collection phase (blue diamond) before the validation step of the auto-migration process of our platform and includes several sub-stages, such as: receiving and logging events from Microsoft, inserting events into a queue, processing them, and locating the Microsoft Tenant and subscription in the platform’s database.
Therefore, this tool will record as much information as possible from the Data Collection step 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 such pre-auto-migration issues.

Accessing the “NCE Migration Failures” Tool

The tool is accessible through the path BSS Setup > Tools > Microsoft NCE Migration Failures.

Open

Viewing the Results of the Tool

When BSS users select the tool, they get redirected to the view page of the tool where they can view a list that is automatically populated with details of any migration failures that occurred before the validation step, as mentioned earlier. This is for any Legacy subscriptions that attempted to be migrated to an NCE subscription.

The available columns of the list of failed migrations are the following:

• Resolved: This checkbox option is utilized for marking a failed migration as resolved (checked) or unresolved (unchecked). No actual action is performed, other than marking each available row, since the list of the tool does not remove automatically the resolved migration failures. Also, this column provides a filter to the users with values True and False, for differentiating the results between the resolved and non-resolved.

• BSS Customer ID (Name): This alphanumeric view field displays a combination of the customer’s ID number and name. When the text “Multiple Accounts” appears, instead of the combination of the customer ID and name, it happens because the option ‘maintain one active’ subscription is enabled in your BSS. In this case, the “see more details” option is available for users to check the details of the customer and the subscription inside the BSS portal. Please check this explanation for more information.

• BSS Subscription ID (Name): This alphanumeric view field displays a combination of the Legacy subscription ID number and name. When the text “Multiple Subscriptions” appears, instead of the combination of the subscription ID and name, it happens because the option ‘maintain one active’ subscription is enabled in your BSS. In this case, the “see more details” option is available for users to check the details of the customer and the subscription inside the BSS portal. Please check this explanation for more information.

• Microsoft Legacy Subscription External ID: This alphanumeric view field displays the identification number of the Legacy subscription inside the Microsoft Partner Center.

• Microsoft Tenant ID: This alphanumeric view field displays the identification number of the Microsoft Tenant.

• Microsoft Completion Date (UTC): This alphanumeric view field displays the date and time Microsoft has finished the migration on the Microsoft Partner Center. Also, this column provides a filter to the users with date sub-panels for defining exact dates and date ranges, for differentiating the results of the list.

• Migration ID: This alphanumeric view field displays the unique reference number used to track the migration process of subscriptions. It is sent by Microsoft after a migration is triggered and it is used by our platform to fetch information about the migration, including the legacy and new commerce subscriptions related to the migration process.
  
  

The BSS user can also click on the “see more details“ hyperlinked text, which is displayed inside the second and third columns (BSS Customer ID & BSS Subscription ID), to reveal more information about the customer name and the legacy subscription inside the BSS portal. Specifically, a new pop-up window appears revealing the following information.

- See more details (clickable option):

• Subscription ID: The ID of the Legacy subscription inside the BSS portal.

• Subscription Name: The name of the Legacy subscription inside the BSS portal.

• Quantity: The number of licenses of the Legacy subscription inside the BSS portal.

• Unit Name: The name of the Unit that the Legacy subscription has (Monthly, Annually, etc.) inside the BSS portal.

• Subscription Status: The actual Status of the Legacy subscription inside the BSS portal.

• Product ID: The identification number of the Microsoft product within the Legacy subscription.

• Product Name: The name of the Microsoft product within the Legacy subscription.

• Customer ID: The identification number of the customer inside the BSS portal.

• Customer Name: The name of the customer inside the BSS portal.

• Instance ID: The identification number of the Microsoft Service Manager instance inside the BSS portal.

• Instance Name: The name of the Microsoft Service Manager instance inside the BSS portal.

Of course, this list can be exported to an Excel file by clicking on the Export to Excel button.

Exporting the Results of the Tool

The export functionality allows BSS users to export filtered results to an Excel file, so that they can then utilize this list when they contact our support team to try and resolve the migration failures.

If you export the list without the use of any filters, then the list will be exported in its entirety. Otherwise, if filters have been used, the list will be exported based on the filters used, containing the data represented by the selected filters.

Contacting our Support Team with the Exported Results

After BSS users have exported the results from the tool, they can contact our support team and raise a ticket by providing the exported results so that we can check in more detail the reason of the failure(s) to resolve them and re-run the migration process.

Once the reasons of failure have been resolved and the migration process is re-run and completed successfully, the failure logged inside this tool is considered resolved and it can be marked as Resolved by clicking on the checkbox option, located at the beginning of the respective row. This action can be performed by both the customer and our support team.

Table of Contents