web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Small and medium business | Business Central, N... / ODataV4 access in BC m...
Small and medium business | Business Central, N...
Answered

ODataV4 access in BC multitenant environment

(0) ShareShare
ReportReport
Posted on by Artis123 5

Hello,

I have multitenant BC 18 environment. OData services are enabled - all of them, also SSL. I am able to connect to domainname:7048/.../, but not able to domainname:7048/.../. Error: HTTP Error 503. The service is unavailable. As I said - both are enabled - V3 and V4. Basic auth is used.

Strange thing I see in event viewer - SSL/HTTPS has not been configured for ODataV4 Services; client credentials will be sent over an unsecured transport (HTTP).

And as I said, SSL is on. And I can get to V3 with HTTPS.

SOAP is working fine.

Base URL set in instance configuration: domain:7048/.../

Have tried also domain:7048/.../

It looks it only effects URLs showing up under Web services in BC. Does not make any effect if set incorrectly. If you know how URL should be, you will be able to open it anyway manually.

Another strange thing - in all MS articles and forums about multitenant OData access all URLs mentioned are containing only /OData/. None have /ODataV4/. Leading me to think - is ODataV4 even possible to configure in multitenant? 

I have the same question (0)
  • Suggested answer
    Marco Mels Profile Picture
    Marco Mels on at

    Hello,

    Recommendation is to enable rewrite rule for tenant name resolution within IIS so that you use an alternate host name per tenant. E.g. tenant1.domain.com:port/.../ODataV4, etc. That usually works fine. It will also enable edit in excel in a multi tenant environment.

    Thank you.

  • Artis123 Profile Picture
    Artis123 5 on at

    Thank you for reply! I tried alternate tenant IDs, but odatav4 was still not accessible. I ended up recreating everything from zero and it works now. Have no idea where exactly the problem was.

  • Verified answer
    Marco Mels Profile Picture
    Marco Mels on at

    Hello,

    Usually, the old cert is being used and the way to get a new cert to work is to disable all services that did have SSL configured and also disable the SSL properties, etc. Then restart, stop the service again and enable them again.

    Here you mentioned that ODataV3 still worked, which is indeed weird.

    Glad that you were able to resolve it.

    Thank you.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Congratulations to the November Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Small and medium business | Business Central, NAV, RMS

#1
OussamaSabbouh Profile Picture

OussamaSabbouh 2,066

#2
YUN ZHU Profile Picture

YUN ZHU 658 Super User 2025 Season 2

#3
Sumit Singh Profile Picture

Sumit Singh 595

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans