This article discusses an issue with Microsoft Office 365 Provisioning tasks failing with the following error:

Automatic provisioning of user XXX to app Microsoft Office 365 failed: Could not push profile for Office 365 user XXX@domain.com, received error: Received response with HTTP status code 400. httpStatusCode=400 errorCode=Request_BadRequest errorMessage="Instantiating an implicit user role is not supported." client-request-id=XYZ request-id=YYY timestamp='MMDDYYYY HH:MM:SS' method=POST url=https://graph.microsoft.com/v1.0/directoryRoles

• Microsoft Office 365 with provisioning enabled
• Okta Integration Network (OIN)
• The problematic Microsoft Office 365 app assignment was created with role assignment of one or more MS implicit user directory roles: User, Guest User, Restricted Guest User being selected.

The Office 365 provisioning 400 bad request error Instantiating an implicit user role is not supported. It was thrown by Microsoft Graph API when an Okta Admin attempted to assign a user one or more Microsoft implicit user directory roles: User, Guest, or Restricted Guest User, as described in Microsoft Documentation.
 

This is an MS Graph call limitation. Not an Okta product issue. For more details about this MS Graph call limitation with implicit user directory role, please contact Microsoft Support Team directly for further assistance. 

To solve the failed O365 app provisioning error on the Okta end, please follow the steps below: 

1. Navigate to Okta Admin Console > Dashboard > Tasks page, locate the failed O365 app assignment or provisioning task.

2. Click on the Edit Assignment button, review the current role assignment selection for each app assignment, and ensure to deselect/uncheck all of the MS implicit user directory roles, including the User, Guest, and Restricted Guest roles, from the current Office365 app assignment.   
3. Scroll the page to the bottom, click the Save Assignment and Retry button. 

4. The app assignment should auto-retry and complete successfully without the previous provisioning error this time. 
5. Repeat step 2-4 until all the failed tasks with the same error.