Migration to the Adobe Business Platform - the new Adobe Identity and Admin Console

Building slightly on Doug's concerns, I also received one of these colorful missives this morning. As did all of my admin users, several of my standard non-admin users, and one user who's account has been disabled since 2022. I'm curious as to why people who have left my organization, and were never admins, needed to receive this message?

I'd like to understand how I can explicitly REVOKE consent for this unnecessary move. My message included the note as below, which is the source for my specific concern. We've just finished a rather painful SSO migration, and I do not want to migrate my people to an entirely different platform all over again, nor do I want to explain to my external customer users that they need new credentials either. The rather high-handed demand that we WILL do so in the next 30 days or else is also rather distasteful.

I have no problem with a new console for my own management process, but I do not need the confusion and headache of telling 350 people that I just finished training on login procedures that they have to learn something else. It is not acceptable for Adobe to email my users with login instructions that do not align with our internal training documents and change management processes. When announcements need to be sent, they come from me alone with appropriate tailored distribution lists.

For those of us who have organizations that do not use any other Adobe product, and thus have no need for a consolidated admin tool, how can we decline to participate entirely? 

Hi @jonahmc,

I just finished a call with Adobe and an 18K+ user client during which I volunteered to create the "Adobe IMS Console 30-Day Migration Best Practice Diagram".

Watch this space...

UPDATE: here…

Regards,

Doug

P.S. @katherinela I will include a placeholder for if and when you learn of an "decline to participate entirely" mechanism; but from what I learned today, believe that Adobe's expectation is that once a client receives their initial "Adobe IMS Console Admin User migration" notification such a client will then be fully migrated (prod, preview, and sandboxes) within 30 days

😨 You are a brave one @doug_den_hoed__atappstore!

I am afraid our thousands of requesters are going to be thoroughly confused by an adobe login screen. A large number of these requesters are not technical at all and  we have enough issues with them accessing just through regular SSO, where they don't even NEED a login. I can't find any information on how to make this easier for those people that don't use other Adobe products and have very little understanding of technology.  And, of course, most of them are not going to read the announcements they receive in advance about what to expect. Does anyone know of a video or other resource to share with free users (reviewers in this case) to give them a visual of what to expect? The screenshots I found will only confuse them more...

@rhondagayletx my client had the same fear, but I found that by giving them screenshots of the screens they'd expect to encounter and hosting "office hours" after the change was made we were able to remedy the issue.

Hi @mmcgovern,

Thanks for sharing your screenshots and office hours tips: it's good to hear that they were effective for your users.

If you or anyone else reading who has completed their migration of Workfront into Adobe IMS Console have any additional "Success Stories" to share, I suspect those who've not migrated would be encouraged to hear about them.

Regards,

Doug

Thanks for the continued commentary here @doug_den_hoed__atappstore !

We worked through our migration and tested it in our Preview environment. It works, but the extra screens are annoying to click through. To make it even more of a challenge, now our Creative Cloud apps are tied to the "Personal account" login and Workfront is tied to our "Company or School Account." This only affects a portion of our users, but for those users it's definitely confusing to log into one account for your CC apps and the other for Workfront. This also screwed up by Experience League profile, my Workfront ExL profile got tied to my personal account (which really isn't personal!), so if I want to check the commuity for Workfront help and saved posts, I have to log out of the Workfront App. I'm trying to get this fixed, but when I opened a Workfront support ticket, they said they couldn't help and to contact Adobe support. When I contacted Adobe support, they told me they couldn't help and to contact Workfront support (@jon_chen any ideas on how I can get this fixed?).

Adobe wanted to migrate our Production environment early, but we're waiting until the date they gave us, which is next Monday. Fingers crossed that everything goes smoothly.

@sheri_whitten I'm in a similar situation with two Adobe accounts.  My IT team advised me to use different browsers for different things.  So I use Chrome for Workfront and Experience League and Edge for the admin console.  That way each browser remembers the username and password for a different account.  If you can't end up getting your accounts merged (or while you wait for it), this could help.  

@chloewy yep, that's what I've been doing, and it works for now, but I do have an open ticket where support thinks they found someone that can fix it. Fingers crossed! 

Regarding the migration in general, we were fully migrated as of this past Monday. It seems so long ago already! I will say, the preemptive email with screenshots I sent to users a week prior was helpful. Most of my active users have not had any issues accessing Workfront, but if they have, or want, Creative Cloud apps, it's a different story. Now users are requesting licenses to CC apps through our "Workfront/Company or School account" and our company has that tied to personal accounts with work email addresses (a different team and company that manages those), so I have to deny requests and let the other team know. If you have everything under one Adobe account, I would imagine your experience will be much better. 

One additional caveat, we never had SSO enabled in our custom refresh sandbox and since I don't use it often, it was refreshed last November. I cleaned up all our users in our production environment so that only active users were migrated. Well, surprise! Adobe migrated anyone who was still left active in our custom refresh sandbox and sent invitation emails to all those users to access the sandbox - people who don't even know we have a custom refresh sandbox, people left the company, external users set up just for our reference and testing, you name it. Now that was an unexpected headache.