Going to update the data store to work on a one table per project basis to pre-empt some likely administrative problems with the one table for all approach we have at the moment. Here's the interface we'll need to implement this feature.
Run all of the tests against both in-memory and local azure table storage. Not sure if we'll do this on the build server (which doesn't have local Azure storage...)
Change to a system where we use one table per organization for data storage instead of just one huge table (should make things a bit more maintainable/redundant)