As of two days ago, my Add Attachment (Enterprise) step stopped working. No other components of this connecter are affected (e.g., Query Attachment, Delete Attachment, Update a record in a feature layer, etc.).
I get a generic 403 error:
{
"statusCode": 403,
"headers": {
"x-ms-environment-id": "",
"x-ms-tenant-id": "",
"x-ms-dlp-re": "-|-",
"x-ms-dlp-gu": "-|-",
"x-ms-dlp-ef": "-|-/-|-|-|-",
"x-ms-mip-sl": "-|-|-|-",
"x-ms-au-creator-id": "",
"Timing-Allow-Origin": "*",
"x-ms-apihub-cached-response": "true",
"x-ms-apihub-obo": "false",
"Date": "Fri, 22 May 2026 14:28:55 GMT",
"Content-Length": "380",
"Content-Type": "application/json"
},
"body": {
"error": {
"code": 403,
"source": "flow-apim-msmanaged-na-westus-01.azure-apim.net",
"clientRequestId": "d18b0a66-cc9c-4261-874a-97325cbaeac2",
"message": "The response is not in a JSON format.",
"innerError": "<html>\r\n<head><title>403 Forbidden</title></head>\r\n<body>\r\n<center><h1>403 Forbidden</h1></center>\r\n</body>\r\n</html>\r\n"
}
}
}According to my IT, they had an issue two days ago (same time as this error suddenly started) which affected email scanning. I also opened an Esri Support case (ID 04181279) and their assessment was (basically) "MS issue". So far, our best guess is something changed on MS's end, we just aren't sure what.
I have confirmed that using the REST endpoint to add attachments still works, but this of course requires a token to be generated every one hour to two weeks (depending on what you choose). This is my temporary workaround.
Has anyone else encountered this or have any suggestions?
Current plan is to open a MS support case (sigh) and see what they say.
