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

Added "GlobalEndPoints, The Webservice can not access

(7) Share

Report

Posted on by JZ-17110702-0

To allow mobile devices to access MARS, we added "GlobalEndPoints" in the web Settings: Null, "ms: / / businesscentral, ms: / / dynamicsnav", but the error 403 page displays the page could not be found.

RE EXTERNAL RE EX...

Categories:

Microsoft Dynamics NAV

Dynamics 365 Business Central

I have the same question (0)

All responses (6)

Answers (0)

Suggested answer

Pallavi Phade 5,292 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!

Namaste @JZ-17110702-0

I have not come across this issue in mobile. But based on sources can suggest

Fix the GlobalEndpoints value (no spaces, exact names).

Make sure the Web Server is reachable over HTTPS from the mobile device

Clear Mobile app and device cache; reinstall if needed.

Check Authentication and URLs

Check logs for the actual 403 reason -IIS logs

HTTPS / certificate not trusted by mobile device.

firewall blocking

wrong instance ( Wrong Nodes)

Regards

Pallavi Phade

1 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

Jainam M. Kothari 15,666 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hello,

The 403 error after adding GlobalEndPoints for MARS mobile access usually happens due to incomplete or incorrect configuration in navsettings.json, SSL issues, or authentication conflicts (especially with ACS/AAD on older on-prem setups).

Ensure your syntax matches Microsoft’s example, SSL is properly configured, and update to the latest cumulative update if using ACS/AAD. For SaaS, verify endpoint handling and raise a support ticket if the issue persists.

https://learn.microsoft.com/en-us/dynamics365/business-central/dev-itpro/deployment/install-business-central-app

1 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 97,970 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

As mentioned in the email, are there more error messages in the Event Log?

Thanks

ZHU

Was this reply helpful? Yes No
Suggested answer

OussamaSabbouh 10,972 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hello,

Your GlobalEndPoints entry is incorrect — it must use the official BC mobile URI schemes. Use this:

ms-businesscentral:;ms-dynamicsnav:

Wrong formats (spaces, slashes, “ms://…”) cause a 403 because BC rejects the endpoint.

Fix the value → restart IIS → mobile access works.

Regards,
Oussama Sabbouh

1 people found this reply helpful.

Was this reply helpful? Yes No
JZ-17110702-0 19 on at

Like (1)

Report
Copy link

Link copied!

The root cause found in https://community.dynamics.com/forums/thread/details/?threadid=d2f2ba9d-2448-4437-9a2c-6c33153e5cb6

Was this reply helpful? Yes No
Suggested answer

Chen M. 5 on at

Like (1)

Report
Copy link

Link copied!

This is a known issue that affects all BC versions prior to 17.0.
To resolve it, you need to install the latest CU or upgrade the entire BC platform to version 17.0+.

For more details, refer to the article shared by a Microsoft engineer in the comment section:

https://community.dynamics.com/forums/thread/details/?threadid=d2f2ba9d-2448-4437-9a2c-6c33153e5cb6

Fix: We have now identified an issue in older versions of BC and are fixing this in the next CU. Issue only happens on-premises when authentication is ACS and only when admin added the GlobalEndPoints parameter … and it is unrelated to the mobile app itself. The fix we have identified is in the web server code not in the mobile app - hence it’s being fixed as part of the next CU in the coming week. Important - this issue is not present in 17.0 on-premises, only in BC16 and below. We will backport this fix to all versions down to 14.

Was this reply helpful? Yes No