Windows Defender blocks ports on Azure Cloud Service

Describe the issue
Hi all,
we have implemented the app based on the AudioVideoPlayback sample. Our app needs to sent data within the bot to outside service from 1688 port. Sometimes that port is blocking, therefore sending data will be stopped in that case.

I tried to use that PowerShell script on runtime after bot deploying to fix that issue:

Set-MpPreference -DisableRealtimeMonitoring $true
Set-MpPreference -DisableBehaviorMonitoring $true
Set-MpPreference -DisableScanningNetworkFiles $true
Set-MpPreference -DisableIntrusionPreventionSystem $true
Set-MpPreference -DisableScriptScanning $true

$rule = Get-NetFirewallRule -DisplayName "Allow Out 1688 TCP" 2> $null;
if (!$rule)
{
New-NetFirewallRule -DisplayName "Allow Out 1688 TCP" -Direction Outbound -LocalPort Any -RemotePort 1688 -Protocol TCP -Action Allow
}

$rule = Get-NetFirewallRule -DisplayName "Allow Out 1688 UDP" 2> $null;
if (!$rule)
{
New-NetFirewallRule -DisplayName "Allow Out 1688 UDP" -Direction Outbound -LocalPort Any -RemotePort 1688 -Protocol UDP -Action Allow
}

Set-NetFirewallProfile -Profile Domain,Public,Private -Enabled False

Get-Service -DisplayName "Windows Modules Installer" | Stop-Service

But that didn't help us. The sending data usually prevents in 3-5 hours after the call starts. Any ideas, please? This issue is stopping us from going to production.

Review the AudioVideoPlayback sample deployment and the runtime PowerShell commands, starting with outbound TCP and UDP traffic to remote port 1688. Reproduce the sending failure after the reported 3–5 hours and compare the deployed service behavior with the script’s changes. Done means the blocking cause and a verified remediation are identified.