Make Event Hubs relocation fail when the target service endpoint is missing

Source facts

Microsoft’s Event Hubs relocation guidance requires recreating source-region service-endpoint restrictions in the destination. In the network rule set, the virtual-network rule must identify the target subnet.

The guidance sets ignoreMissingVnetServiceEndpoint to false so deployment fails when the required service endpoint is not configured at the destination. Exporting the old configuration is therefore not the whole target-network preparation. Microsoft Learn.

Applicability

Identify whether the source namespace actually uses service-endpoint rules and which target network replaces each source reference. This check is for that network-control path, not a claim that it configures private endpoints or completes event migration.

DSE recommendation

DSE recommends pairing each migrated network rule with evidence that the intended target subnet has been prepared. Keep the missing-endpoint validation enabled instead of suppressing it to make a deployment pass. Coordinate the network and messaging owners so a source-region identifier is not mistaken for a valid target reference. Review other relocation dependencies separately.

Verification

Inspect the proposed template’s target subnet identifier and missing-endpoint flag before deployment. In an approved test environment, verify that the absent prerequisite produces the intended failure and that a correctly prepared target permits the expected deployment. Then test authorized client connectivity through the selected network path. A successful template deployment should not be recorded as proof that every producer, consumer or retained event has migrated.

Official references

Microsoft Learn: Relocate Azure Event Hubs to another region. Source retrieved September 9, 2026.