pac code add-data-source NOT WORKING

[PFSIzakovic]

Describe the bug

PS C:\CodeApps\Release-Manager-Pro> pac code add-data-source -a "shared_sharepointonline" -c "shared-sharepointonl-f8a749c6-a266-xxxx-xxx-xxxxxxx" -d "https://xxxxxxxxxxxx.sharepoint.com/sites/ORG00006318" -t "xxxxxxx-xxxx-xxxx-xxxxx-xxxxxxxxxxxxx"
Connected as matej.izakovic@porsche.sk
Error: Request failed: {}
at e. (c:\Users\xxxxxx\AppData\Roaming\Code\User\globalStorage\microsoft-isvexptools.powerplatform-vscode\pac\tools\powerapps-cli.js:2:14093)
at e. (c:\Users\xxxxxx\AppData\Roaming\Code\User\globalStorage\microsoft-isvexptools.powerplatform-vscode\pac\tools\powerapps-cli.js:2:7723)
at Generator. (c:\Users\xxxxxx\AppData\Roaming\Code\User\globalStorage\microsoft-isvexptools.powerplatform-vscode\pac\tools\powerapps-cli.js:2:10279)
at Generator.throw (c:\Users\xxxxxx\AppData\Roaming\Code\User\globalStorage\microsoft-isvexptools.powerplatform-vscode\pac\tools\powerapps-cli.js:2:11195)
at g (c:\Users\xxxxx\AppData\Roaming\Code\User\globalStorage\microsoft-isvexptools.powerplatform-vscode\pac\tools\powerapps-cli.js:2:11338)
at u (c:\Users\xxxxx\AppData\Roaming\Code\User\globalStorage\microsoft-isvexptools.powerplatform-vscode\pac\tools\powerapps-cli.js:2:11577)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)

Steps to Reproduce

see above

Expected behavior

Sharepoint list is added as a source

Actual behavior

Request failed

Screenshots or Error Messages

Environment information

• Framework, build tool or relevant package used: React,Vite
• Any connection/components: Sharepoint list

[jordanchodakWork]

[Microsoft Power Apps Product Manager]

Thank you for opening an issue. Which version of the PAC CLI are you using? You can see the version by typing 'pac'

The latest version is 1.49.4, which you can install with 'dotnet tool update --global Microsoft.PowerApps.CLI.Tool' or reference the documentation here.

[PFSIzakovic]

[Microsoft Power Apps Product Manager]

Thank you for opening an issue. Which version of the PAC CLI are you using? You can see the version by typing 'pac'

The latest version is 1.49.4, which you can install with 'dotnet tool update --global Microsoft.PowerApps.CLI.Tool' or reference the documentation here.

Microsoft PowerPlatform CLI
Version: 1.49.4+g406813e (.NET Framework 4.8.9310.0)
Online documentation: https://aka.ms/PowerPlatformCLI

[terbee15]

I also get this error and can't connect to my data sources. I'm using the latest PAC CLI.

[pavankm]

[Microsoft Power Apps Dev]

Based on our investigation into issues like these, these errors are typically not caused by a bug in the PAC CLI itself. Instead, they often point to environmental factors on the client-side that prevent the CLI from successfully authenticating or connecting to the data source endpoint.

Possible causes include:

• Network Security: Firewalls, proxies, or other network security components may be blocking the network calls made by the pac.exe process.
• Authentication Issues: The authentication context used by the CLI may not have sufficient permissions, or it may be affected by conditional access policies.

Troubleshooting Steps

To diagnose the root cause, please follow these steps:

1. Verify Permissions and Connectivity in the Browser

This step helps confirm that your user account has the correct permissions and that the data source is reachable from your machine.

• Open a web browser on the same machine where you are using the PAC CLI.
• Navigate directly to the data source you are trying to add (e.g., the SharePoint site or the Dataverse environment URL).
• Log in with the exact same credentials you used to authenticate with the PAC CLI (pac auth create).
• Result: If you cannot access the resource, there is likely a permissions issue with your user account. If you can access it, proceed to the next step.

2. Inspect Network Traffic with a Web Debugger

This is the most effective way to see the raw network communication between the PAC CLI and the data source endpoint.

• Download and install Fiddler Classic.
• Start Fiddler and ensure it is capturing traffic (go to File > Capture Traffic).
• In a command prompt, run the pac code add-data-source command that is failing.
• In the Fiddler session list, look for requests made to your data source endpoint (e.g., yourorg.crm.dynamics.com or yourtenant.sharepoint.com).
• Analyze the response:
  • A 200 status code indicates success.
  • A 401 (Unauthorized) or 403 (Forbidden) status code points to an authentication or permission issue.
  • Other error codes or a complete lack of response can indicate that a firewall or proxy is blocking the request.

By following these steps, you can determine whether the issue is related to network policies or authentication, which will help you and your IT department resolve the underlying problem.

[3DInspiron]

I've exactly the same issue; this is not even related to access/permissions or any company related setting.

Please fix it.

[RitvikChauhan1]

I am facing the same issue not able to connect to any data source in my code app.

[PFSIzakovic]

[Microsoft Power Apps Dev]

Based on our investigation into issues like these, these errors are typically not caused by a bug in the PAC CLI itself. Instead, they often point to environmental factors on the client-side that prevent the CLI from successfully authenticating or connecting to the data source endpoint.

Possible causes include:

• Network Security: Firewalls, proxies, or other network security components may be blocking the network calls made by the pac.exe process.
• Authentication Issues: The authentication context used by the CLI may not have sufficient permissions, or it may be affected by conditional access policies.

Troubleshooting Steps

To diagnose the root cause, please follow these steps:

1. Verify Permissions and Connectivity in the Browser

This step helps confirm that your user account has the correct permissions and that the data source is reachable from your machine.

• Open a web browser on the same machine where you are using the PAC CLI.
• Navigate directly to the data source you are trying to add (e.g., the SharePoint site or the Dataverse environment URL).
• Log in with the exact same credentials you used to authenticate with the PAC CLI (pac auth create).
• Result: If you cannot access the resource, there is likely a permissions issue with your user account. If you can access it, proceed to the next step.

2. Inspect Network Traffic with a Web Debugger

This is the most effective way to see the raw network communication between the PAC CLI and the data source endpoint.

• Download and install Fiddler Classic.

• Start Fiddler and ensure it is capturing traffic (go to File > Capture Traffic).

• In a command prompt, run the pac code add-data-source command that is failing.

• In the Fiddler session list, look for requests made to your data source endpoint (e.g., yourorg.crm.dynamics.com or yourtenant.sharepoint.com).

• Analyze the response:

  • A 200 status code indicates success.
  • A 401 (Unauthorized) or 403 (Forbidden) status code points to an authentication or permission issue.
  • Other error codes or a complete lack of response can indicate that a firewall or proxy is blocking the request.

By following these steps, you can determine whether the issue is related to network policies or authentication, which will help you and your IT department resolve the underlying problem.

There is nothing with permissions or firewalls. Please fix the bug as the entire Code App does not make any sense when only working with Dataverse.

[PFSIzakovic]

Sorry closed by mistake

[JonEricEubanks]

Any Updates on this Bug?

[pavankm]

We are investigating this issue right now.
We'll provide an update here when the fix starts rolling out.

In the meantime, Can we check that this line "region": "prod", is present in the power.config.json fles?
If not can we add this, and then attempt to add the data source

[JackBaxter722]

Hello @pavankm, I am able to add dataverse tables and get context, however, adding "region": "prod", did not fix the issue for SharePoint or Office 365 Users.

power.config.json:

{ "appId": "my-app-id", "appDisplayName": "my-app-name", "description": null, "environmentId": "my-env-id", "buildPath": "./dist", "buildEntryPoint": "index.html", "logoPath": "./public/vite.svg", "region": "prod", // Added "region": "prod", "localAppUrl": "http://localhost:3000/", "connectionReferences": {}, ...

package.json:

{ "name": "myappname", "private": true, "version": "0.0.0", "type": "module", "scripts": { "dev": "start pac code run && vite", "build": "tsc --noEmit --skipLibCheck && vite build", "lint": "eslint .", "preview": "vite preview", "start": "start pac code run" }, "devDependencies": { "@eslint/js": "^9.29.0", "@types/node": "^24.9.1", "@types/react": "^18.3.12", "@types/react-dom": "^18.3.5", "@vitejs/plugin-react": "^4.6.0", "eslint": "^9.29.0", "eslint-plugin-react-hooks": "^5.2.0", "eslint-plugin-react-refresh": "^0.4.20", "globals": "^16.2.0", "typescript": "~5.8.3", "typescript-eslint": "^8.34.1", "vite": "^7.0.0" }, "dependencies": { "@fluentui/react-charts": "^9.3.3", "@fluentui/react-components": "^9.72.2", "@fluentui/react-icons": "^2.0.312", "@microsoft/power-apps": "^0.3.21", "@types/react-router-dom": "^5.3.3", "clsx": "^2.1.1", "date-fns": "^4.1.0", "react": "^18.3.0", "react-dom": "^18.3.0", "react-router-dom": "^7.6.3", "wx-react-gantt": "^1.3.1" } }

Directory: C:\Users\my-user-id\CodeApps3\PowerAppsCodeAppsDemos\ProjectHub\ProjectHub\ProjectHub

Mode LastWriteTime Length Name

---

d----- 10/20/2025 7:58 PM .power
d----- 10/24/2025 2:21 PM dist
d----- 10/22/2025 7:03 PM node_modules
d----- 10/20/2025 7:58 PM public
d----- 10/22/2025 10:11 PM src
-a---- 10/20/2025 7:58 PM 373 .gitignore
-a---- 10/20/2025 7:58 PM 633 eslint.config.js
-a---- 10/21/2025 9:24 PM 333 fluentui-types.d.ts
-a---- 10/21/2025 9:45 PM 327 global.d.ts
-a---- 10/20/2025 7:58 PM 459 index.html
-a---- 10/22/2025 7:03 PM 232847 package-lock.json
-a---- 10/22/2025 7:03 PM 1150 package.json
-a---- 10/24/2025 2:19 PM 2013 power.config.json
-a---- 10/20/2025 7:58 PM 4158 setup-data-sources.ps1
-a---- 10/21/2025 9:46 PM 1074 tsconfig.app.json
-a---- 10/20/2025 7:58 PM 126 tsconfig.json
-a---- 10/20/2025 7:58 PM 655 tsconfig.node.json
-a---- 10/21/2025 9:22 PM 752 vite.config.ts

Output from terminal:

`PS C:\Users\my-user-id\CodeApps3\PowerAppsCodeAppsDemos\ProjectHub\ProjectHub\ProjectHub> pac code add-data-source -a "shared_office365users" -c "d55677c3074f4cb4acc87f568daf2895"
Connected as my-email@example.com
Error: Request failed: {}
at e. (c:\Users\my-user-id\AppData\Roaming\Code\User\globalStorage\microsoft-isvexptools.powerplatform-vscode\pac\tools\powerapps-cli.js:2:14093)
at e. (c:\Users\my-user-id\AppData\Roaming\Code\User\globalStorage\microsoft-isvexptools.powerplatform-vscode\pac\tools\powerapps-cli.js:2:7723)
at Generator. (c:\Users\my-user-id\AppData\Roaming\Code\User\globalStorage\microsoft-isvexptools.powerplatform-vscode\pac\tools\powerapps-cli.js:2:10279)
at Generator.throw (c:\Users\my-user-id\AppData\Roaming\Code\User\globalStorage\microsoft-isvexptools.powerplatform-vscode\pac\tools\powerapps-cli.js:2:11195)
at g (c:\Users\my-user-id\AppData\Roaming\Code\User\globalStorage\microsoft-isvexptools.powerplatform-vscode\pac\tools\powerapps-cli.js:2:11338)
at u (c:\Users\my-user-id\AppData\Roaming\Code\User\globalStorage\microsoft-isvexptools.powerplatform-vscode\pac\tools\powerapps-cli.js:2:11577)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)

PS C:\Users\my-user-id\CodeApps3\PowerAppsCodeAppsDemos\ProjectHub\ProjectHub\ProjectHub>`

Thank you,

[Cliveo]

I'm using the latest pac cli, 1.50.1. I can't add SQL or Office connections. With pac 1.49.4 and the prod region, I get the same as above.

02:15:32.908Z [INFO]}: [AddDataSource.Start] {
apiId: 'shared_office365users',
hasConnectionId: true,
hasConnectionRef: false,
hasSolutionId: false,
tableName: '',
dataset: '',
region: 'prod',
environmentName: 'zzz'
}
02:15:32.912Z [INFO]}: [AddDataSource.Path.Connector] {
apiId: 'shared_office365users',
tableName: '',
dataset: '',
sqlStoredProcedure: ''
}
02:15:32.913Z [INFO]}: [AddDataSource.ServiceCall.GetConnector.Start] { apiId: 'shared_office365users' }
02:15:33.873Z [INFO]}: [AddDataSource.ServiceCall.GetConnector.Failure] { apiId: 'shared_office365users', error: 'fetch failed' }
02:15:33.874Z [INFO]}: [AddDataSource.Failure] { dataSourceType: 'Connector', error: 'fetch failed' }
Error executing verb 'add-data-source': TypeError: fetch failed

==========================================================================

02:36:53.768Z [INFO]}: [AddDataSource.Start] {
apiId: 'shared_sql',
hasConnectionId: true,
hasConnectionRef: false,
hasSolutionId: false,
tableName: '',
dataset: 'xxx.database.windows.net,PowerPlatform',
region: 'prod',
environmentName: 'zzz'
}
02:36:53.774Z [INFO]}: [AddDataSource.Path.Connector] {
apiId: 'shared_sql',
tableName: '',
dataset: 'xxx.database.windows.net,PowerPlatform',
sqlStoredProcedure: '[dbo].[GetAllProjects]'
}
02:36:53.775Z [INFO]}: [AddDataSource.ServiceCall.GetConnector.Start] { apiId: 'shared_sql' }
02:36:54.332Z [INFO]}: [AddDataSource.ServiceCall.GetConnector.Failure] { apiId: 'shared_sql', error: 'fetch failed' }
02:36:54.333Z [INFO]}: [AddDataSource.Failure] { dataSourceType: 'Connector', error: 'fetch failed' }
Error executing verb 'add-data-source': TypeError: fetch failed