Power Platform Community Forum Thread Details

Dataverse Virtual Tables + SQL (Service Principal): the steps that actually work

TL;DR: The Virtual Table wizard won’t let you pick a SQL connection that uses a Service Principal (even if you created it). It also doesn’t become selectable after creating a new SPN connection from inside the wizard. The workaround is to author with a user (Entra ID) connection, then switch the connection reference to the SPN and share it with Virtual Connector Provider.

The steps

Create the VT with a user (Entra ID) SQL connection using the Virtual Table wizard.

Why: the wizard doesn’t list the SPN SQL connection as a selectable option—even if you created it, and even if you add a new SPN connection from within the wizard and refresh.

Repoint the connection reference to the SPN connection.

In your solution, open the connection reference used by the VT and change it to the SQL connection that uses your Service Principal.

Share the SPN SQL connection with Virtual Connector Provider → “Can use”.

Go to Connections → your SQL (SPN) connection → Share, add Virtual Connector Provider with role “Can use”. This unblocks Web API calls because the VT runtime needs permission to use that connection server-side.

Test the Web API.

Call GET https://<org>.crm.dynamics.com/api/data/v9.2/<entityset>?$top=1 with your normal user token. No special SPN token is required

Why this flow

The wizard currently won’t surface SPN connections as selectable, so you can’t author the VT with SPN directly.
After creation, switching the connection reference to SPN and sharing it with Virtual Connector Provider makes both model-driven app and Web API work consistently.