A subtle change in authentication to Dataverse in Dataverse DevTool

If you have been using Dataverse DevTools and went through adding a connection to your Dataverse environment and picked “Microsoft Login Prompt” as the authentication type you might have gone through the process where you need additional Global Admin approval for the app. This was because I was using my own AppId in Azure Entra that was creating an enterprise app request which as a process and for security reason needs a Global or Azure Admin permission to accept this new app.

Most of the times, people dont have the access to approve it themself and rely on their admin to approve which can get denied. So, I started looking into the connection logic; also reached out to one-and-only Scott Durow. He pointed me to his dataverse-auth repo which is open source as well. Looking into his code I realized the mistake I was preventing me from using Microsoft Dev App Id and kept throwing error when I did.

So, with some trial and error with the code I was able to fix it. Now I longer use the App Id I had created eliminating the need to get additional approval and uses Microsoft’s Dev App Id.

In case if you have deterred from the tool in past because it needed additional approval now is the time to try it again and lemme know how it goes.

There is no visual change in the authentication; just choose the regular “Microsoft Login Prompt” and that’s it! This would allow to connect to Dataverse for almost all environment and reduce the issues authenticating with Dataverse and simplifies working with DVDT overall.

Original Post https://powermaverick.dev/2025/03/21/a-subtle-change-in-authentication-to-dataverse-in-dataverse-devtool/