Hi @RickWeisbond ,
I know this is an old post but I just wanted to share some alternative workflows to limit batch geocoding.
According to the documentation, all default user roles can use geocoding services in AGOL. We can control users' access to geocoding services using custom roles. However, it is not possible to allow a user to use geocoding services but limit batch geocoding. Aside from using custom roles, there are some alternative solutions:
1. Use credit budgeting to limit the credit usage allowed for each user. This limit does not apply to storage, app related credits, and using premium content through a proxy.
2. Add a copy of ArcGIS World Geocoding service to your geocoders under Utility Services in Organization settings where it allows you to disable batch geocoding. The advantage of this workaround is that it would only apply to this geocoder and users can batch geocode using other available geocoders in the org. On the other hand, one downside of it is that it would affect all users in the organization and the ability to batch geocode won't be controlled by user type/role.
3. If you want to give some users or an specific app access to batch geocoding, you can add ArcGIS World Geocoding Service as a secured item in your AGOL account, limit the access to a specific URL or IP that is being used by Emergency Operations Center and give them access through a proxy.
Best,
MJ