[PINNED] - KNOWN ISSUES - READ HERE FIRST

[legra-ms]

Updated 9/14/2020:

• [PRIORITY] Long collection sessions (over an hour) using CLI credentials will time out and cause errors. This is because access tokens have an expiration of roughly 60 minutes and Stormspotter does not currently support automatic refreshing tokens. The Azure Identity team for the SDK is currently working on automatically refresh credentials but I will be testing workarounds in the meantime. If your long run time is caused by a large Azure AD environment, there is no current work around. If you have large subscriptions, you can split your collection up by subscriptions using the --subs flag to specify the subscriptions you want to enumerate.

• On Windows, running the collector with CLI credentials may fail the first time fairly quickly with ValueError: I/O operation on closed pipe. This is a result of how asyncio works on Windows, and the way the collector will handle the ProactorEventLoop for Windows. It is likely only to occur when either you've just logged in via az cli before running the collector, or if your access tokens have expired and you attempt to run the collector. Running it a second time should be successful. If not, create an issue.

• Currently, Stormspotter only supports running containers locally. Attempting to upload to the frontend hosted remotely will be unsuccessful but this behavior is expected to change in the future as the tool matures.