hope this fix your issue There is no way to enumerate partition keys (without doing a table scan), so you can either: do a full table scan, keeping track of various partition keys you find along the way, along with highest-value row key keep track of your partition keys as you write them to table storage (e.g. create another table with just your partition keys).
Difference in value - Azure Table Storage Timestamp and new DateTime property in Azure Table Storage
help you fix your problem On my analysis I now have resolved it using ToUniversal and ToLocal _#1. Since Timestamp is GMT and TimeReceived saves as LocalTime as I was using DateTime.Now Changing it to UniversalTime solved the issue . Now I see both having the same value _#2 Using ToUniversalTime while querying\saving the Azure TableStorage to retreive\save the data and back to ToLocalTime to display on UI helped to save\retrieve \display correctly _#3 I am now saving GMT. Anyone suggestion here is appreciated _#4 Any suggestion on best practice is appreciated _#5 Changing DataType to DateTimeOffset will not help I feel. ToUniversal and ToLocal helped resolve the issue _#6ToUniversal and ToLocal helped resolve the issue as I mention here above in 2nd bulleted point _#7 Selecting Date from UI is local, so now from Controller(MVC) I send the Date converted to UTC to Azure
How to add a property to Azure table storage row with Azure Powershell module