This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(316.8, 2%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECB%3C/text%3E%3C/svg%3E)
I have deployed a based Blue Print but anytime I create another version with an update. I see that my new version is creating a duplicate policy that was created in the base blue print.
@Charlie Brown Thank you for reaching out, reviewing the scenario you are getting into and will share any learnings I might have at the earliest.
@Charlie Brown - To further investigate the issue , it might help can you please provide some additional information on your end to end scenario.
In case you are using an ARM template artifact in your Blueprint that defines the Azure Policy definition in the assigned Subscription. One possibility you can either tweak the ARM template so its smart enough not to replace the Azure Policy definition if it already exists (haven't tried this before) , or you could move the Policy out of the ARM template and define it by hand higher in the Management Group hierarchy and just have the Blueprint assign that policy definition.
Please share additional information on your scenario, so that we can help you further on this. Looking forward to hear from you.
open exisitng blueprint edit existing blue print
add artifact
publish blue print
name blueprint with version
Go to Assigned blueprints - Open the previous version blue print
Update Assignment and select updated blueprint
Select Assign