Microsoft Perpetual License Assets

 

The Microsoft Perpetual Licenses are represented in our system as assets. The assets are part of our Billing module and when your resellers or your customers place an order for a Perpetual License, a new asset record is created in our platform for managing and invoicing purposes. 

On this page, we explain what information we keep in the asset record for each Perpetual License and how you or your customers can manage them.

The Perpetual License Asset Record


For every Perpetual License purchased by a customer, our system creates an asset record. This record is the trigger for the provisioning mechanism and it is related to the Microsoft Perpetual License that is created in the Microsoft systems.

This record is accessible through the Billing > Assets module. The information we keep for each Perpetual License is the following:

  • General Information:

    • Name: By default, it's the Perpetual License plan name.

    • Status: The status of a Perpetual License can be active or canceled.

    • Provisioning Sync Status: It can be synchronized or failed analogous with the status we are keeping for the Office 365 subscriptions. 
      Note: If the status is failed, you can try to re-synchronize the asset record with Microsoft, by editing the asset and then saving it. During the re-synchronization, if the provisioning sync status becomes synchronized, this means that a new Perpetual License asset was created in the Microsoft systems and is now connected to that specific BSS asset. Otherwise, if it fails, no change occurs to the Perpetual License asset in BSS or the corresponding asset under the Microsoft systems.

    • Purchase Date: The date the asset record was created and the provisioning was executed.

  • Product Section: Each asset record is related to the purchased Perpetual License product and in this section, you have the pricing details.

  • Microsoft Perpetual License Details:

    • Perpetual Order ID and Perpetual Order ID Alias: We collect this information from Microsoft when we execute the provisioning.

    • Perpetual License SKU: Is the original name of the Perpetual License.

    • Perpetual ID: Microsoft Subscription ID for this perpetual license.
      Note: Sometimes the "Perpetual ID" is not returned from Microsoft API during the initial provisioning, If you see that this field is empty, edit and save again the asset record for the field to be updated.

Managing the Perpetual Licenses from the Storefront


Your resellers and your customers can access the Perpetual Licenses they have purchased from the Assets section that is in the Billing area of your Storefront.

By clicking on the respective link, your reseller or customer will be redirected to the list of the Perpetual Licenses he has purchased.

The details page of a Perpetual License in Storefront includes all the information our system keeps as explained in the paragraph Perpetual License Asset Record.

Managing the Perpetual Licenses in BSS


The Perpetual Licenses are stored in our system as asset records. You can find them if you navigate to BSS > Billing > Assets module or from the assets section that is available on the account details page.

Provisioning of failed Perpetual License Assets


The Perpetual License assets have a "Provisioning Sync Status" field for understanding if the Perpetual License has been provisioned successfully in Microsoft systems. If the sync status is failed, you can try to re-provision the Perpetual License asset, by editing and saving the record. Afterwards, the following message appears:

  • If you continue, a new Perpetual License will be provisioned and a new Perpetual License asset will be created in the Microsoft Partner Center. 

  • If you cancel that action, no Perpetual License will be provisioned, meaning that it will remain as-is in BSS and no Perpetual License asset will be created in the Microsoft Partner Center.

The only way to synchronize a BSS Perpetual License asset with the one residing in the Microsoft Partner Center is by manually adding the external ID to the database since no reconciliation tool exists for assets yet.