
Instead of using the built-in attachment field, host the file elsewhere (e.g., SharePoint) and provide a link in the approval description.
Example:
Upload your file to SharePoint in a known library.
Use Get file content and Create sharing link for a file or folder.
In the Approval Details field, put something like:
This method is fully supported and very reliable.
If you absolutely must embed attachments, consider switching to Teams Adaptive Cards approvals, where you can include:
Rich card content
Links
Even thumbnails
This approach requires building the card JSON and sending via Post an adaptive card and wait for response, but avoids the problematic backend entity.
If your business process requires official attachment support in the Approval connector:
Open a support ticket with Microsoft referencing:
Ask them to confirm whether your environment supports attachments.
If not, request provisioning or migration guidance.
Be prepared for them to tell you that attachment support is still in partial rollout.
If I have answered your question, please mark it as the preferred solution ✅ . If you like my response, please give it a Thumbs Up 👍.
Regards,
Riyaz