The customer accounts you selected in the previous step of the conversion procedure must be prepared.
The following preparation activities are performed by the script prepareMOSI2CSP.py for each customer tenant of every customer account:
1 The customer tenant is validated against the following requirements:
• The customer tenant must not have trial syndication cloud subscriptions.
• The customer tenant must not have syndication cloud subscriptions which cannot be converted into CSP cloud subscriptions.
137
• Office 365 subscriptions of the customer tenant can include non-Office 365 resources only if the limits of the resources are zero.
• None of the Office 365 subscriptions of the customer tenant must include 'DNS Hosting' resources which are in use by domains.
Validation is necessary to identify if a customer tenant is ready for conversion. If a customer tenant does not pass validation, this means that it is not ready for conversion and further preparation activities are not performed for it.
2 MOSI API communication is disabled for the customer tenant. This is needed to protect customer tenants and their cloud subscriptions from changes made in Odin Automation.
3 The MOSI Customer ID of the customer tenant is stored. The MOSI Customer ID is sent to Microsoft to convert the customer tenant and its cloud subscriptions on the Microsoft side.
4 The mapping between the customer account and its customer tenant is stored. This mapping will be used to find the customer account of the customer tenant in further steps of the conversion procedure.
Parameters of prepareMOSI2CSP.py Script
Note that the app-id and gateway-url parameters and the --mosi-app-instance-id parameter are mutually exclusive.
• --conversion-mode – It defines the mode of conversion. You must specify the resplitSubscriptions value.
• --on-hold – It defines if Office 365 subscriptions are put on administrative hold. You must specify either yes or no. Note that the same value must be used in further steps of the conversion procedure.
We recommend using yes to prevent customers from placing upgrade and downgrade orders during conversion.
• --mosi-app-id – It defines the identifier of a source Office 365 APS 1.2 application (Syndication Partner Program). You must use the value you prepared in the previous step of the conversion procedure.
• --mosi-gateway-url – It defines the URL of the gateway application of a source Office 365 APS 1.2 application (Syndication Partner Program). You must use the value you prepared in the previous step of the conversion procedure.
• --mosi-app-instance-id – It defines the identifier of a source Office 365 APS 2 application instance (Syndication Partner Program). You must use the value you prepared in the previous step of the conversion procedure.
• --csp-app-instance-id – It defines the identifier of a target Office 365 APS 2 application instance (CSP Program). You must use the value you prepared in the previous step of the conversion procedure.
138
specify the parameter if your Odin Automation installation includes OA Billing.
• --input-file – It defines the name of a CSV file containing a list of customer
accounts which must be prepared for conversion. You must specify the name of the CSV file you prepared in the previous step of the conversion procedure.
• --out-file – It defines the name of a CSV file containing a list of customer tenants which are ready for conversion. The CSV file is created by the prepareMOSI2CSP.py script. The file is sent to Microsoft to convert the customer tenants on the Microsoft side.
• --error-file – It defines the name of a CSV file containing a list of customer tenants which are not ready for conversion. The CSV file is created by the
prepareMOSI2CSP.py script. If the parameter is not specified, the default name error_YYYYMMDD-HHMMSS.csv is used.
Input Files of prepareMOSI2CSP.py Script
The prepareMOSI2CSP.py script uses an input CSV file containing a list of customer accounts which must be prepared for conversion. Each row of the CSV file contains the following data of a customer account:
• CustomerId – The identifier of the customer account.
• other auxiliary columns (optional) – These columns are ignored by the script.
Output Files of prepareMOSI2CSP.py Script
The prepareMOSI2CSP.py script creates an output CSV file containing a list of customer tenants which are ready for conversion. The name of the CSV file is defined by the --out-file parameter of the script. Each row of the CSV --out-file contains the following data of a customer tenant:
• MosiCustomerId – The MOSI Customer ID of the customer tenant.
The script creates an output CSV file containing a list of customer tenants which are not ready for conversion. The name of the CSV file is defined by the --error-file parameter of the script; if the parameter is not specified, the default name
error_YYYYMMDD-HHMMSS.csv is used. Each row of the CSV file contains the following data of a customer tenant:
• Aps – The APS version of the Office 365 application to which the customer tenant belongs.
• mosiAppIdOrMosiAppInstanceId – It contains one of the following: the identifier of the Office 365 APS 1.2 application to which the customer tenant belongs; the identifier of the Office 365 APS 2 application instance to which the customer tenant belongs.
• CustomerId – The identifier of the customer account to which the customer tenant belongs.
• MosiCustomerId – The MOSI Customer ID of the customer tenant.
139
• SubscriptionId – The identifier of an Office 365 subscription which blocks the conversion of the customer tenant.
• Error – An error message.
Log and Auxiliary Files of prepareMOSI2CSP.py Script
The prepareMOSI2CSP.py script creates the following log and auxiliary files:
• prepareMOSI2CSP_YYYYMMDD-HHMMSS.log – A log file containing general messages, such as information messages and error messages.
• mosi2csp_mapping.csv – A CSV file containing mappings between customer accounts and their customer tenants. The file is auxiliary and must not be modified or renamed. The file will be used by the completeMOSI2CSP.py script in further steps of the conversion procedure.
Running prepareMOSI2CSP.py Script
Log in to the host where the conversion scripts are placed. Run the prepareMOSI2CSP.py script.
Example (Office 365 APS 1.2 / Syndication Partner Program):
python prepareMOSI2CSP.py conversion-mode resplitSubscriptions on-hold yes --mosi-app-id 100 --mosi-gateway-url
https://office365.provider.com/Office365GatewayApplication/HTTPEndpoint.aspx --csp-app-instance-id 1000 --pba --input-file input.csv --out-file out.csv --error-file errors.csv
Example (Office 365 APS 2 / Syndication Partner Program):
python prepareMOSI2CSP.py conversion-mode resplitSubscriptions on-hold yes --mosi-app-instance-id 999 --csp-app-instance-id 1000 --pba --input-file input.csv --out-file out.csv --error-file errors.csv
After running the script, check the output CSV file containing a list of customer tenants which are not ready for conversion. If the file is not empty, you have the following options:
• Investigate and fix the errors. Run the script again using the same values of parameters.
Repeat this until all customer tenants are ready for conversion.
• Postpone processing the customer tenants which are not ready for conversion and process them later. Note that you will need to start the conversion procedure from the beginning for the postponed customer tenants.
Troubleshooting
Use the KB article https://kb.odin.com/en/129840 for troubleshooting.
140
The customer tenants you prepared in the previous step of the conversion procedure must be converted on the Microsoft side:
1 Fill out a conversion request form:
a Download the conversion request form template provided at https://kb.odin.com/en/130124.
b Fill out the form using the information you prepared earlier:
• The email address of the administrative user of the required syndication partner account.
• The Microsoft ID of the required CSP partner account.
• The CSV file containing the list of the customer tenants.
2 Send the file of the form to [email protected].
3 Microsoft will perform conversion on its side and provide you with two CSV files:
• A CSV file containing a list of customer tenants which were successfully converted on the Microsoft side.
• A CSV file containing a list of customer tenants which cannot be converted on the Microsoft side.
4 Check that the CSV files received from Microsoft have the MosiCustomerId column.
5 Upload both the CSV files to the host for running the conversion scripts.
The CSV files received from Microsoft will be used in further steps of the conversion procedure.