is the notion of a Table required at all in Azure Table service?

is the notion of a Table required at all in Azure Table service?

I am working with azure table services. What I would like to ask is
whether the Azure internals care about the notion of Table at all?
Making things fast largely depend on partition key and row key. Tables do
not look like containers or Grouping of entities because there is no limit
on number of tables you can create. The total storage size is tied to my
storage account.
So is Table just a notion to help people transition from RDBMS land or do
they serve a purpose internally? Can I do applications with a single table
design without worrying about performance? After all, if table is a just a
tag then I may as well include as part of partition key.