Hi,

This is all assuming you have FNMS on premises.

I would start with the actual process. If the license harvesting process is still to be defined, or open to be changed, maybe start with some of these questions:

• What does actually define/trigger when a license can be harvested? This might be a user account status change in AD. Or maybe a workflow where users are asked to return licenses no longer needed? Maybe they even do this proactively?
• Where is this information (point above) stored? How can it be accessed? Maybe this is stored in a worklow engine/ticket system and we can get it form a DB?
• How is this data incorporated into existing FNMS workflows? For example: If a user was disbaled in AD and you therefore disabled the user in FNMS, it would automatically exempt that user account from consuming any licenses. Of course, you can also take more active actions, like removing existing allocations.
• Are possibly multiple triggers/sources/logics from above involved, that need to be combined?

There are nearly endless options to automate these things using business imports. This is usually where you would hire some experienced consultants

Best regards,

Markward