We will not migrate the remaining 1% of customers to the new, centralized user management experience. This cohort includes customers with multiple sites, and are therefore typically larger, enterprise-sized organizations. Many of you in this group have shared with us that centralization isn’t always the best fit.
Unfortunately they're omitting the fact that as @Jason Bowne and I have discovered, it's not that we don't WANT the new user management experience. It's that our instances are too complex or too "big" to be migrated to the new experience.
Jason wrote:
Hello! I put a support ticket in to request we move to the centralized management. I was given a list of blockers that are preventing me from having Atlassian move our organization to centralized management experience. We have taken care of several of the blockers but there is one that is causing me to just wait and let Atlassian do the move later when all the blockers are figured out.
I had similar issues to Jason - our user and groups are set up "just so", and the numbers for both are relatively big (although for a regular tech company? Doesn't seem so to me): 6000 users, 5000 groups.
We are using Azure AD for Nested Groups rather than his SCIM, but got the same frankly ludicrous suggestion from Support that we "turn off" synchronization with Entra (Azure AD) just for the weekend while they run the migration, and then they turn it back on.
Uh, no.
So I guess then, they just decided to not go for 100%, and leave us 1%ers (not the rich kind) to languish without the new user management features.
Thank you @Darryl Lee ! Appreciate the 'add' on the challenge. I ultimately decided to not do the migration even though I did a significant amount of blocker work removal including flagging over 7,000 users for deletion that were in Disabled status via the process we crated using power automate and a spreadsheet download that was cleaned up for targeted account deletion.
The core reason I made the call to not do the migration was the need to disable SCIM and have everyone sign in with username and password. ALL the users don't know what their password is because we have SSO turned on. The risk of making the entire Atlassian suite inaccessible is not a risk we were willing to take so we cancelled the support ticket and we will wait for whatever smooth transition Atlassian figures out. The user management isn't 'broken' so we are not pursuing fixing it :)
Oh man @Jason Bowne I also wasted so much time trying to clean up disabled users: Similar process - spreadsheets, filtering, and then Appfire (Bob Swift's) ACLI tool to bulk delete. So I totally sympathize.
With reduced group availability I didn't even see a real path forward to having users log in at all during the migration and didn't relish telling everyone in the company to "just stay logged out over the weekend", although I suppose we did do that when we migrated to the Cloud.
I too am glad that the current system isn't broken, but I could really use the new Directory API endpoints that are only available if you're on "Vortex" (Atlassian's codename for Centralized User Management).
But even more importantly, Vortex is a prerequisite for a bugfix that we need! There is an EAP to fix:
7. This is only available for customers who are in the new, enhanced user management experience within admin.atlassian.com.
It seems like Atlassian made substantial structural changes in Vortex, which... is great. They just didn't fully think through how to migrate (slightly) larger organizations to it. Which is not so great.
And because (they claim) it's only 1% of their customers, I suppose they're making the calculation that it's just not important enough to prioritize.
Very cool thanks @Darryl Lee really good information. Yes I love the pace of innovation with Atlassian and their focus that I truly feel they are pushing into the Enterprise space for more than just software development. I feel sooo lucky that we started with cloud and we use Jira, JPD, JSM, confluence and it has completely changed how our entire IT department functions. I hope Atlassian sees that changes at the enterprise customer (not enterprise license) level customers have to have a different mindset that may not be as fast as they are used to with Vortex and the how of upgrading being a prime example of that.
Can there be an ORG admin that does not need to have software licensing for each product in full? So you can have admin user to make API calls? that is not an day to day user?
OR just even an day to day user that is an ORG ADMIN but does not use all products.
Also it seams like lots of tasks that other admins used to be able to do now need or will need org admin / site admin.
158 comments