Example - we have an activity with requester as a logon type. This activity has a time limit defined within a connection profile in the respective access policy and it states maximum session limit to be 60 minutes.
In this case, I can open second, third, etc. session just before initial or subsequent session would expire and have the same RDP session on the target resource indefinitely (would not be limited to 60 minutes total).
Is there an option to limit the number of concurrent NPS sessions we can open using the same requester account to the same resource while another one already exists?
One thing you could do is require approval before a user’s requested session can begin - that way you, or another NPS admin, are in control of how many sessions a user can provision.
Additionally, you could leverage a custom action to check for any duplicate specific activities that are already provisioned and end the session before continuing. This is something I have only begun to look in to in our environment, but if I get some experiment further, I will be sure to share some code. If you beat me to it, I’d love to see another’s approach to the issue.
Thank you all for your feedback. I will submit this as an idea. Having approval workflow in place definitely is an option I totally forgot about custom action(s).
I totally forgot about custom action(s). 
