unable to update throughput settings of a sql database container in cosmos db via bicep

Question

I am trying to update cosmos sql container throughput settings via bicep. Bicep deployment is successful however the configuration is not in place... anyone else is facing this? please help.. thank you

resource db_account 'Microsoft.DocumentDB/databaseAccounts@2024-02-15-preview' existing = {
name:'sql-sit'
}


resource sqldb 'Microsoft.DocumentDB/databaseAccounts/sqlDatabases@2024-02-15-preview' existing = {
  parent:db_account
name: 'sqldatabase'
}

resource container 'Microsoft.DocumentDB/databaseAccounts/sqlDatabases/containers@2024-02-15-preview' existing = {
  parent:sqldb
  name: 'data'

  }
  

  resource thp 'Microsoft.DocumentDB/databaseAccounts/sqlDatabases/containers/throughputSettings@2024-02-15-preview'  = {
  parent:container
  name: 'default'
    properties: {
      resource: {
        throughput:400
        autoscaleSettings: {
          maxThroughput: 4000
          autoUpgradePolicy: {
            throughputPolicy: {
              incrementPercent:10
              isEnabled: true
            }
          }
        }
      }
    }
  }

Answer 1

Hi Pamitha Herath,

Appreciate your effort is sharing the solution/suggestion for the question so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution which is product limitation in case you'd like to "Accept " the answer.

Solution:

Bicep isn't supported for enabling autoscale on an existing database or container and only supported Azure portal , powershell and Azure CLI according to below

https://learn.microsoft.com/en-us/azure/cosmos-db/autoscale-faq#can-i-enable-autoscale-on-an-existing-database-or-container-

If you have any other questions or are still running into more issues, please let me know. Thank you again for your time and patience throughout this issue.

Please remember to "Accept Answer" if any answer/reply helped, so that others in the community facing similar issues can easily find the solution.

Answer 2

Hi Pamitha Herath,

Welcome to Microsoft Q&A forum.

As I understand, you are unable to update throughput settings of a sql database container in cosmos db via bicep.

Could you please let us know if are redeploying the Bicep file with updated RU/s since to change the throughput (RU/s) values, redeploying the Bicep file with updated RU/s is needed?

Also, please let us know the Cosmos DB configuration related details so that we can check at our end.

Thanks

Answer 3

Hi Pamitha Herath •,

It is recommended to please file a support ticket for deeper investigation and in case if you don't have a support plan, do let us know here so that we can check on other options to unblock you. Thanks

Answer 4

Hi ShaktiSingh-MSFT

Raised MS support ticket and advised that bicep isn't supported for enabling autoscale on an existing database or container and only supported Azure portal , powershell and Azure CLI according to below

https://learn.microsoft.com/en-us/azure/cosmos-db/autoscale-faq#can-i-enable-autoscale-on-an-existing-database-or-container-

Thanks all your help!