Issue Summary

Users with an Atlassian Access subscription are able to integrate their Org with an external Identity Provider using User Provisioning (SCIM integration).

We are currently releasing the ability to use this integration to also sync external users (users from unverified domains).

However, in case you are syncing external users, if you click on Force Sync on Okta (you can find this button under Atlassian cloud Attribute Mappings, accessing  the Atlassian app > Provisioning), the external accounts will get unlinked on the Atlassian directory side, being removed from the synced groups, even if no change was performed on these accounts.

Steps to Reproduce

1. Create a SCIM integration between Okta and Atlassian.
2. Sync a group with unmanaged accounts.
3. Access the Atlassian App on Okta.
4. Navigate to Provisioning.
5. Click on **Force Sync, without making any change on the attributes or their values.

Expected Results

As no change was synced to the external accounts, they shouldn't be unlinked neither removed from the synced groups on Atlassian side. 

Actual Results

The accounts are unlinked and removed from the synced groups. Below log is displayed on the troubleshooting logs for User Provisioning (on the Org):

Email update to unmanaged user with ID #, primary email <user-email>, unlinked any associated atlassian account.

Workaround

Engage Atlassian Support team providing this bug report, so we can manually re-link the account on our side.