Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Next »

This page provides information about the systemic notifications that are dispatched from our platform to keep you informed about the progress of the legacy subscriptions migration.

Migration Completed Successfully

Once the migration process is successfully completed in both MPC and interworks.cloud platforms, a notification titled “Migration completed successfully” will be dispatched. You can find this notification in the “Subscriptions” folder under the “Customers Notifications” section in the BSS Setup. The notification includes information about the migrated legacy subscription and the NCE subscription created from the migration process.

Note: If the migration process results in multiple NCE subscriptions (due to add-ons on the legacy subscription), the notification will only provide information about the primary NCE subscription.

Migration Failed to be Completed in our Platform

After the migration is completed in MPC, our platform initiates an internal migration process that consists of the following steps:

  1. Data Validation: To complete the migration in our system, we require a unique BSS legacy subscription synced with the migrated MS legacy subscription. If we find two BSS subscriptions in different BSS organizations linked with the same migrated subscription, we will abort the migration since we cannot determine which subscription to migrate. In this case, the notification “Migration validation requirements not met” will be dispatched.

The subscription uniqueness rule is not applied for subscriptions managed from your Tenant Resellers and also exists on your BSS for billing purposes.

  • Cancellation of Legacy Subscription - If we fail to cancel the legacy subscription in our platform, we will dispatch the notification “Auto cancellation failed during migration”.

  • Creation of the NCE Subscription(s) - If we fail to import the NCE subscription(s) in our platform, we will dispatch the notification “Auto creation failed during migration”.

valsetup.jpg

If you receive any of the notifications mentioned above, it indicates that the BSS platform and the Microsoft Partner Center are not aligned. To resolve the reason for the failure of the Auto-Migration process, further assistance is required from the Inteworks support team. They will help you identify the root cause of the issue and provide you with the necessary steps to resolve it.

Migration Failed to be Completed in MPC

In case Microsoft fails to complete the migration within 72 hours, there is no notification sent from interworks.cloud platform.

Table of Contents

  • No labels