Please help me understand why some properties are not available in bicep

[dulfer]

While building modules for our standardised deployments, I ran into the following which I hope you can answer for me.
Why is it that some resource properties that are available in ARM are not available in bicep? I thought that bicep offered full support for any resource provider, as soon as it got updated.

Support for all resource types and API versions: Bicep immediately supports all preview and GA versions for Azure services. As soon as a resource provider introduces new resources types and API versions, you can use them in your Bicep file. You don't have to wait for tools to be updated before using the new services.

I.e. the following (highlighted) properties for an EventHub namespace are available in ARM templates.
This is taken from the export template automation output.

{
            "type": "Microsoft.EventHub/namespaces",
            "apiVersion": "2022-01-01-preview",
            "name": "[parameters('eventhubName')]",
            "location": "[parameters('location')]",
            "sku": {
                "name": "Standard",
                "tier": "Standard",
                "capacity": 1
            },
            "properties": {
                **"minimumTlsVersion": "1.2",**
                **"publicNetworkAccess": "Enabled",**
                "disableLocalAuth": false,
                "zoneRedundant": false,
                "isAutoInflateEnabled": false,
                "maximumThroughputUnits": 0,
                "kafkaEnabled": true
            }
        },

but not in bicep...

resource eventHubNamespace 'Microsoft.EventHub/namespaces@2021-11-01' = {
  name: '${eventhubName}-evhns'
  location: location
  sku: {
    name: eventHubSku
    tier: eventHubSku
    capacity: eventHubCapacity
  }
  properties: {
    isAutoInflateEnabled: false
    maximumThroughputUnits: 0
    // minimumTlsVersion: '1.2'   <--- this property is not available
    // publicNetworkAccess: 'Enabled'  <--- this property is not available
  }
}

Why can't I explicitly set the Tls version for this service? Should I set this properties somewhere else?
Is it enforcing the latest security defaults?

Reference: Configure the minimum TLS version for an Event Hubs namespace using ARM (Preview)

Namespaces created using an api-version prior to 2022-01-01-preview will have 1.0 as the value for MinimumTlsVersion. This behavior was the prior default, and is still there for backwards compatibility.

[kevball2]

Your Bicep code is using an older API version. The 2022-01-01-preview version doesn't appear in the API list yet. you can manually set the API verion to be the 2022 preview, but you won't get type support.

[dulfer]

I totally overlooked the difference in API version!
Given Bicep docs states Bicep immediately supports **all preview** and GA versions for Azure services, I did not expect code editor's intellisense and type support would lag behind. My mistake. Thanks for answering!

[kevball2]

That would be a good question for @alex-frankel or someone from the Bicep team. Does your ARM template deploy successfully against that preview API? If so, it would be interesting to understand at what point can Bicep discover the new API versions.

In my previous message I noted that the API you show in your ARM template does not even show up in the version list in MS docs yet. If it does work and is available, why would it not be listed in the Doc's page yet?

[alex-frankel]

In order for a type to show up in bicep, two things need to happen:

1. the swagger spec needs to be published to the main branch of the azure-rest-api-specs repo.
2. the bicep team needs to generate updated types based on the latest snapshot of that repo and ship the latest types with a new bicep release.

It looks like that type may have been added recently: https://github.com/Azure/azure-rest-api-specs/tree/main/specification/eventhub/resource-manager/Microsoft.EventHub/preview/2022-01-01-preview

So if you upgrade to the latest 0.7.4 release, I would expect to see this new type available.

[dulfer]

Indeed, after upgrading to 0.7.4.23292 bicep cli builds without warnings.
Including type support in vscode. Thanks!