How is Autoprovisioning intended to work after Admin Console migration?

We haven't migrated yet but have been told that auto-provisioning will work provided that we go through the Enterprise Storage Migration beforehand.

Following this closely.

I've had the same questions, and it's why I've continually delayed our Admin Console migration.  One support rep mentioned an upcoming feature called a 'Product access automation rule'. This was supposed to be a URL that new users could visit that would create a new account, but I haven't heard anything about that in a couple of months.  

When we've talked to different levels of support reps, we've gotten different answers about what's possible. Hoping others can provide more insight, thank you!

Autoprovisioning doesn't currently work.

There are half-workarounds, though. Here's how it works for us:

Keep in mind that our instance uses Azure SSO, so results may vary if you use a different approach to user logins.

With Azure, we're able to create a group. That group has SSO access to Workfront, therefore anyone in the group has access to Workfront. When an employee is added to the Workfront Azure group, it creates a record in Workfront with the lowest access level and the user can freely login. Ahead of our migration, IT populated this group with existing users. We had a relatively seamless transition. There were a few people who had login snafus (maybe a dozen out of nearly 2000 users), but I had a dedicated person in IT to help me monitor this for the first couple of weeks after our migration.

So how do we add users to the group? When we broached the idea of adding all company employees to this Azure group, IT basically laughed in my face. Instead we created a ticketing system to automate 90% of the process:

1. Someone submits a ticket. (The submitter can anyone: the user who needs access, their manager, a project owner who knows they'll need to communicate with the new user in a project, me, etc.)
2. That ticket automatically sends an approval request to the system admin (me).
3. The approver approves the request.
4. The system refreshes within the hour, which creates the Workfront record.

Yes, this was a big change, so preparing communications before, during, and after your migration is essential. Things I did to help with the transition:

• I posted instructions on our SharePoint site on how a new user can gain access to Workfront. If someone knocks on my virtual door in confusion that we no longer have autoprovisioning, I send those instructions (or submit the ticket on their behalf) and move on.
• I keep an ear out for any bulk needs. Recently we had a case in which we needed to add over 200 users just so they can access a request form. In that case, I submitted a spreadsheet to IT and they bulk loaded those users.
• Any users who are added to a proof will appear in my user list as an email address. I  audit the system every other week to submit the IT ticket to formally add them. I do this with a report that picks up new user entries within the last 3 weeks. I have a report with recurring tasks that prompt me to do this new user audit so I don't forget.

A year later, I still have people within my department who come to me confused, but it's fewer and fewer.

Exception: Our external users have their own email addresses and therefore don't log in with SSO. As system admin, I add them to the admin console by their email address. I follow up with an email to the external user with instructions on how to log in.