Resolving License Change Log (LCL) Provisioning Failures

Modified on Fri, Feb 7 at 12:02 PM

Applies to: Work 365 | Audience: Administrators, IT Teams, Billing Specialists

Overview

In Work 365, automatic provisioning of subscriptions may sometimes fail, resulting in a "Failed Provisioning" status on License Change Logs (LCLs). This guide outlines common provisioning error messages, their causes, and step-by-step resolutions to help users efficiently troubleshoot and resolve LCL provisioning failures.


Common Provisioning Errors and Resolutions

1. Prior License Change Logs Awaiting or Failed Provisioning

Cause:

A previous LCL is either awaiting provisioning or has failed, preventing new license changes from processing.

Resolution:

βœ… Identify the first failed LCL and resolve its issue.
βœ… Update its Provisioning Status to "Awaiting Provisioning".
βœ… Update any subsequent failed LCLs to "Awaiting Provisioning" and retry provisioning.


2. Account Does Not Exist for Subscription

Cause:

The subscription is not linked to a customer account in Dynamics 365.

Resolution:

βœ… Open the Subscription record in Dynamics 365.
βœ… Ensure the Customer field is populated. If missing, assign the correct CRM account.
βœ… If the Customer field is locked, use the Dynamics Level Up Extension (God Mode) to unlock and edit it.
βœ… Return to the LCL and set its Provisioning Status to "Awaiting Provisioning" to retry.


3. Provider Account Does Not Exist for Subscription

Cause:

The provider account for Work365.Providers.MicrosoftCspProvider is missing.

Resolution:

βœ… Navigate to Work 365 > Provider Accounts.
βœ… Ensure the customer’s Provider Account is mapped to a CRM account.
βœ… If missing, create a new CRM account and map it under Provider Accounts.
βœ… Update the LCL Provisioning Status to "Awaiting Provisioning" and retry.


4. Error Connecting to Partner Center: Timeout

Cause:

Work 365 could not connect to Microsoft Partner Center due to a timeout error.

Resolution:

βœ… Change the LCL Provisioning Status back to "Awaiting Provisioning" and retry.
βœ… Navigate to Work 365 > Providers > Microsoft Partner Center, then click "Verify Connectivity".
βœ… If verification fails, the consent token for the Work 365 integration account may have expired.
βœ… Re-authenticate with Microsoft Partner Center, then retry provisioning.


5. Maximum Subscription Limit Reached (Sandbox Environments)

Cause:

Sandbox environments only allow up to five (5) subscriptions per customer.

Resolution:

βœ… Deactivate additional subscriptions in Work 365.
βœ… If needed, create a new customer, billing contract, and subscriptions for testing purposes.


6. Missing Partner Agreement Confirmation

Cause:

The required Customer Agreement is missing.

Resolution:

βœ… Navigate to Work 365 > Agreements.
βœ… Create a new customer agreement.
βœ… Return to the LCL and set the Provisioning Status to "Awaiting Provisioning".


7. Missing Provider Part Number

Cause:

The Provider Part Number is missing from the subscription.

Resolution:

βœ… Navigate to Work 365 > Products.
βœ… Locate and copy the Provider Part Number.
βœ… Paste it into the subscription’s "Provider Part Number" field.
βœ… Set the Provisioning Status to "Awaiting Provisioning" to retry.


8. Input String Was Not in the Correct Format

Cause:

Microsoft Partner Center was unavailable at the time of provisioning.

Resolution:

βœ… Open the failed LCL and set its Provisioning Status to "Awaiting Provisioning".
βœ… Retry provisioning multiple times if necessary.


9. Object Reference Not Set to an Instance of an Object

Cause:

A generic error indicating an unidentified issue within Dynamics 365.

Resolution:

βœ… Contact Work 365 Support at support@work365apps.com.
βœ… Provide screenshots and a detailed error report.


10. Synnex Provider: Status Code BadRequest

Cause:

This error occurs with Synnex automatic provider subscriptions.

Resolution:

βœ… Ensure the Synnex provider setup is correctly configured.
βœ… Verify connectivity by navigating to Work 365 > Providers > Synnex, then click "Verify Connectivity".


11. Account is on Credit Hold

Cause:

The customer’s account is on credit hold, preventing provisioning.

Resolution:

βœ… Lift the credit hold on the account.
βœ… Retry provisioning by updating the LCL Provisioning Status to "Awaiting Provisioning".


12. Subscription Not Found in Partner Center

Cause:

The Subscription ID does not exist in Partner Center.

Resolution:

βœ… Verify the Subscription ID in Partner Center.
βœ… If missing, update the LCL Provisioning Status to "Not Applicable".


13. Subscription Quantity Requirement Not Met

Cause:

Some subscriptions require a minimum quantity to be provisioned.

Resolution:

βœ… Deactivate the failed subscription.
βœ… Create a new subscription with the required quantity.
βœ… Ensure the correct provisioning frequency is set before saving.


14. Billing Cycle Mismatch Between Parent and Add-on Subscription

Cause:

The provisioning frequency of the add-on does not match the parent subscription.

Resolution:

βœ… Deactivate the failed subscription.
βœ… Set the Provisioning Status of the LCL to "Not Applicable" and archive it.
βœ… Create a new subscription with the correct provisioning frequency.


15. Subscription Cannot Be Updated Due to Deleted Status

Cause:

The subscription was deleted in Partner Center.

Resolution:

βœ… Create a new subscription for the same product.
βœ… Ensure it provisions successfully.
βœ… Deactivate the previous subscription and archive the LCL records.


Additional Notes

βœ” Always check Work 365 logs for detailed error messages.
βœ” Microsoft Partner Center downtime can cause temporary provisioning failures.
βœ” Contact Work 365 Support if none of the above solutions resolve the issue.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article