[AVM Module Issue]: Not able to setup account throughput limit on CosmosDB Account level (Provisioned Capacity mode)

[dmusic]

Check for previous/existing GitHub issues

• I have checked for previous/existing GitHub issues

Issue Type?

Feature Request

Module Name

avm/res/document-db/database-account

(Optional) Module Version

0.8.1

Description

When using CosmosDB AVM module, it is not possible to setup Account throughput limit when using Provisioned capacity mode.
See more about account throughput here: https://learn.microsoft.com/en-us/azure/cosmos-db/limit-total-account-throughput

This is possible in Azure portal:

and also in ARM template:

and Vanilla Bicep:

If not set it opens up account for unlimited throughput, so if overlooked it could cause additional costs for application workflows.

As the implementation is straight forward, it would be great to include it in the next release.

(Optional) Correlation Id

No response

[microsoft-github-policy-service]

Important

The "Needs: Triage 🔍" label must be removed once the triage process is complete!

Tip

For additional guidance on how to triage this issue/PR, see the BRM Issue Triage documentation.

[avm-team-linter]

@dmusic, thanks for submitting this issue for the avm/res/document-db/database-account module!

Important

A member of the @Azure/avm-res-documentdb-databaseaccount-module-owners-bicep or @Azure/avm-res-documentdb-databaseaccount-module-contributors-bicep team will review it soon!

[microsoft-github-policy-service]

Warning

Tagging the AVM Core Team (@Azure/avm-core-team-technical-bicep) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly.

Tip

• To prevent further actions to take effect, the "Status: Response Overdue 🚩" label must be removed, once this issue has been responded to.
• To avoid this rule being (re)triggered, the ""Needs: Triage 🔍" label must be removed as part of the triage process (when the issue is first responded to)!