Share via

"HCRP403 Error when registering second on prem SQL server in ARC

Anonymous
2025-04-14T21:15:05.1133333+00:00

I have a test on prem SQL server already ARC enabled and is configured as a PE with a link scope and there is also a Virtual network Gateway in the mix. When attempting to register a second SQL server in ARC and a PE with the already existing link scope, we see that the VM is created, however the "HCRP403" error is presented before creating the SQL instance. We also noticed that the error output indicated the connection is "public": level=debug msg="HTTP trace gbl.his.arc.azure.com. " Public ip xxx"

SQL Server Integration Services

1 answer

Sort by: Most helpful
  1. Kuruba Gowthami (US) 0 Reputation points
    2025-04-15T13:49:56.9166667+00:00

    I think the second server is not correctly configured to point/use private endpoint/link, so it is defaulting to public path and triggering the HCRP403 error (mostly the permission issue/network restriction error)

    Try the options to resolve:

    1. Reverify the private endpoint/link configuration.
    2. Confirm the server is routed through the VNG (Virtual Network Gateway) and it is not reaching Azure over a public network path.
    3. Make sure outbound traffic to Azure Arc endpoints is not blocked/rerouted.
    4. Use network trace tools/detailed logs to ensure which endpoint the server is trying to reach.

    Hope this might be helpful

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.