Bicep version
0.12.40

Describe the bug
Deploy Synapse Workspace through Bicep with trustedServiceBypassEnabled set to true. After deployment otherwise successfully finishes, the setting is "false", which is the opposite of what is declared in the template. Expected "Allow Azure services and resources to access this workspace" to be enabled.

To Reproduce
Deploy Synapse Workspace resource through a Bicep template file using resource group scope in either Complete or Incremental mode.

resource synapseWorkspace 'Microsoft.Synapse/workspaces@2021-06-01' = {
  name: synapseWorkspaceName
  location: azureLocation
  identity: {
    type: 'SystemAssigned'
  }
  properties: {
    azureADOnlyAuthentication: true
    cspWorkspaceAdminProperties: {
      initialWorkspaceAdminObjectId: '<ObjectID>'
    }
    defaultDataLakeStorage: {
      accountUrl: <SymbolicNameForDataLakeStorage>.properties.primaryEndpoints.dfs
      createManagedPrivateEndpoint: false
      filesystem: 'synapse'
    }
    publicNetworkAccess: 'Enabled'
    sqlAdministratorLogin: '<AdminName>'
    sqlAdministratorLoginPassword: '<LoginPass>'
    trustedServiceBypassEnabled: true 
  }
}

Additional context
Also tried the trustedServiceByPassConfiguration resource type as described in documentation:
https://learn.microsoft.com/en-us/azure/templates/microsoft.synapse/workspaces/trustedservicebypassconfiguration?pivots=deployment-language-bicep

However that resulted in a NullRequest: Request was deserialized as null error.