NAV SOAP Connection to BC Cloud

(9) Share

Report

Posted on by PP-09121354-0

Hi Experts,

I’m working on an integration between NAV 2017 (on-premise) and BC Cloud, where I’m pushing data from BC Cloud to NAV.

I’m using a SOAP service from NAV with the following endpoint:

https://navwstest.ABC.com:7047/TEST_WEB/WS/CompanyName/Page/ItemStaging

This service works perfectly in Postman for both GET and POST requests.

But, when I try the same from BC Cloud, I receive the following error:

"There was an error while executing the HTTP request, error request: NameResolutionError. Make sure you are connecting to a valid endpoint."

Could you please help me understand what might be going wrong? Or is it not possible to integrate NAV with BC Cloud in this way?

Thank you.

Categories:

Dynamics 365 Business Central

Microsoft Dynamics NAV

Dynamics 365 Business Central migration

I have the same question (0)

All responses (7)

Answers (5)

Suggested answer

RockwithNav 8,600 Super User 2025 Season 2 on at

Like (3)

Report

Why SOAP?

Why not this - https://yzhums.com/6117/

Was this reply helpful? Yes No
Verified answer

Sohail Ahmed 11,136 Super User 2025 Season 2 on at

Like (4)

Report

Business Central Cloud can’t reach on-prem NAV endpoints unless they’re publicly accessible. The error means it can’t resolve the NAV URL. To fix it, expose the NAV SOAP service over the internet securely (e.g., via HTTPS) or use Azure services like API Management to bridge the connection.

✅ Mark this as the verified answer if helpful.

Was this reply helpful? Yes No
Verified answer

Sahib Dino 196 on at

Like (3)

Report
Business Central Online (Cloud) runs in Microsoft’s SaaS environment and cannot access private on-premise resources directly. The error NameResolutionError means that the DNS name (navwstest.ABC.com) is not publicly resolvable from BC Cloud.

🔧 Solutions:

Expose NAV 2017 SOAP Service Securely Over the Internet:

Ensure NAV is hosted with a public DNS and valid SSL certificate (e.g., using a domain like navwstest.yourdomain.com).

Open port 7047 securely through your firewall or better, proxy it through port 443 (HTTPS).

Use Azure Services:

Set up Azure API Management, Azure Application Gateway, or Azure Relay/Hybrid Connection to expose NAV SOAP to BC Online.

This gives you extra security, throttling, and monitoring options

✅ Confirm if this resolves your issue, and mark it as verified if helpful.

Was this reply helpful? Yes No
Verified answer

DAnny3211 11,397 on at

Like (3)

Report
Hello,

Thank you for providing the details of your integration scenario.

The error message:

"There was an error while executing the HTTP request, error request: NameResolutionError. Make sure you are connecting to a valid endpoint."

suggests that Business Central Cloud is unable to resolve or reach the specified on-premises NAV SOAP endpoint. While the service works in Postman, the issue likely stems from network accessibility and DNS resolution limitations in the cloud environment.

Key Considerations and Recommendations:

Public Accessibility of the Endpoint
Business Central Cloud cannot access internal or private network addresses. Ensure that the NAV SOAP endpoint is:

Publicly accessible over the internet.

Secured with a valid SSL certificate (self-signed certificates are not supported in BC Cloud).

DNS Resolution
The domain navvsstest.ABC.com must be resolvable from the public internet. If it is an internal DNS name, BC Cloud will not be able to resolve it. Consider using a public DNS entry or exposing the service through a reverse proxy.

Firewall and Port Configuration
Ensure that port 7047 is open and accessible from external sources. You may need to configure your firewall or network gateway to allow inbound traffic to the NAV server.

Use of Azure Relay or API Gateway (Optional)
If exposing the NAV server directly is not feasible, consider using Azure Relay, Azure API Management, or a secure VPN tunnel to bridge the cloud-to-on-premises communication securely.

Authentication and Headers
Double-check that the authentication method used in Postman is replicated correctly in the BC Cloud HTTP request, including any required headers or credentials.

If this response helps resolve your issue, please consider marking it as accepted so it may assist others facing similar integration challenges.

Best regards.

Was this reply helpful? Yes No
Verified answer

Jeffrey Bulanadi 8,760 on at

Like (3)

Report
Hi,

The error you're seeing is a classic symptom of DNS or firewall restrictions when trying to connect from BC Cloud to an on-prem NAV SOAP endpoint.

The message:

“There was an error while executing the HTTP request, error request: NameResolutionError. Make sure you are connecting to a valid endpoint.”

means that BC SaaS cannot resolve the hostname navwstest.ABC.com to an IP address. This typically happens because:

The NAV server is hosted on a private network or VPN that’s not publicly accessible

The domain name is internal and not registered in public DNS

There’s no public-facing firewall rule or reverse proxy to expose the SOAP service externally

To resolve this:

Ensure the NAV server is reachable from the public internet. You’ll need to expose the SOAP service via a public IP or domain, ideally behind a secure reverse proxy.

Confirm that port 7047 is open and accessible externally. You may need to configure NAT or firewall rules to allow inbound traffic.

Use a fully qualified domain name (FQDN) that resolves via public DNS. If you’re using a custom domain, make sure it’s registered and points to the correct IP.

If the NAV server is behind a VPN or internal network, consider deploying a relay service or Azure-hosted proxy to bridge the connection.

Also, make sure the NAV SOAP service is configured to allow external access. You can verify this in the NAV Server Administration tool and test using Postman from an external network.

Helpful references:
Consume external NAV SOAP webservices from SaaS BC
Resolving Access Issues to OData and SOAP Services – Stoneridge Software
Walkthrough: Creating and Using a Codeunit Web Service (SOAP)
How to resolve NameResolutionFailure – Stack Overflow

If you find this helpful, feel free to mark this as the suggested or verified answer.

Cheers
Jeffrey

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 95,329 Super User 2025 Season 2 on at

Like (4)

Report

Hi, If you're using the BC Cloud version, the latest version is BC26.
SOAP is disabled by default.
Recommended APIs. Please use OData at least.

https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/upgrade/deprecated-features-platform?wt.mc_id=DX-MVP-5004336#changes-in-2026-release-wave-2-version-290

Changes in 2025 release wave 1 (version 26.0)

More details:

Dynamics 365 Business Central Blog Series: REST API web services (APIs)

https://yzhums.com/63801/

Thanks.

ZHU

Was this reply helpful? Yes No
Verified answer

Andrés Arias 4,188 Super User 2025 Season 2 on at

Like (3)

Report

Hello,

The error indicates that access is not possible. You need to make the SOAP service publicly accessible. I would recommend:

- Try publishing your SOAP service over HTTPS with a public domain.
- Use basic authentication (if possible with restricted IP).
- Or create an intermediate API in Azure that receives from BC and forwards to NAV or some other service.

I hope this helps.

Regards,

Andrés

Was this reply helpful? Yes No