Use Azure AD Authentication for Business Central On-Premises Installations

In addition to using Windows and NavUserPassword authentication, you can use Azure AD to authenticate and publish in on-premises installations and containers from Visual Studio Code. Using Azure AD makes it possible to mimic application lifecycle operations in an on-premises environment, while keeping the cloud-based Azure AD authentication.

To enable Azure AD authentication, make sure to do as follows:

• Use the primaryTenantDomain setting in the launch.json file to specify the URL of the Azure AD organization or company associated with the Azure AD tenant. For more information, see Find tenant ID, domain name, user object ID and JSON Files.
• On the NST, you must ensure that the server is set up to use Azure AD as authentication mechanism. For more information, see User Authentication with Azure AD for Single Sign-on.
• Furthermore, if the Allowed Extension Target Level setting is set to Cloud, the server setting ForceExtensionAllowedTargetLevel must be set to true. If the Allowed Extension Target Level setting is set to OnPrem, it isn't necessary to set ForceExtensionAllowedTargetLevel. For more information, see Microsoft Dynamics 365 Business Central Server Configuration.

See also

JSON Files
User Authentication with Azure AD for Single Sign-on
Find tenant ID, domain name, user object ID