I have a flow using the "When a HTTP request is received" connector and it is working fine with the new trigger URL since being notified by Microsoft in September 2025. On 14 November 2025, all my HTTP POST requests were sent but failed to trigger the flow.
"Who can trigger the flow?" has been set to "Anyone". I have been using the x-api-key header for authentication using "equals(triggerOutputs()['headers']['x-api-key'],'my-api-key-here') in the trigger condition before 14 November 2025 and it works fine but I am now receiving this error instead:
{"error":{"code":"InvalidTemplate","message":"The template language expression evaluation failed: 'The template language expression 'equals(triggerOutputs()['headers']['x-api-key'],'my-api-key-here')' cannot be evaluated because property 'x-api-key' doesn't exist, available properties are 'Accept, Accept-Encoding, Host, Max-Forwards, User-Agent, x-real-ip, X-Original-Proto, x-ms-origin-endpoint, X-Original-Host, x-ms-igw-external-uri, x-ms-gw-trace-id, x-ms-igw-raw-target, x-ms-correlation-id, x-ms-coreframework-caller-activity-id, X-Original-For, x-ms-ppapi-forwarded-path, x-ms-ppapi-forwarded-api-version, x-ms-gateway-clusters, X-Forwarded-Prefix, Forwarded, x-ms-activity-vector, X-ARR-LOG-ID, CLIENT-IP, DISGUISED-HOST, X-SITE-DEPLOYMENT-ID, WAS-DEFAULT-HOSTNAME, X-Forwarded-Proto, X-AppService-Proto, X-ARR-SSL, X-Forwarded-TlsVersion, X-Forwarded-For, X-Original-URL, X-WAWS-Unencoded-URL, Content-Length, Content-Type'. Please see https://aka.ms/logicexpressions for usage details.'."}}
I did not make any changes to the flow and I can confirm that there were no changes made to the authentication headers in the HTTP POST. However, when I remove the trigger condition from the connector and do a HTTP POST without the authentication header the trigger works. Has anything changed in the way the trigger recognizes authentication headers?
