Error BCP400: Fetching types from the registry requires enabling EXPERIMENTAL feature "ExtensionRegistry"

[ngruson]

I'm trying to create an Entra app registration using Bicep as described in https://learn.microsoft.com/en-us/graph/templates/reference/applications?view=graph-bicep-1.0

The error is pointing to an experimental feature called ExtensionRegistry, but I don't see that feature listed in https://github.com/Azure/bicep/blob/main/docs/experimental-features.md.

How can I fix this?

extension microsoftGraphV1_0

resource appRegistration 'Microsoft.Graph/applications@v1.0' = {
  displayName: 'MyEntraApp'
  uniqueName: 'MyEntraApp'
}

My bicepconfig.json file:

{
  "analyzers": {
    "core": {
      "rules": {
        "no-unused-params": {
          "level": "warning"
        }
      }
    }
  },
  "experimentalFeaturesEnabled": {
    "assertions": true,
    "testFramework": true,
    "extensibility": true
  },
  "extensions": {
    "microsoftGraphV1_0": "br:mcr.microsoft.com/bicep/extensions/microsoftgraph/v1.0:0.1.8-preview"
  } 
}

[slavizh]

@ngruson you need extensibility feature enabled in bicepfconfig which you already did.

"experimentalFeaturesEnabled": {
        "extensibility": true
    }

There is nothing more to enable. use the latest Bicep CLI as well. Not sure where you get the error message as you do not provide such information. Also the repository for Bicep Graph issues is at https://github.com/microsoftgraph/msgraph-bicep-types.

[ngruson]

Thanks @slavizh,

I created a smaller sample Bicep file.
It turns out that in isolation it works correctly and the app registration is created.

The error occurs when running Azure Developer CLI (https://github.com/Azure/azure-dev) to deploy my entire solution to Azure.
So I think I'll ask the same question in that repo. Maybe the config file is not being taken into account by azd, not sure yet.

[anthony-c-martin]

@ngruson it sounds like you are using an earlier version of the Bicep CLI to compile. "extensionRegistry" was a previous experimental feature that was later merged with the "extensibility" feature.

To fix this you could either:

• Upgrade the Bicep CLI to v0.30.3 or later.
• Add "extensionRegistry" to the "experimentalFeatures" section in your bicepconfig.json.