Export-QuarantineMessage Fail: Undocumented Parameter Dependency between ReasonForExport and CompressOutput

Question

Hello,

I am encountering an undocumented behavior with the Export-QuarantineMessage cmdlet in the Exchange Online PowerShell module (V3).

The Issue: According to the official Microsoft documentation, both -ReasonForExport and -CompressOutput are listed as optional parameters. However, I have discovered a hard dependency where the cmdlet fails if a reason is provided without the compression switch set to true.

When running the command with only the ReasonForExport ( parameter:

The command fails with the following error:

"Cannot process command because of missing mandatory parameters: CompressOutput."

Expected Result: The command should execute successfully, as neither parameter is marked as mandatory in the cmdlet definition or documentation.

If I add -CompressOutput $false, the commands give the same error.
If I add -CompressOutput $true, the command works as expected.

Questions :

Is this a known design requirement where metadata (Reason) can only be exported within a compressed archive?

• Are there other undocumented parameter dependencies for this cmdlet that we should be aware of for automation purposes?

Thank you for your assistance.

Answer 1

Hi @Niv BenSalmon 

Thanks for reaching out to the Microsoft Q&A forum.

I tried to replicate the situation in my environment, and here’s what I’ve observed so far: 

When running Export-QuarantineMessage with only the –ReasonForExport parameter, I received the same response you described. 

After adding –CompressOutput, the command executed successfully.

However, when I specified a value for -CompressOutput, I encountered an error indicating that this parameter does not accept explicit values.  

This aligns with the official documentation: Export-QuarantineMessage (ExchangePowerShell) | Microsoft Learn 

 Based on this, the behavior seems slightly different from what I understood from your description. Could you confirm if the same situation occurs in your environment? 

During my research, I couldn’t find any official documentation stating that –CompressOutput is required when using –ReasonForExport. Additionally, through testing, I discovered that –CompressOutput is also required when using –PasswordV2. 

That said, aside from my findings regarding –PasswordV2, if your environment does not behave the same way as mine, I recommend raising a support ticket with the Microsoft Support team through the Microsoft Admin Center for deeper assistance. 

I hope this provides additional insight. If you have any updates or further questions, please feel free to reach out.

---

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.