Select to view content in your preferred language

AGOL Disabled Account returns Licences

815
2
07-04-2022 03:03 AM
Status: Open
MartinLomas
Occasional Contributor

When an AGOL Member Account is Disabled, it would be good if the ArcGIS Pro Licences and Extension Licences associated with the disabled account were returned to the available count.  Also, that the Disabled Account was no longer counted as a member taking up User Type resources.

2 Comments
KylieA
by Esri Contributor

Hello! This is a great idea. I've come across an additional use case for this request that is also very compelling, so I figured I'd add it here: 

Automatic deallocation of licenses from disabled users would also be useful for large organizations who have "uncapped"/large amounts of Named User licenses for ArcGIS Pro, and recover subscription costs by charging individual underlying offices (i.e. those that reside under the umbrella of the larger organization) based on the proportion of the licenses they are using. While availability of the license might not be an issue if it remains connected to a disabled user in terms of availability of licenses for other users, this may lead to each individual office paying more than their share of licenses, when they are not actually using them. In other words, if a user leaves the organization, the ArcGIS Online admin disables their account (to avoid deleting content), and overlooks deallocating ArcGIS Pro licenses, the office will be on the hook to pay for an ArcGIS Pro license for this nonexistent user. 

ChelseaRozek

Was about to write my own idea for this, so here's what I was going to say:

Migrating to the new user types from concurrent licensing is going to add the hassle of assigning/unassigning licenses to named users, especially when it comes to seasonal or temporary employees. One thing that would make this a little easier was if disabling a named user freed up that license. As disabling the user means they can't log in, no license would in use anyways. Normally I have to get around this by moving all their items to myself and then back to them later when they start working again. As long as you have at least one Creator/Admin user in your organization with a valid license that could have hypothetically taken all those items or ownership of the groups, it seems like that should be allowed. It would save us a lot of hassle of moving items around, trying to remember which groups they were in, hoping their same name is still available, and reassigning group ownership.