Provide a way to "close" TCP sockets opened by accessing Azure PaaS services
Iterating over resources (such as all storage accounts across all subscriptions) can result in thousands of open TCP sockets. This is particularly problematic for Azure runbooks which suspend runbooks execution when 1,000 sockets are reached.
Either provide a way to close such sockets (e.g. "close-AzureStorage -Context $sa.context) OR at least close sockets automatically in Azure runbooks on a least-recently-used basis. The work-around is to use hybrid runbooks but that defeats the purpose of using the built-in Azure automation.