Noise Microsoft.DocumentDB/databaseAccounts/mongodbDatabases/throughputSettings : throughput when autoscaleSettings are set

[dj-r1]

Describe the noise

Resource type
Microsoft.DocumentDB/databaseAccounts/mongodbDatabases/throughputSettings

apiVersion
2024-05-15

Client (PowerShell, Azure CLI, or API)
PowerShell

Relevant Bicep code

resource mongoDbThroughputSettings 'Microsoft.DocumentDB/databaseAccounts/mongodbDatabases/throughputSettings@2024-05-15' = {
  name: 'default'
  parent: mongoDb
  properties: {
    resource: {
      autoscaleSettings: {
        maxThroughput: 10000
      }
    }
  }
}

Expected response

{
  "apiVersion": "2024-05-15",
  "id": "/subscriptions/0000bb0-000b-0bb0-0000-bb00b0b0b00/resourceGroups/my-rg/providers/Microsoft.DocumentDB/databaseAccounts/my-cosmosdb-account/mongodbDatabases/my-mongodb/throughputSettings/default",
  "name": "default",
  "properties": {
    "resource": {
      "autoscaleSettings": {
        "maxThroughput": 10000
      }
    }
  },
  "type": "Microsoft.DocumentDB/databaseAccounts/mongodbDatabases/throughputSettings"
}

Current (noisy) response

{
  "apiVersion": "2024-05-15",
  "id": "/subscriptions/0000bb0-000b-0bb0-0000-bb00b0b0b00/resourceGroups/my-rg/providers/Microsoft.DocumentDB/databaseAccounts/my-cosmosdb-account/mongodbDatabases/my-mongodb/throughputSettings/default",
  "name": "default",
  "properties": {
    "resource": {
      "autoscaleSettings": {
        "maxThroughput": 10000
      },
      "throughput": 1000
    }
  },
  "type": "Microsoft.DocumentDB/databaseAccounts/mongodbDatabases/throughputSettings"
}

Additional context
WhatIf should not output parameter actual throughput when autoscaleSettings (with maxThroughput) are specified in ThroughputSettingsResourceOrThroughputSettingsGetPropertiesResource Azure documentation as

Value of the Cosmos DB resource throughput. Either throughput is required or autoscaleSettings is required, but not both.

So "throughput": 1000 modify change is a noise. Such parameter can't be specified in ARM template (Bicep) in the scenario with autoscaleSettings.

P.S.
To reproduce the issue be aware that during initial provisioning autoscaleSettings must be present in MongoDb resource due to 'Cannot set throughput for database that is not created with throughput'. With second deployment throughput settings may specified with extension-extension resource (throughputSettings), but can't be added in the initial deployment (issue #58213 azure-docs).