Migration Method No. 1

This migration method has the following key features:

• Your existing Microsoft 365 application instance is reconfigured.
• Existing Microsoft 365 subscriptions are not changed in CloudBlue Commerce, which allows you to keep the existing configuration of resources and service plans.
• Existing cloud subscriptions, which have reseller relationships with your Direct CSP Provider account, are suspended. New cloud subscriptions, which obtain reseller relationships with the Indirect CSP Provider account of Ingram Micro, are created.

To perform migration using this method, follow these steps:

1. Working together with Ingram Micro staff, send all your customers invitations from the Indirect CSP Provider account of Ingram Micro. All your customers must accept these invitations.

2. For your Microsoft 365 application instance, which is currently configured to use your Direct CSP Provider account, run the readCSPAccounts.py script with the --ignore-disabled option. In addition to the standard output files, the script creates the existsSubs_PARTNER_SUBDOMAIN.csv or existsSubs_PARTNER_TENANT_ID.csv output file that contains cloud subscriptions to be migrated. For details on running the script, see Importing Tenant Subscriptions from the Microsoft Cloud to CloudBlue Commerce.

   Note: You can remove rows from the output file to exclude Microsoft accounts from migration, but you must not modify the content of rows. Also, you can use the --account-domain-list option of the readCSPAccounts.py script to specify which Microsoft accounts you need to migrate.

3. Check the following:

   • The importSubs_PARTNER_SUBDOMAIN.csv or importSubs_PARTNER_TENANT_ID.csv output file must be empty. If there are any rows, this means that there are cloud subscriptions that are not registered in CloudBlue Commerce. You must import, remove, or ignore them (these cloud subscriptions will be migrated only if you import them).
   • The errorSubs_PARTNER_SUBDOMAIN.csv or errorSubs_PARTNER_TENANT_ID.csv output file must be empty. If there are any errors, you must process them before migration.
   • The existsSubs_PARTNER_SUBDOMAIN.csv or existsSubs_PARTNER_TENANT_ID.csv output file must not contain The cloud subscription with the CspId '...' (offer id '...' and limit '...') is an active add-on and is not represented by an Odin Automation subscription messages. If there are such messages, this means that there are cloud subscriptions that are not registered in CloudBlue Commerce. You must either remove or ignore them (in both cases these cloud subscriptions will not be migrated).
4. In CloudBlue Commerce, put all Microsoft 365 subscriptions of your customers on administrative hold, and wait for the respective Microsoft 365 tasks to be processed.
5. Write down the values from the MSSubscriptionIDs column of the existsSubs_PARTNER_SUBDOMAIN.csv or existsSubs_PARTNER_TENANT_ID.csv output file.

6. From the database of the application endpoint of your Microsoft 365 application instance, remove the records of the cloud subscriptions that you obtained in step 5. To do this, use the instructions in this KB article.

7. Working together with Ingram Micro staff, reconfigure your Microsoft 365 application instance for Ingram Micro Syndication. To do this, use the instructions in The Ingram Micro Syndication Scenario.
8. In CloudBlue Commerce, release all Microsoft 365 subscriptions of your customers from administrative hold, and wait for the respective Microsoft 365 tasks to be processed.

After you perform these steps, your new and existing customers will be provided with Microsoft 365 services within the Ingram Micro Syndication program.