Problem Definition

Bulk upload to authentication policy via CSV is a key way for teams to quickly move many users to an authentication policy. However, if the CSV contains users with an incorrect email, do not have an Atlassian Cloud account, are not claimed or have some other property that makes them ineligible for bulk movement, then the bulk movement service will fail with only a generic error message:

• "Unable to find members - We’re unable to find any of these members. Make sure all your members are managed accounts and try again."
• "Unable to find some members - We’re unable to find some of these members. Make sure all members are managed accounts and try again."

Suggested Solution

Improve error messaging to show all users who are not eligible to be bulk moved, and why they failed to be moved.

Why this is important

Customers with many users are especailly impacted by this. For example, moving users from a local policy (that does not allow SAML SSO logins) to a policy that does allow SAML SSO enforced logins. This process should take just a few moments, but when moving thousands of users and receiving a generic error message, this can take quite some time to "find a needle in the haystack" – the user causing the issue.

Without better error messaging, customers cannot self-serve without lots of additional effort on their part.

Workaround

There is no workaround currently. This feature request will be updated when there is one.

You may find the following helpful:

• Ensuring that your CSV only has users from your managed accounts list.
• Double checking which users your team has claimed in Atlassian Cloud. Only claimed users can be placed in your authentication policies.
• Try cutting the CSV in half until you are able to successfully upload the CSV.