Error:Blueprint resource group placeholder

D Ds 6 Reputation points
2020-07-29T18:29:15.06+00:00

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 ?

Azure Blueprints
Azure Blueprints
An Azure service that provides templates for quick, repeatable creation of fully governed cloud subscriptions.
72 questions
{count} vote

5 answers

Sort by: Most helpful
  1. D Ds 6 Reputation points
    2020-07-30T05:13:37.527+00:00

    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'.'

    14454-image.png

    0 comments No comments

  2. olufemia-MSFT 2,861 Reputation points
    2020-07-31T07:54:33.873+00:00

    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.

    0 comments No comments

  3. D Ds 6 Reputation points
    2020-07-31T12:39:45.68+00:00

    Hi

    Still getting the same error when shorting the RG.
    14903-image.png

    0 comments No comments

  4. olufemia-MSFT 2,861 Reputation points
    2020-08-01T02:25:09.653+00:00

    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.

    0 comments No comments

  5. Drew 11 Reputation points
    2020-08-02T22:59:31.607+00:00

    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"
        }
      }
    

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.