Merge pull request #187561 from andrewbrownmsft/andbrown020422

Adding anti-malware messaging

Author: PRMerger18

articles/iot-hub-device-update/device-update-error-codes.md

@@ -60,5 +60,7 @@ The following table lists error codes pertaining to the content service componen
 | "UpdateVersionCompatibility"  | Cannot import additional update version with the specified compatibility.  | Same as for UpdateProviderCompatibility.ContentLimitNamespaceCompatibility. |
 | "CannotProcessUpdateFile"     | Error processing source file.                                              |                                    |
 | "ContentFileCannotDownload"   | Cannot download source file.                                               | Check to make sure the URL for the update file(s) is still valid. |
+| "SourceFileMalwareDetected"   | A known malware signature was detected in a file being imported.                                             | Content imported into Device Update for IoT Hub is scanned for malware by several different mechanisms. If a known malware signature is identified, the import will fail and a unique error message will be returned. The error message contains the description of the malware signature, and a file hash for each file where the signature was detected. You can use the file hash to find the exact file being flagged, and use the description of the malware signature to check that file for malware. <br><br>Once you have removed the malware from any files being imported, you can start the import process again. |
+| "SourceFilePendingMalwareAnalysis"   | A signature was detected in a file being imported that may indicate malware is present.                                             | Content imported into Device Update for IoT Hub is scanned for malware by several different mechanisms. If a signature is identified that is not an exact match for known malware, but has characteristics of malware, the import will fail and a unique error message will be returned. The error message contains the description of the suspected malware signature, and a file hash for each file where the signature was detected. You can use the file hash to find the exact file being flagged, and use the description of the malware signature to check that file for malware. <br><br>Once you have removed the malware from any files being imported, you can start the import process again. If you are certain your files are free of malware and continue to see this error, use the [Contact Microsoft Support](troubleshoot-device-update.md#contact) process. |
 
 **[Next Step: Troubleshoot issues with Device Update](.\troubleshoot-device-update.md)**