Non-derived POCO and Azure Storage
azure-table-storage
Solution
Take a look at `DynamicTableEntity` (ctrl+f for it). It can be used to query and insert entities.
Using this type, you won't introduce any dependencies intor your Domain Model, however you will have to convert a POCO to a DynamicTableEntity by yourself – this process can easily be automated though if you're willing to flag your POCOs with a custom interface and write a mapper (basically you just need a dictionary of properties + need to know wich ones are Partition/RowKey).
The reason why you can't just save any entity in Azure Table Storage is that it needs to know which property acts as Partition Key and wich as Row Key. The upside of having to work with `DynamicTableEntity` on a "lower level" is that you can create queries that return only a subset of properties which reduces resource consumption. This may or may not be beneficial in your case.
Problem
Is it possible to have a non-derived POCO for Azure Table Storage? In other words, a POCO that does not derive from `TableEntity` or implement `ITableEntity`? It seems a step backward to have to have a model which is dependent on the interface or base class, as this causes reference leaks upward in the chain - I cannot set up the model in another tier without it having to know about Azure Storage for either the interface or the base class!