Currently we supply an offset that is used as a continuationToken, however if this token is not correctly being supplied it could potentially have an issue where it is not able to actually query the data out of the Azure Blob Container.
- It came up when adding the capability set a "nativeKey" to begin querying data from.
 
- This transpired as requiring a continuationToken to begin from a specific point within a Container for the Azure Blob client