An Azure NoSQL database service for app development.
Azure Cosmos DB for Table API - How to enable Account Level Throughput on an existing empty account (without tables)?
Product
Azure Cosmos DB
API for Table
Question
We are using Azure Cosmos DB for Table API and would like to use Account Level Throughput (shared throughput across all tables) instead of dedicated throughput per table.
The Azure Portal shows a dedicated Account Level Throughput blade with the following note:
"You can optionally provision throughput at the account level to be shared by all tables in this account. This setting can be changed ONLY when you don't have any tables in the account."
Our account currently has:
API for Table
0 tables
Continuous Backup enabled
Free Tier enabled
No data
Newly created account
The problem is that we cannot find a supported way to enable Account Level Throughput outside of the Azure Portal.
Microsoft documentation states:
"Enabling account-level throughput cannot be done using ARM templates or Bicep. To enable shared throughput when using API for Table, use Azure CLI or PowerShell."
However, the Azure CLI and PowerShell examples we found appear to be table-scoped and require an existing table name.
Questions
Is there currently a supported Azure CLI command to create or enable Account Level Throughput for a Table API account before any tables exist?
Is there a supported PowerShell command for the same operation?
Is Account Level Throughput intended to be configured only through Azure Portal?
If the Portal control is disabled on an empty Table API account, what permissions or account settings are required to enable it?
Can Account Level Throughput be enabled on an existing empty account, or is it only possible immediately after account creation?
Is there a documented REST API operation for creating the account-level shared throughput offer for Table API?
Environment
Azure Cosmos DB for Table
Region: Sweden Central
Account contains zero tables
Azure Portal shows the "Account Level Throughput" blade
ARM/Bicep deployment is not being used because documentation states this scenario is unsupported
What we have already verified
ARM/Bicep does not appear to support creating Account Level Throughput for Table API. [implementa...on-spec.md | GitHub Cloud Knowledge], [ambicue-co...onments.md | GitHub Cloud Knowledge]
The Azure Portal contains a dedicated Account Level Throughput blade and states that the operation is only allowed when no tables exist. [implementa...on-spec.md | GitHub Cloud Knowledge], [ambicue-co...onments.md | GitHub Cloud Knowledge]
We could not find a CLI or PowerShell example that works at account scope without an existing table. [implementa...on-spec.md | GitHub Cloud Knowledge], [decision-log.md | GitHub Cloud Knowledge]
Could Microsoft clarify the supported and recommended way to enable Account Level Throughput for Azure Cosmos DB for Table API accounts?