Updating Microsoft.AppConfiguration/configurationStores/keyValues fails via Bicep, but is accepted by Azure Portal

[lettucemode]

Bicep version Bicep CLI version 0.30.23 (ec3612efc7)

Describe the bug I have a 7.3KB JSON object value for an app config key I am attempting to deploy through Bicep.

When setting this key-value manually via Azure Portal, there are no issues.

When using Bicep, the Azure deployment gives the following error:

{
  "code": "DeploymentFailed",
  "target": "/subscriptions/<omitted>/resourceGroups/<omitted>/providers/Microsoft.Resources/deployments/<omitted>",
  "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.",
  "details": [
    {
      "code": "PayloadTooLarge",
      "message": "The request entity is larger than limits defined by server.",
      "additionalInfo": [
        {
          "type": "ActivityId",
          "info": {
            "activityId": "<omitted>"
          }
        }
      ]
    }
  ]
}

To Reproduce

appconfig.bicep

param keyValues array

resource appConfig 'Microsoft.AppConfiguration/configurationStores@2023-03-01' = {
  name: 'appConfigName'
  location: eastus
  sku: 'Standard'
  properties: { ... }
}

resource configStoreKeyValue 'Microsoft.AppConfiguration/configurationStores/keyValues@2023-03-01' = [for item in keyValues: {
  parent: appConfig
  name: item.key
  properties: {
    value: item.value
    contentType: item.content_type
    tags: item.tags
  }
}]

appconfig.bicepparam

using 'appconfig.bicep'

param keyValues = [
  {
    key: 'some_key_name'
    value: 'an admittedly kinda large JSON object'
    content_type: 'application/json'
    tags: {}
  }
]

Additional context If these needs to be reported in a different repo, happy to move it there. Or maybe I'm trying to do something I shouldn't :D just let me know.