I think there could be value here to implementing a decorator and just using it any time there's an API call that uses a continuation token. It seems like that would be cleaner and reduce code duplication.

The decorator concept satisfies the continuation token handling, but in most cases, users use these in some sort of loop, and making them a generator and exposing the underlying data intuitively is better than requiring the user to extract the data of interest.

For instance, query_tables() can directly return an iterable of TableMetadata instead of the user needing to invoke PagedTables.tables

I see your point; I was oversimplifying. I do feel there's some kind of reusable approach though. I'll think it through and post something more intelligent later if I can get my thoughts aligned.