Error:Blueprint resource group placeholder

Question

I am trying to assign a blueprint via az cmd but keep on getting the following error Error: 'Blueprint resource group placeholder " the artifact has been specified in the blueprint as io-default-vnet

example
az blueprint assignment create --name 'IO-Default-Network-Config-test' --location 'South Africa North' --subscription "[sub id]" --resource-group-value artifact_name="io-default-vnet" name="io-default-vnet" location="South Africa North" --blueprint-version "/providers/Microsoft.Management/managementGroups/IO-Management-Group/providers/Microsoft.Blueprint/blueprints/IO-Default-Network-Config" --parameters @Rebecca .json

any ideas why ?

Answer 1

Hi, thanks, below is the complete cmd and out of the error. Yes the resource group has been defined , see snip of all artifacts.

devuser@ad01e081df88:/tmp$ az blueprint assignment create --name 'IO-Default-Network-Config-test' --location 'South Africa North' --subscription "[sub id]" --resource-group-value artifact_name="io-default-vnet" name="io-default-vnet" location="South Africa North" --blueprint-version "/providers/Microsoft.Management/managementGroups/IO-Management-Group/providers/Microsoft.Blueprint/blueprints/IO-Default-Network-Config" --parameters @Rebecca .json
Command group 'blueprint' is experimental and not covered by customer support. Please use with discretion.
This assignment is invalid. Error: 'Blueprint resource group placeholder 'io-default-vnet' does not exist in blueprint '/providers/Microsoft.Management/managementGroups/IO-Management-Group/providers/Microsoft.Blueprint/blueprints/IO-Default-Network-Config/versions/1.4'.'

Answer 2

Thanks for sharing @D Ds . Let me investigate on my end to see if I can reproduce this issue. In the meantime, can you try with a new, diff RG (preferably with a shorter name) to see if the error persists. I should have an update in 24 hours.

Cheers.

Answer 3

Hi

Still getting the same error when shorting the RG.

Answer 4

Trying to rule out Az CLI cmds as the root cause. Can you retry the blueprint assignment via PowerShell instead?
Here's a sample PS cmd below for your reference.

New-AzBlueprintAssignment -Blueprint $blueprint -Name 'assignMyBlueprint' -AssignmentFile .\blueprintAssignment.json

I've reached out to the blueprint team for help with this. Hope to have an update by Monday. thanks for your patience.

Answer 5

I just encountered this same issue using powershell. It appeared to be because I'd defined the resource group location in both my blueprint.json and assignment.json files.

eg:

blueprint.json

  "resourceGroups": {
    "mainRG": {
      "location": "australiaeast",
      "dependsOn": []
    }
  }

assignment.json

  "resourceGroups": {
    "mainRG": {
      "name": "rg-myresourcegroup",
      "location": "australiaeast"
    }
  }