Unable to send REST message using POST method to Azure APIM - Internal server errorIssue ServiceNow is posting attachment data in Base64Encoded string format in the payload along with other fields in an outbound REST call to Azure. The following exception is received in the response from Azure Post method exception in Azure response:{ "statusCode": 500, "message": "Internal server error", "activityId": "bc3139f7-83ee-48cd-9fec-653a07e78940" }CauseactivityId in the response from Azure indicated the POST call is received by them but for some reason, they were not able to process the request from ServiceNow. Enabling HTTP to debug on the instance will help capture the request and response headers along with the payload of the REST call From the response, we could see the below data "{Content-Length=111, Content-Type=application/json, Ocp-Apim-Trace-Location=https://apimstkuxa9ygoh28qxwbbx9.blob.core.windows.net/apiinspectorcontainer/4riBH1fo4u5kPKQZZQDyqg2-17?sv=2019-07-07&sr=b&sig=whhSO8HppAgTNrjr384A6HQuzi%2BTXBlQhAlIddvv1Pg%3D&se=2020-12-16T11%3A16%3A53Z&sp=r&traceId=4a4ce11f4aab433988ee68a0918a5f77, Date=Tue, 15 Dec 2020 11:16:52 GMT}" If you open the link for the field "Ocp-Apim-Trace-Location" in the response, the cause of the issue will most likely be related to the authentication and certificates in the Azure portal. Ocp-Apim-Trace is a kind of Trace that can be enabled at Azure to know any errors in the REST transaction More information on this trace: Ocp-Apim-Trace In this context, here is the exception reported by the above trace from the link in response "<Error> <Code>AuthenticationFailed</Code> <Message>Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature. RequestId:6d16f979-601e-00a1-5fff-d5389c000000 Time:2020-12-19T12:08:26.7712943Z</Message> <AuthenticationErrorDetail>Signed expiry time [Wed, 16 Dec 2020 11:16:53 GMT] must be after signed start time [Sat, 19 Dec 2020 12:08:26 GMT]</AuthenticationErrorDetail> </Error>" ResolutionThe issue is with the Azure certificate and authentication. This needs to be fixed by Azure at their end based on the exception populated in the Ocp-Apim-Trace field in the REST response to instance