Forced lowercase tag names

[solstone]

Am I going crazy or does the 0.4.1008 version force the beginning of the name of a Azure resource tag to be lowercase.

For example I go to create a resource group with bicep and I pass it the resource group name and a hashtable for the tags.

$tagsObject = @{
Application = 'Cloud Arch Testing'
Criticality = 'Non Critical'
DeploymentState = 'Deploy'
Environment = 'DEV'
Organization = 'TestCorp'
}

When I go to check the resource group in Azure all the Tag names have had the first 2 letters turned to lowercase. Any other letter after that is unchanged.

environment
criticality
deploymentState
organization
application

Has anyone else seen this?

Thanks

[majastrz]

Can you share your Bicep file?

[solstone]

Here is the bicep file.

targetScope = 'subscription'

@description('Tags')
param tagsObject object

@description('The name of the Resource Group')
param resourceGroupName string

@description('The Azure region')
param location string = 'eastus'

resource resourceGroup 'Microsoft.Resources/resourceGroups@2021-04-01' = {
  name: resourceGroupName
  location: location
  tags: tagsObject
  properties: {}
}

[solstone]

So would this be considered a bug?

[brwilkinson]

Yes, most likely something with how the json is being parsed, within the powershell Cmdlet, that is used for the deployment.

I'll see if I can figure out why my AZ cli is not deploying, to see if it's a powershell only issue.

Those AZ powershell cmdlets, come from the AZ.resources module, which is actually on a different repo, so we will likely open an issue over there as a next step.

We recently opened an issue there for json outputs. I am not certain, if they changed the json libraries they are using at some stage. That issue is: Azure/azure-powershell#16523

[solstone]

I'm fairly certain I didn't see this until I updated to bicep 0.4.1008, but I honestly can't remember if I updated my Az module at the same time. I see that az 7.0 was just released, so I may update to that and see if I see the same results. Thanks for you help so far!

[brwilkinson]

okay, thanks for the update/info.

What is your current version of the az.resources module ?

get-module az.resources -ListAvailable

ModuleType Version    PreRelease Name                                PSEdition ExportedCommands
---------- -------    ---------- ----                                --------- ----------------
Manifest   4.3.8                 Az.Resources                        Core,Desk {Get-AzProviderO

looks like 5.1 is the latest so I'll do some more testing with the latest version etc. I think this is a PS issue, not Bicep issue, however will have to do more testing to confirm.

find-module az.resources -AllVersions

Version              Name                                Repository           Description
-------              ----                                ----------           -----------
5.1.0                Az.Resources                        PSGallery            Microsoft Azure

[solstone]

Looks like I am currently on 4.3.1.

ModuleType Version    PreRelease Name                                PSEdition ExportedCommands
---------- -------    ---------- ----                                --------- ----------------
Script     4.3.1                 Az.Resources                        Core,Desk {Get-AzProviderOperation, Remove-AzRoleAssignment, Get-AzRoleAssignment, New-AzRoleAssignment…}

[brwilkinson]

@BethanyZhou This is another query relating to deployments, however on inputs, this time.

• I haven't finished discovery, however since you were already reviewing New-AzDeployment and New-AzResourceGroupDeployment outputs string array not working azure-powershell#16523 I figured I might ask anyway.

As outlined above: The Deployment parameters, when they are an Object, the keys appear to be set to camel case after they are passed in.

The visual on this is above on #5365 (reply in thread)

I haven't opened an issue on azure/powershell yet, however wanted to check if you had any comment first?

[BethanyZhou]

I'm using Bicep v0.4.1008

This issue can be reproduced in Az.Resources 4.3.1 when passing in with PowerShell as dynamic parameter. I was unable to reproduce this issue in Az.Resources 5.1.0. @brwilkinson Could you help to double confirm this?

Checked the template json file generated by bicep, they are same. So maybe something special when passing parameter. I will continue investigate this issue.

Sorry for inconvenience. Please try to upgrade to our latest Az.Resources and have a try. @solstone

[BethanyZhou]

BTW, I tested Az.Resources >= 4.4.0, all of them are workable for this issue. There is no Az.Resources 4.3.8 in PowerShell Gallery. Where is your Az.Resources come from? @brwilkinson

[solstone]

Woot! Updated my AZ module to the latest and I am not see the issue anymore! Thanks everyone for work with me on this!

[brwilkinson]

Thanks @BethanyZhou much appreciated, thank you for testing that.

Looks like I listed out module 4.3.8 from a private preview feature.

Glad this was already resolved in the recent modules.