# Steps to reproduce
1. I use a tool called rabtap to publish messages to rabbitMQ. Tool can be found here: https://github.com/jandelgado/rabtap
2. When I tap on an exchange and redirect output to a file.
-> It comes OK when I use this cmd on cmd prompt (i.e., as here): rabtap tap "myexchange:" --json > c:\tmp\usingCMDline.txt"
-> However if I redirect the output using powershell, I miss out the ending bracekt in the output file. rabtap tap "myexchange:" --json | Out-File "c:\tmp\ps02.txt" (see attached output)
# Expected behavior
Full JSON should output, as done by the cmd line redirect operator.

# Actual behavior
Miss out on the ending bracket.
More details on issues can be seen here: https://github.com/jandelgado/rabtap/issues/21

This looks like a bug on first sight but maybe there is a workaround that I am missing? Any idea why this is happening?

# Environment data

The first time New-NetLbfoTeam is used by Desired State Configuration it creates a misnamed interface.

This is on Server 2019 Build 17763.557 with the following updates applied:

KB4483452
KB4470788
KB4503308
KB4504369
KB4503327

Powershell shows:
Name Value
---- -----
PSVersion 5.1.17763.503
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.17763.503
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

For example:

New-NetLbfoTeam -Name "Team1" -TeamMembers "NIC1" -TeamNicName "Team1" -LoadBalancingAlgorithm Dynamic -TeamingMode SwitchIndependent -Confirm:$False

Will create an interface called "Ethernet" (Visible through Get-NetAdapter).

If you delete the team and recreate in the same DSC, it'll work correctly.

i.e. this works and creates an interface called "Team1"

$team1 = Get-NetLbfoTeam -Name "Team1" -ErrorAction SilentlyContinue;
$teamExists = [bool]($team1);
if(!($teamExists)) {
New-NetLbfoTeam -Name "Team1" -TeamMembers "NIC1" -TeamNicName "Team1" -LoadBalancingAlgorithm Dynamic -TeamingMode SwitchIndependent -Confirm:$False;
Remove-NetLbfoTeam -Name "Team1" -Confirm:$False;
New-NetLbfoTeam -Name "Team1" -TeamMembers "NIC1" -TeamNicName "Team1" -LoadBalancingAlgorithm Dynamic -TeamingMode SwitchIndependent -Confirm:$False;
}

Hey every body,

"New-AzVM" has a strange behaviour (maybe a bug), if you pass vn and subnet as parameters and
the vn exists but the subnet doesn't, it will try try to delete the vn (cascading) and recreate it. This
will fail if you have other VMs in the vnet but will succeed if you have empty subnets deleting all of them (OUCH!).

Steps to reproduce:

1. login to portal and create 1 vnet (say vnProd2 ) and 2 subnets (say snProd, snDev)
2. login to Azure from powershell (module AZ)
3. run the following command:
New-Azvm -Location "northeurope" -ResourceGroupName "rgTest" -virtualnetworkname vnProd2 -SubnetName "snProd101" -Image CentOS -Name linux06
In my head that command should create the new snProd101 since it doesn't exist, and it will, too bad it will recreate the vnet deleting the existent subnets snProd and snDev.