Adding a schema to Eventhub Schema registry with a private endpoint enabled

Question

Greetings,

As the title suggests I am trying to register a schema in an Eventhub Schema Registry which is in a vnet with a private endpoint enabled. I see that there is a warning sign inside the schema group saying:

"This namespace has private endpoint enabled. Not all Schema Registry functionality is currently supported for private endpoint connection".

I also receive an error when trying to register this sample schema which I copied from the docs:

{
  "namespace": "com.azure.schemaregistry.samples",
  "type": "record",
  "name": "Order",
  "fields": [
    {
      "name": "id",
      "type": "string"
    },
    {
      "name": "amount",
      "type": "double"
    }
  ]
}

My question is then is it possible to create the schema at all and am I missing some step because of the vnet and private endpoint?

Regards,
Dimitar

Answer 1

Hi @Dimitar Grozev

Greetings & Welcome to Microsoft Q&A forum! Thanks for posting your query!

Apologies for the inconvenience.

The issue you are facing is due to the limitations of Azure Event Hub’s Schema Registry when using a private endpoint. The warning message indicates, not all Schema Registry functionalities are supported with private endpoint connections.

Schema Registry in Azure Event Hubs provides you with a repository to use and manage schemas in schema-driven event streaming scenarios. Azure Schema Registry is a feature of Event Hubs, which provides a central repository for schemas for event-driven and messaging-centric applications. It provides the flexibility for your producer and consumer applications to exchange data without having to manage and share the schema.

Here are some limitations and considerations for creating an Azure Event Hubs schema registry using Azure portal:

For additional information please refer: Create an Azure Event Hubs schema registry using Azure portal.

Here are the limitations and considerations for Event Hubs namespace:

For details please refer: Allow access to Azure Event Hubs namespaces via private endpoints.

I hope this information helps. Please do let us know if you have any further queries.