Signed installer receives an uncommon-download warning

Question

We publish a Windows application signed through Microsoft Artifact Signing. Authenticode verification succeeds and displays the expected publisher, but Microsoft Edge still shows an uncommon-download warning. How can a publisher distinguish ordinary new-file reputation from a publisher-identity mapping issue, and which official support or assessment route applies? No installer, download link, credentials, private build details, screenshots, or diagnostic logs are attached. We are not requesting a warning bypass.