That won’t give the desired behavior because it will wipe all the settings and only leave Bar. In this case I am pulling down the existing settings and modifying them with Bar which leaves the exiting settings in tact.

As for why we can’t just do the foreach passing in the site, it is because Get-AzureWebsite without a name returns only summary information including the site name, status, and uri. This is because the API call is cheaper. When you specify the site name it gets all the details.

Get-AzureWebsite | ForEach-Object -Process {
$site = Get-AzureWebsite $_.Name; $site.AppSettings["Bar"]=”Baz”;
Set-AzureWebsite $_.Name -AppSettings $site.AppSettings}

Just be this:
Get-AzureWebsite | Set-AzureWebsite -AppSettings @{ “Bar” = “Baz” }

I’m not 100% sure about that one, because I don’t have those cmdlets — but based on your syntax, I think that would work (you need to take advantage of the pipeline, not use ForEach-Object and create loops — loops are expensive, because you’re creating that cmdlet object every time, instead of just once) (P.S. where’s the download link? I installed the ones off github/WindowsAzure but it’s not there)

The next example (with Start-Job) definitely doesn’t need the foreach…