I'm encountering an error when attempting to use the HTTP with Microsoft Entra ID (preauthorized) connector in Copilot Studio to send a POST request.
The connector requires a File type value for the body parameter, but I cannot find any way to create a variable of this type in Copilot Studio.
To bypass this restriction, I created an action instead, this is how the input and output look like:
inputs:
- kind: ManualTaskInput
propertyName: method
value: POST
- kind: ManualTaskInput
propertyName: url
value: /api/v2/cortex/analyst/message
- kind: ManualTaskInput
propertyName: headers
value:
kind: ValueExpression
literalValue:
Accept: */*
Content-Type: application/json
- kind: ManualTaskInput
propertyName: body
value: |
{
"messages": [
{
"role": "user",
"content": [
{
"type": "text",
"text": "hi"
}
]
}
],
"semantic_model_file": "xxx"
}
outputs:
- propertyName: Response
Despite trying several variations of the body value, I consistently receive this error: The connector 'HTTP with Microsoft Entra ID (preauthorized)' returned an HTTP error with code 400. Error code: ConnectorRequestFailure. Conversation ID: xxx
The identical configuration works correctly in Power Automate
I suspect the issue might be related to either:
Incorrect body value formatting in Copilot Studio
This connector requiring a premium license in Power Automate (which might make it unavailable in Copilot Studio)
Any suggestions for resolving this issue? And is there a way to access more detailed error logs?
as you can see on the screenshot that you provided - connector actions in Copilot Studio are still in preview (you can read more about preview features here: https://copilottoday.posthaven.com/what-is-a-preview-feature-in-microsoft-products). That kind of formatting issues happen quite a lot for preview features - don't use it on production workload, only for testing. You should leverage Power Automate flow for the action that you want to perform.
In case of any other questions, let me know. If the answer helped you, mark it, so that others can benefit from it.
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.