Getting Issue with CES unable to connect with Azure Event Hub

Question

Getting Issue with CES unable to connect with Azure Event Hub

Ajay Agrahari 0

Earlier CES working with Destination Type = AzureEventHubsAmqp this was working with same Credentials and everything but now my Azure SQL Database update and not accepting above destination type and restrict to pass AzureEventHubs only then it is not working.

Getting below error.

error_number error_severity error_state error_message

23679 16 1 Unable to reach the configured destination.

23658 16 62 Change Event Streaming encountered a SQL exception.

22782 10 1 Failed to output batch data for table 3 in partition 1520928802

22777 10 2 Failure reported in table group processing

22777 10 1 Failure reported in database processing

23679 16 2 Unable to reach the configured destination.

Eugenio Rossetto 0 Reputation points

2026-08-31T18:57:23.4433333+00:00

We hit this exact error after the forced move from AzureEventHubsAmqp to AzureEventHubs. The fix for us was the destination location, not the credentials: the new AzureEventHubs type delivers over the Event Hubs Kafka endpoint, and it needs the port to be explicit. Without it, sp_create_change_event_stream_group succeeds but every delivery fails with error 23679 "Unable to reach the configured destination" and the 23658/22782/22777 cascade you're seeing.

Change your @destination_location from:

<namespace>.servicebus.windows.net/<hub-name>

to:

<namespace>.servicebus.windows.net:9093/<hub-name>

and recreate the group (same credential, @destination_type = N'AzureEventHubs'). Delivery started working immediately for us once the :9093 port was in the location. Note you'll have to re-add every table to the group after recreating it, since dropping the group clears the enrollment list.

2 answers

Your answer

Eugenio Rossetto 0 Reputation points

2026-08-31T18:57:23.4433333+00:00

We hit this exact error after the forced move from AzureEventHubsAmqp to AzureEventHubs. The fix for us was the destination location, not the credentials: the new AzureEventHubs type delivers over the Event Hubs Kafka endpoint, and it needs the port to be explicit. Without it, sp_create_change_event_stream_group succeeds but every delivery fails with error 23679 "Unable to reach the configured destination" and the 23658/22782/22777 cascade you're seeing.

Change your @destination_location from:

<namespace>.servicebus.windows.net/<hub-name>

to:

<namespace>.servicebus.windows.net:9093/<hub-name>

and recreate the group (same credential, @destination_type = N'AzureEventHubs'). Delivery started working immediately for us once the :9093 port was in the location. Note you'll have to re-add every table to the group after recreating it, since dropping the group clears the enrollment list.

Answer 1

Ganesh Chelluri 190 Microsoft External Staff Moderator

Hi @Ajay Agrahari ,

Based on your description, the main change appears to be that "AzureEventHubsAmqp" is no longer accepted and the configuration now requires "AzureEventHubs".
The errors:

23679: Unable to reach the configured destination
23658: Change Event Streaming encountered a SQL exception
indicate that CES is unable to communicate with the configured Event Hub destination.

As a first step, please verify:

The CES destination has been recreated using the currently supported "AzureEventHubs" destination type.
The Event Hub is reachable and operational.
The credentials configured for the Event Hub destination are still valid.
No recent networking or access-policy changes were made to the Event Hub environment.
If the issue persists, please share the "complete CES creation/alter statement with all secrets removed" and any additional non-sensitive error details so we can review the configuration.

Ganesh Chelluri 190 Reputation points Microsoft External Staff Moderator

2026-08-06T11:00:50.8566667+00:00

Hi @Ajay Agrahari ,

Just checking in to see if the information provided earlier was helpful. Please let us know if you need any additional details or assistance, and we’ll gladly continue supporting you.

Answer 2

hi Ajay Agrahari & thx for sharing urs issue here at Q&A portal,

if the same configuration worked with AzureEventHubsAmqp and failed only after Azure SQL started requiring AzureEventHubs, this looks more like a product change or regression than a credential issue.

Unable to reach the configured destination is generic and doesn’t prove that Event Hubs itself is unreachable. It can also mean CES failed while validating or opening the connection through the new destination type. I’d confirm that the Event Hubs credentials still work from another client and that no firewall, private endpoint, or network rules changed. If they do work elsewhere and the failure started exactly after the destination type change, the Azure SQL team needs to check whether AzureEventHubs uses different connection requirements or whether the update introduced a regression.

Open an Azure SQL support case and include the database and Event Hubs regions, the full CES configuration with secrets removed, the first failure timestamp, and errors 23679, 23658, 22782, and 22777. The important detail is that AzureEventHubsAmqp worked with the same destination and credentials, while AzureEventHubs does not.

rgds,

Alex

&

If my answer was helpful pls mark it and additional thx if u follow me at Q&A portal

and at my blog https://ctrlaltdel.blog/