Okta Error Occurs When Pushing Atlassian Cloud Group Due to Missing User

An Atlassian Cloud group push fails because a user in the pushed group is missing or inactive in the Atlassian application. Resolve this issue by validating the user account in Atlassian and retrying the group push. Okta displays the following error: 

Unable to update Group Push mapping target App group <group name>: Error while updating user group membership for group <group name>: Bad Request. Errors reported by remote server: Resource [USER] Missing user:<externalId>

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Atlassian Cloud
• Provisioning
• Push Groups

The user listed in the Okta System Log error message is missing or inactive in the Atlassian application.

How is the missing user error resolved?

Validate the user account in Atlassian and retry the group push in the Okta Admin Console.

1. Verify that the user listed in the Okta System Log error message has an active account in Atlassian. A pushed user must be active in Okta, assigned to the application, part of the Okta pushed group, and provisioned and active in the Atlassian application.
2. Verify that the external ID on the application assignment in Okta matches the value in Atlassian. Navigate to the Assignments tab, click the pencil icon next to the user, and verify the external ID.
3. Verify that the user account remains unchanged in Atlassian.
4. Navigate to Applications > Applications > Atlassian Cloud > Push Groups in the Okta Admin Console.
5. Retry the group push.