Automatic Migration Process
The Auto-Migration feature operates in the background, continuously monitoring and managing all Microsoft-led migrations. This process involves:
Auto-Capture Migration Events: Our system automatically detects and captures any migration initiated by Microsoft, using a dedicated listener to subscribe to migration-related events from the Microsoft Partner Center (MPC).
Successful Migrations Handling:
Legacy Subscription Cancellation: Upon successful migration completion in the MPC, the existing legacy commercial license-based subscription in your BSS platform is automatically canceled.
NCE Subscription Creation: Corresponding New Commerce Experience (NCE) subscriptions are automatically imported into your BSS platform, mirroring the newly created NCE subscriptions in the MPC.
Customer Notification: Email notifications are sent to your resellers or customers to inform them of the successful completion of the Auto-Migration process.
Failed Migrations Handling:
Legacy Subscription Reactivation: For migrations that fail to complete successfully, our system keeps as active the legacy subscriptions in your BSS platform.
Customer Notification: Email notifications are sent to your resellers or customers to inform them of the unsuccessful outcome of the Auto-Migration process.
This automated approach ensures that your subscriptions remain seamlessly integrated with the MPC, minimizing manual intervention and potential errors.
Auto-Capture Migration Events
When Microsoft begins migrating a legacy subscription, our platform detects the event and initiates monitoring of the migration process. During the migration process, the legacy subscriptions remain active in our system but are locked, and no action is permitted on them.
Cancellation of the Legacy Subscription
When Microsoft has successfully completed the migration process, we will automatically cancel the legacy subscription from the date the migration was initiated or the legacy subscription’s start date (whichever is earlier).
When will the legacy subscription be cancelled from the subscription’s start date?
Due to the Microsoft Partner Center (MPC) operating in the GMT timezone, there may be instances where the migration initiation date in the MPC differs from the subscription's date in your platform. For organizations operating in time zones ahead of GMT, there may be scenarios where the start date of the legacy subscription in your BSS platform precedes the date the migration was initiated. In such cases, the legacy subscription in our system will be canceled from the subscription's actual start date.
Once the legacy subscription is successfully canceled within our platform, a corresponding credit invoice will be issued to reflect the prorated amount for the unused service days. This credit will cover the period between the migration's initiation date and the end date of the legacy subscription. For more details, please check the https://interworkscloud.atlassian.net/wiki/spaces/ICPD/pages/969769240/Auto-Migration+Process+in+the+BSS+Platform+Following+the+Microsoft-led+Migration#Use-Cases-of-the-%E2%80%98Auto-Migration%E2%80%99-Process page.
NCE Subscriptions Creation
The Microsoft Partner Center (MPC) migration process may generate multiple NCE subscriptions to accommodate the add-ons associated with the legacy subscription. For each eligible add-on attached to the legacy subscription, a corresponding NCE subscription will be created, ensuring that all add-ons are mirrored in the NCE environment. These NCE subscriptions will seamlessly be imported into your BSS platform, residing under the same BSS account as the legacy subscription they replace. Each NCE subscription will be imported with the exact same properties as its NCE counterpart in the MPC, including the start date (the date the migration is completed), the number of licenses, billing cycle, billing frequency, promotion status, and any other relevant details.
Pricing and Promotions
The billing of NCE subscriptions will follow the price lists assigned to the BSS customers under which they reside. Therefore, assigning price lists with equivalent NCE products to all your resellers and customers is crucial before the auto-migration process begins. Also, any promotions eligible for NCE offers will automatically apply to the newly created NCE subscriptions.
Customer Notification
Since the Auto-Migration process is a background running process, the only visual feedback of whether it is successfully working or not is done via our distinct Email Notifications. Specifically, our platform informs its users in case of a failure during any of the Auto-Migration steps (validation process, provisionless cancellation of Legacy subscription, creation of NCE subscription) and when the Auto-Migration process has been completed successfully.
🔹 For more information concerning the Email Notifications of the ‘Auto-Migration’ process, please proceed to the Auto-Migration Notifications on Our Platform page.
Use Cases of the ‘Auto-Migration’ Process
In the following three use cases of Auto-Migration, we depict how the Auto-Migration works for Legacy Subscriptions that their End Dates in BSS are aligned with those kept in the Microsoft Partner Center and Legacy Subscriptions for which the BSS End Dates are different than those kept in Microsoft Partner Center.
Migration Custom Fields
Upon successfully completing the Auto-Migration process, the respective migration details are saved inside the newly created NCE subscriptions' view page in the form of custom fields. More specifically, these custom fields are the following:
‘Migration’ Custom Fields in the Legacy Subscription View Page in BSS | ‘Migration’ Custom Fields in the NCE Subscription View Page in BSS |
|---|---|
|
|
 |  |
These custom fields can be managed by navigating to BSS Setup > Subscriptions > and selecting the respective instance.
Tenants & Backordering After the Completion of the Auto-Migration Process
All of the above will be reflected via the backordering mechanism to root/parent organizations along with their child organization(s), wherever applicable.
What can Happen In the BSS While the 'Microsoft-led Migration' is Ongoing
While the ‘Microsoft-led Migration’ of a legacy subscription is in progress in the Microsoft Partner Center (MPC), its status on the MPC is suspended, but its status on our platform remains Active, and it will still be invoiced/will renew automatically once its renewal date is reached, if it’s not canceled in-between. Therefore, to avoid any glitches or inconsistencies between the two systems (BSS & MPC), while the ‘Microsoft-led Migration’ of a legacy subscription is still in progress, our system applies a checking mechanism on that subscription on our platform, so that the user cannot perform any provisioning actions on this subscription. The same checking mechanism will inform the user if something is wrong. Consequently, an explanatory message is displayed when users attempt provisioning actions on active legacy subscriptions during the ‘Microsoft-led Migration’ process. The message is visible in both the BSS and Storefront platforms when a user tries the following actions:
Increase/Decrease licenses of the subscription
Cancel the subscription.
Suspend the subscription.
Activate the subscription
Upgrade/Downgrade the subscription.
Change the name of the subscription.
Add an add-on.
Increase/Decrease the licenses of an add-on.
Cancel an add-on.
Informative Message in the BSS Platform | Informative Messages in the Storefront |
|---|---|
 |  |
When the auto-renew option is activated on the legacy subscription, users can change the number of licenses on the subscription’s renewal. In this case, there are two possible scenarios:
If the ‘Microsoft-led Migration’ fails, the number of licenses will change, because the legacy subscription in the Microsoft Partner Center will be re-activated.
If the ‘Microsoft-led Migration’ is successfully completed, the number of licenses will not change because the legacy subscription in the Microsoft Partner Center will be suspended.
⚠️ However, if, for any reason, the subscription in the BSS platform fails to sync, then the Auto-Migration must be handled by the interworks Support team.