Showing results for 
Search instead for 
Did you mean: 
Helper III
Helper III

([Bad Request], The remote server returned an error: (400) Bad Request.), AX export encountered an error

Scenario: We currently have a system on Dynamic 365 Finance for Operation, and we want to connect PowerApps to transfer data from 365 to CDS. We followed this tutorial:


So far these are the steps that we did:

1. We created an entity in PowerApps with some fields that match the entity in 365


2. We created two connections for the PowerApps CDS and the Dynamic 365 For Fin & Op


3. In Admin Center -> Data Integration -> Connection sets, we created a new connection set that include the two connections above. 


4. Later on we created an integration project that use the above connection set 


5. We created a task 


6. Finally when we ran the project, we got the following error 


we did a quick search and found a similar article:


We tried to wait but it did not change anything, we still got the same problem. 

Community Support
Community Support

Hi @MinhPham96 ,

400 bad request generally comes when you can't access the resource.

Please check:
1)whether your firewall block this service

2)whether you have access to these two data source

3)whether your file is too large

Here's a blog about 400 bad request for your reference:


What's more, you could also try to clear your browser's cache.

If the problem still exists , I suggest you ask for help here:



Best regards,

Community Support Team _ Phoebe Liu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Helper III
Helper III

Dear @v-yutliu-msft , thank you for your response, we want to update some information based on your questions. 


1)whether your firewall block this service

Both the Dynamic 365 and PowerApps are stored on clouds and under the same organization. There should be no problem linking the two, if there is a possible firewall, can you give us some information ? 


2)whether you have access to these two data source

We used the admin account for this project and it has full access to the data source.


3)whether your file is too large

We just perform some data transfer between the entities, so no large file transfer or anything. 


Thank you and Regards

New Member

The 400 Bad Request error is an HTTP status code indicates that the request you sent to the webserver was malformed , in other words, the data stream sent by the client to the server didn't follow the rules. It means that the request itself has somehow incorrect or corrupted and the server couldn't understand it. The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method . Therefore, it prevents the website from being properly displayed. There are a number of different causes for a 400 Bad Request Error . It might be a malformed request syntax, invalid request message framing, or deceptive request routing . In most cases, the problem is on the website itself, and there's not much you can do about that. To fix a 400 Bad Request error it is best to start diagnosing the issue from the client side itself. Complete the steps outlined in this section to help diagnose and correct the error.


Check for errors in the URL.
Clear Browser Cache and cookies.
Clear DNS Cache.
Check your File upload Size.
Deactivate Browser Extensions.
Contact the site owner to report the 404 error.


New Member

Have you found resolution to this issue? Im having same problem at the moment.

I have admin rights, project is running timed and tried it manually (both gives same error). I have only one entity and not all fields from it.

Helpful resources

New Badges

New Solution Badges!

Check out our new profile badges recognizing authored solutions!

New Power Super Users


We are excited to announce the Power Apps Super Users!

Power Apps Community Call

Power Apps Community Call: February

Did you miss the call? Check out the Power Apps Community Call here.

Microsoft Ignite

Microsoft Ignite

Join digitally, March 2–4, 2021 to explore new tech that's ready to implement. Experience the keynote in mixed reality through AltspaceVR!

Users online (73,414)