During a group push to Office 365, an error occurs because a user in the group has a provisioning error. Resolve this issue by identifying the user with the Rockstar browser extension, fixing the provisioning error, and retrying the group push. Okta generates the following error in the Okta Admin Console: 

Unable to update Group Push mapping target App group <group name>: Could not update the Office 365 group membership for <group name> because the group could not be found, received error: Received response with
error code Request_ResourceNotFound. httpStatusCode=404 errorCode=Request_ResourceNotFound errorMessage="Resource '<object ID>' does not exist or one of its queried reference-property objects are not present." client-request-id=<client request id>

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Office 365
• Group Push
• Provisioning

The resource object ID mentioned in the error belongs to a user rather than a group. The user has an Office 365 provisioning error, which prevents Okta from updating the group membership in the target application.

What steps resolve the Office 365 group push error?

Identify the user associated with the object ID using the Rockstar browser extension, resolve the provisioning error, and retry the group push.

1. Navigate to the Okta Admin Console and open the Office 365 application.
2. Use the Rockstar browser extension to download the App User file.
3. Open the downloaded file and locate the user by matching the <object ID> from the error message with the value in column D (externalID).
4. Navigate to the Tasks page or the user profile in the Okta Admin Console to locate the Office 365 provisioning error for that specific user.
5. Resolve the user provisioning error and verify that Okta successfully assigns the user to the Office 365 application.
6. Navigate to the Push Groups tab in the Office 365 application.
7. Retry the group push to complete the process successfully.

Related References

• Using the Rockstar Browser Extension with Okta