Small and medium business | Business Central, N...

v26 System.Hyperlink(url) for non-public (local) sites

(6) Share

Report

Posted on by CG-29052127-0

In BC SaaS v25, we were able to open URLs to our non-public (local) sites using the System.Hyperlink(url) method.

However, after upgrading to version 26, this functionality no longer works.
We’ve confirmed that the feature Enable server certificate validation for HTTP requests is currently disabled, which may be contributing to the issue.

While our public-facing portals continue to operate as expected, we rely on access to internal sites for testing and development purposes.

Please advise whether this behavior is expected in v26? If so, are there recommended alternatives or workarounds for accessing internal URLs from within Business Central?

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (9)

Answers (0)

Suggested answer

YUN ZHU 99,086 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Hi, I did a simple test and didn't encounter your problem, because HyperLink opens a new tab. Is there any new restriction on your browser or company?

Thanks.

ZHU

Was this reply helpful? Yes No
CU21051319-0 10 on at

Like (3)

Report
Copy link

Link copied!

Hi,

I have update my production enviroment tonight, and all my links to internal URLs are not working.

I have all my links using the standar link section on the right box of the item page.

Its like BC are trying to verify first the link, but if you link and internet URL or just a wrong URL, does nothing.

Any solution?

Was this reply helpful? Yes No
Suggested answer

RockwithNav 8,959 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

I understand your pain area but afaik, this has nothing do with the Hyperlink.

Hyperlink will anyway open a new tab to redirect your link.\

Blog - rockwithnav.wordpress.com/
Twitter - https://twitter.com/RockwithNav
Facebook - https://facebook.com/rockwithnav/

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 99,086 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

PS: Dynamics 365 Business Central: Using Hyperlink() Method to open a URL in a current session without opening a new tab in the browser

https://yzhums.com/29051/

Thanks.

ZHU

Was this reply helpful? Yes No
Gerardo Rentería Ga... 25,555 Most Valuable Professional on at

Like (3)

Report
Copy link

Link copied!

Hi, good day
I hope this can help you, and give you some hints.

Viva Engage : Dynamics 365 Business Central Partner Community (Formerly: Development) : Ver conversación

Best Regards
Gerardo

Was this reply helpful? Yes No
CU09071338-0 42 on at

Like (3)

Report
Copy link

Link copied!

We have the same problem. Internal websites cannot be opened via the “Links” fact box. Is there a solution for this?

Was this reply helpful? Yes No
Gerardo Rentería Ga... 25,555 Most Valuable Professional on at

Like (3)

Report
Copy link

Link copied!

Hi, good day
I hope this can help you, and give you some hints.

System.Hyperlink(Text) Method - Business Central | Microsoft Learn

Best Regards
Gerardo

Was this reply helpful? Yes No
AN-01071315-0 23 on at

Like (2)

Report
Copy link

Link copied!

We have the same issue. Our partners raised a case with Microsoft, they came back with the following comments -

"I understand that a customized link no longer works after upgrading to Business Central version 26.0

I apologize for the inconvenience, however, due to recent security enhancements, hyperlinks pointing to internal, on-premises systems (e.g., https://internalsystemhostname.clientdomain.com) no longer function when triggered from cloud-based environments. This impacts Business Central users who rely on the System.Hyperlink(Text) method to access internal case management systems.

The root cause is that internal-only DNS entries are not resolvable from the cloud, and the new security model enforces stricter validation, blocking such links from executing silently.

The recommended solution is to configure a public DNS record for the internal system, which would make the URL resolvable from the cloud and restore hyperlink functionality."

Unfortunately, creating a public DNS record to an internal system poses it's own security issues and we are uncomfortable in doing this. With this additional information, can anyone suggest another way around the issue?

Was this reply helpful? Yes No
Suggested answer

Jeffrey Bulanadi 9,112 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!
Hi,

The shift in behavior post-v26 has caught many off guard, especially those relying on internal URLs for dev and QA workflows. While System.Hyperlink(url) still works for public-facing links, local or non-public URLs are now subject to stricter browser and runtime constraints.

Here’s what’s likely happening:

In BC SaaS v26, the runtime environment enforces stricter browser security policies, especially around mixed content and local file access.

Even with server certificate validation disabled, the browser may block attempts to open http://localhost or file:// links from within the BC web client.

This behavior aligns with modern browser standards — hyperlinks to local resources are often blocked unless explicitly whitelisted or opened manually.

To work around this:

Consider using a WebPageViewer control add-in to embed internal content directly within BC. This bypasses the browser’s tab-opening logic and renders the page inline.

Alternatively, create a custom page that stores the internal URL and opens it via a trusted iframe or redirect logic — though this may still be blocked depending on CSP headers.

For testing purposes, you can expose internal sites via a secure tunnel (e.g., ngrok or Azure Relay) and use HTTPS endpoints that pass browser validation.

Helpful References
System.Hyperlink Method – Microsoft Learn
WebPageViewer Add-in Example – Dynamics 365 Lab

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

Cheers
Jeffrey

Was this reply helpful? Yes No