Application digitally signed with EV Certificate behaves differently when built in AzDO Pipeline

We have a desktop application that has historically been built on a local developer machine using Advanced Installer. When signing with the EV certificate it receives the value from Azure Key Vault without issue.

However, we have recently begun moving to an automated pipeline in Azure DevOps. We still use Advanced Installer in the pipeline and access the same certificate for signing. When the pipeline completes the EXE and MSI that are created get placed in a storage account.

However, the artifacts that are created in the pipeline trigger the Windows Defender Smart Screen warning, whereas, the locally built executables do not.

I was under the impression that the EV certificate would help prevent situations like this.

We are looking for a solution that prevents the Smart Screen from triggering on the pipeline builds, but are not sure on the best approach. Is the recommended approach to include the malware analysis scan and submission within the pipeline? And, if so, is there a delay between that process and the application being considered safe?