Microsoft Office 365 Provisioning Error "License <license> does not correspond to a valid company License"
Last Updated:
Overview
Microsoft Office 365 provisioning flow fails with the following error visible in the Okta dashboard:
Automatic profile push of user <user> to app Microsoft Office 365 failed: Could not push profile for Office 365 user <user>, received error: Received response with HTTP status code 400. httpStatusCode=400 errorCode=Request_BadRequest errorMessage="License <license> does not correspond to a valid company License."
Applies To
- Microsoft Office 365
- Provisioning
- Error
Cause
The Microsoft Office 365 application license data has not been updated in Okta.
Solution
Use one of the following methods to update the Microsoft Office 365 application data in Okta:
Method 1
Navigate to Okta's admin panel, then navigate to the Applications tab and click More to select Refresh Application Data (NOTE: This will trigger an import of application data for all applications configured with Provisioning.):
Method 2
Re-authenticate API credentials being used for provisioning to/from Office, which will cause the download and updating of application data into Okta (this will only refresh the application data for Microsoft Office 365):
-
Go to the Okta admin panel and navigate to Applications > Microsoft Office 365 > Provisioning > Integration.
-
Click Edit, then click Re-authenticate with Microsoft Office 365. A new window will open. Log in with the account mentioned below the above-mentioned button, and then save it.
- Afterwards, attempt the user provisioning again. Go to Okta Admin Console and navigate to Dashboard > Tasks. Any failed assignments should appear under Tasks.
- After identifying the failed task for the user that should be retried, click on Retry Selected.
