AI Docs

Importing Microsoft License Statements | v6.1 and above

3 min read

Importing Microsoft License Statements | v6.1 and above

Microsoft License Statements (often referred to as an MLS) can be imported under any of the Microsoft Licensing menu items apart from Retail Transactions.

Note that only the import of Microsoft License Statements in English is currently supported. When requesting a Microsoft License Statement from your re-seller, please ensure it is requested in English as the language.

Importing your Microsoft License Statement

To import a Microsoft License Statement, click on the Import button to open the Import Data File dialog. Click on the magnifying glass to browse to the Microsoft License Statement you wish to import (you must ensure that the Microsoft License Statement is not open in Excel)

Note that if you use Zones to partition your data, you will need to import the Microsoft License Statement into the relevant zone.

When importing a Microsoft License Statement, there are three options:

Replace previously imported entitlement data:

This option will replace only entitlement that has been previously imported. Any manually added transactions will not be overwritten. Use this option if you have manually added Microsoft transactions to reflect license novation’s or other entitlement that is missing from your Microsoft License Statement.

Replace all entitlement data:

This option will replace all Microsoft Entitlement Data including manually added transactions

Set the effective date of ‘SA’ transactions purchased against ‘Enterprise’ agreements to the agreement start date:

This option is for advanced users only. Often when customers purchase or renew Enterprise Agreements there may be gaps in Software Assurance. This may be for a valid reason or may be due to procurement errors. This option will correct the gaps in the Software Assurance.

Note that you should check that any discrepancies in Software Assurance are valid before using this option: During an audit situation, the gaps in Software Assurance may be deemed to be an issue and that the entitlement may not actually be valid.

Once you have selected your preferred option, click OK to import and process the Microsoft Licensing Statement.

Invalid Transactions

After the import completes, the number of Valid and Invalid transactions will be shown, as in the example below:

Invalid transactions could occur for one of the following reasons:

  • The Microsoft Part Number or SKU does not exist in the Microsoft Licensing Definitions.

  • The Microsoft Part Number is no longer valid as a licensable product e.g. Microsoft SharePoint Designer. This became a Free Product in 2007.

  • The entitlement relates to Cloud based subscriptions such as Azure Monthly Commitments.

To identify the invalid transactions click on the View button to bring up the Missing Part Numbers dialog:

For the missing part number, you have a choice as to what to do:

  • Click the Download button to download the missing part number and submit them to Certero for categorisation. Use the Help Desk facility of the Customer Centre to raise a support ticket with details of the missing part numbers for categorisation (simply attache the downloaded file to the ticket). The relevant numbers will be categorised by Certero and be provided in the next release of the Software Recognition Database definitions.

  • You could choose to continue with the import and upload your Microsoft License Statement for processing.