How to set an audioFile to a call queue correctly ?

Hi @Chartier-Boivin, Isaac, 

Based on what you've described, this seems to one of those cases where there is a discrepancy between standard PowerShell script guidance and actual service- or tenant-side behavior. 

When managing a Call Queue, the standard method is to import the audio file using Import-CsOnlineAudioFile -ApplicationId "HuntGroup" and then apply the returned ID to the appropriate Set-CsCallQueue parameter. Please note that Call Queue and Auto Attendant audio files often show MarkedForDeletion = True immediately after import, so that flag alone doesn't necessarily mean the file is invalid. 

Before opening a support ticket for further check, here are a few recommendations you can check first:

• Make sure the file is imported with -ApplicationId "HuntGroup" for Call Queue use.
•  
• Use the returned audio file ID directly in the correct Call Queue parameter, such as -MusicOnHoldAudioFileId or -WelcomeMusicAudioFileId. 
• If you intend to use the same source audio across multiple queues, a practical approach is to re-import the file for each specific queue and apply the newly generated ID. Technically, it does not explicitly confirm whether a single, previously imported HuntGroup audio object is guaranteed to remain reusable across multiple queues indefinitely. 

If the issue still continues after following the documented cmdlet pattern, then I would recommend opening a Microsoft 365 support ticket so a Teams support agent can review the behavior from the service side. While support may not help write or redesign a custom PowerShell script, they can help investigate whether the problem is related to tenant configuration, provisioning, or backend behavior when the documented workflow itself is not behaving as expected. 

If you do open a case, it will help to include: 

• the exact cmdlets used, 
• the exact error or unexpected result, 
• whether it happens with all queues or only certain ones, 
• whether a freshly imported audio file behaves differently from a reused ID, 
• and your Teams PowerShell module version. 

From the moderator side, I can provide guidance based on the information shared here, but I cannot access your tenant, test the commands in your environment, or verify backend behavior directly. If the issue continues after the documented checks above, a support ticket is the best next step for deeper investigation. 

• For detailed instructions on how to get support, please refer to Get support - Microsoft 365 admin.  
• In case you do not know who is your IT admin, kindly refer to this article: How do I find my Microsoft 365 admin? - Microsoft Support.

I hope this helps. Should you have any further questions, please feel free to let me know.

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.