When deploying front door, if the front door already exists the assignment fails

[pbalexlear]

When deploying front door using a blueprint, if the front door already exists it fails every time due to Permissions
The artifact 'xxxx-xxxxx-xxxxxx-xxxxxx' of type 'Template' failed to deploy due to the following error: Template deployment failed with error [
{
"code": "Forbidden",
"message": "{\r\n "error": {\r\n "code": "AuthorizationFailed",\r\n "message": "The client 'xxxxx-xxxxxxxx-xxxxx-xxxxx' with object id 'xxxxxx-xxxxxxx-xxxxxx-xxxxx' does not have authorization to perform action 'Microsoft.Network/frontdoors/write' over scope '/subscriptions/00000-000000-0000000-000000/resourcegroups/{resourceGroup}/providers/Microsoft.Network/frontdoors/{frontdoorname} or the scope is invalid. If access was recently granted, please refresh your credentials."\r\n }\r\n}"
}
]

[alex-frankel]

does that front door exist in a different subscription than where the blueprint is being assigned? Are you using the system-assigned or user-assigned managed identity?

[pbalexlear]

Hello, no it doesn't, I've also noticed at the moment it seems to be on any resources that already exist, that were previous deployed using the same blueprint assignment, I'm using the system assigned identity.

[alex-frankel]

Hmm - if that's the case - this could be a larger issue. Are you able to open a support ticket so our engineering team can take a look?

[pbalexlear]

sure, a support ticket on Azure Portal?

[alex-frankel]

yep