Dear all,
Effective March 2, 2020, the regional Discovery Service is deprecated. Microsoft will continue to provide support, security, and other critical updates for the regional Discovery Service, but won't release any additional functionality beyond what has already been announced. After April 21, 2021, the regional Discovery Service will be shut down.
Customers must transition to using the global OData V4 Discovery Service before April 21, 2021 so their applications are not impacted. More information: Modify your code to use global Discovery Service.
Source of announcement:
Important changes (deprecations) coming in Power Apps, Power Automate and customer engagement apps - Power Platform | Microsoft Docs
Today we see an high influx of support requests after the service was stopped.
Unfortunately, the default configuration in the SDK redirected the URL validation to the global discoverability that requires OAUTH and does not support username/password. This causes the connection to fail for the supported releases that do not yet support OAUTH or OAUTH2.
OAUTH support has been made available in a later CU of Microsoft Dynamics 365 Business Central Spring 2019 Update on-premises.
OAUTH support will be made available in upcoming CU for Dynamics NAV 2018 (link). It will be released soon.
OAUTH support is not yet available in other supported releases of Dynamics NAV.
Short term a hotfix that will disable the call to global discoverability service.
Medium term enable oath for the supported releases (work is already started)
As we are aware of the issue and we are already working on it with high priority, there is no need to raise a support request about this issue. As a general suggestion, we recommend all customers to consider to upgrade to a supported release of Dynamics 365 Business Central and / or to ensure latest CU is already applied.
