Provide a Policy for Querying Table Storage
As it stands out, Table Storage OData Queries return at maximum 1000 results with headers 'x-ms-continuation-NextPartitionKey' and 'x-ms-continuation-NextRowKey'
It would be beneficial to provide a policy which forwards a request to table storage, figures out how many pages there are and sends multiple requests to get and combine all the data into one response.
Raphael Köppel commented
Yes a continuation token policy would be very handy. To Provide Customers direct more the 1000 items from Azure Table Storage via Azure API Management...