@jjonescz does this issue remain in branches that have migrated to use the 1ES pipeline templates❔ I am wondering whether SDL support in dotnet/arcade should be removed soon after the migrations wrap.

You're right. The SDL step is currently disabled/skipped in 1ES templates, so the issue doesn't occur there, or at least not in SDL step, but it might occur in other steps where artifacts are uploaded similarly (during migration I have tried rerunning the pipeline at various stages and it often failed with similar error although I haven't investigated more deeply). Also I think the SDL step should be re-enabled, see internal thread.

SDL scans should be used in conjunction with the Official 1ES PT. We will be removing SDL from Arcade as not to duplicate efforts between Arcade and 1ES PT.

Please reach out to 1ES PT support channel if you need help with it. https://teams.microsoft.com/l/channel/19%3A6d24d44587aa4d868bd4e96fe0eead31%40thread.tacv2/Support%20-%20General?groupId=886b1d22-e648-4492-af5f-6fbe81e73d4a&tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47

1ES PT conversions should be completed. SDL is not injected into pipelines via Arcade. Closing this issue.