Check your eligibility for this 50% exam voucher offer and join us for free live learning sessions to get prepared for Exam DP-700.
Get StartedDon't miss out! 2025 Microsoft Fabric Community Conference, March 31 - April 2, Las Vegas, Nevada. Use code MSCUST for a $150 discount. Prices go up February 11th. Register now.
Hello,
I'm fairly new to using Fabric and I'm hoping I could pick your brains on something.
I'm trying to configure the Rest connector in Fabric copy data activity for Adobe Learning Manager but no luck. I've run it in Postman and I got 200 response code using Auth Type Bearer. Using Basic Auth in Postman is returning 401 response code.
However, Auth Type is not an option in Copy Data. I can select Anonymous, Basic, or Service Principal. Basically I selected anonymous and added Authorization Bearer <token> in the header but I can't get it to work. It's timing out. Any idea is appreciated.
Fabric
Solved! Go to Solution.
Hi @rasalhague
Authorization Header: Since you're using Bearer token authentication, ensure that you're correctly formatting the Authorization header. It should look like this:
Authorization: Bearer <your_token>
Make sure there are no extra spaces or characters.
Connection Type: Since the Copy Data activity in Fabric doesn't support Bearer token directly, using the Anonymous option and adding the Bearer token in the headers is a common workaround. However, ensure that you have set the headers correctly in the Additional headers section of the source configuration.
Timeout Settings: If you're experiencing timeouts, consider increasing the Request timeout setting in the advanced options of the Copy Data activity. The default is 1 minute and 40 seconds, but you can extend it to see if that resolves the issue.
Testing the Connection: Since you received a 200 response in Postman, double-check the exact URL and parameters you're using in Fabric. Ensure that the Relative URL is correctly appended to the base URL defined in your connection settings.
Make sure that Bearer tokens are valid and have no problems when tested in Postman.
Regards,
Nono Chen
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi @rasalhague
Authorization Header: Since you're using Bearer token authentication, ensure that you're correctly formatting the Authorization header. It should look like this:
Authorization: Bearer <your_token>
Make sure there are no extra spaces or characters.
Connection Type: Since the Copy Data activity in Fabric doesn't support Bearer token directly, using the Anonymous option and adding the Bearer token in the headers is a common workaround. However, ensure that you have set the headers correctly in the Additional headers section of the source configuration.
Timeout Settings: If you're experiencing timeouts, consider increasing the Request timeout setting in the advanced options of the Copy Data activity. The default is 1 minute and 40 seconds, but you can extend it to see if that resolves the issue.
Testing the Connection: Since you received a 200 response in Postman, double-check the exact URL and parameters you're using in Fabric. Ensure that the Relative URL is correctly appended to the base URL defined in your connection settings.
Make sure that Bearer tokens are valid and have no problems when tested in Postman.
Regards,
Nono Chen
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thanks, @v-nuoc-msft! Appreciate your help. Finally got it working using HTTP connector and following your advise. Also, added the domain in my base URL.
User | Count |
---|---|
7 | |
3 | |
2 | |
2 | |
1 |
User | Count |
---|---|
10 | |
9 | |
5 | |
3 | |
3 |