30
It is currently possible to specify Windows, NavUserPassword or AAD in the launch.json file.
The problem is that the AAD option only works for Cloud deployments, not for on-premise.

That really lowers the advantages of using Azure Active Directory instead of Windows authentication, when working with an on-premise deployment. It practically means that the environment is not debugable...

So please look into enabling the AAD autentication option for on-premise deployments.
Category: Development
STATUS DETAILS
Needs Votes
Ideas Administrator

Thank you for this suggestion! Currently this is not on our roadmap. We are tracking this idea and if it gathers more votes and comments we will consider it in the future.

Best regards,
Business Central Team

Comments

E

We also need this when customer wants to only allow AAD authentication for all ports and services from the Internett to the on-prem server.

Category: Development

E

Fully agree! Additionally it would be very helpful to be able to publish to on-premises environment from VSCode using AAD auth. Currently we're running a second service instance using NavUserPassword authentication to be able to deploy new versions.

Category: Development