Trying to add Front Door to a brand new blob storage account, I get: "Property EnforceMtls is not allowed to set in current API Version"

Question

Trying to add Front Door to a brand new blob storage account, I get: "Property EnforceMtls is not allowed to set in current API Version"

Thomas Boutell 45

It's the strangest thing - I set up a brand new blob storage account, create a container, and click to create a matching Front Door, and the deployment starts, but eventually fails with the above error.

I'm using all default settings. I have no idea what to make of the advice that I should use a different API version because, again, this is a brand new blob storage account and Microsoft decides what APIs are involved in that. I assume!

Has anyone else seen this issue?

G Sree Vidya 4,005 Reputation points Microsoft External Staff Moderator

2025-07-15T19:31:33.45+00:00

Hi Thomas Boutell

I am following up to see if you have checked the answer below. Please let me know if you need further assistance.

please don’t forget to close the thread by clicking Accept the answer wherever the information provided helps you, as this can be beneficial to other community members.

2 answers

Your answer

G Sree Vidya 4,005 Reputation points Microsoft External Staff Moderator

2025-07-15T19:31:33.45+00:00

Hi Thomas Boutell

I am following up to see if you have checked the answer below. Please let me know if you need further assistance.

please don’t forget to close the thread by clicking Accept the answer wherever the information provided helps you, as this can be beneficial to other community members.

Answer 1

Daniel Tarabocchia 50

Hi all. I was having the same issue while trying to deploy Front Door Standard to a brand new storage account through the Azure portal. They way I resolved it was to let the initial deployment fail. When the result pane comes up showing the failure, there is an option to re-run the deployment. When you select this option, it gives you the ability to edit the deployment template. I edited the template and removed "enforceMtls" from the properties section of the JSON and saved it.

"properties": {

...

"enforceMtls": "Disabled",

...

}

Upon re-running the deployment with the updated template, the deployment succeeded.

ross baker 0 Reputation points

2025-08-07T12:57:49.1866667+00:00

Daniel thanks that worked for me too on a premium afd. Ms advise the following - redeploy with a stable version via ARM template, for example using ver. 2022-05-01.

This is currently expected behaviour due to the release version including schema validations that are not compatible with storage accounts and other backends but there's no documentation from Microsoft highlighting this as of yet, I would expect this to appear when the version enters General Availability (GA)

Answer 2

G Sree Vidya 4,005 Microsoft External Staff Moderator

Hello Thomas Boutell

The error "Property EnforceMtls is not allowed to set in current API Version" when adding Azure Front Door to a new Blob Storage account indicates an issue with the API version used in the deployment, but the API version used (e.g., an older version like 2020-05-01) does not support this property. Newer API versions (e.g., 2023-05-01 or later) may handle or exclude EnforceMtls differently.

Since you mentioned using all default settings, ensure that your blob storage account was created with the correct settings for compatibility with Front Door.

If the API version is outdated (e.g., pre-2023), try deploying Front Door using a newer API version via Azure CLI, PowerShell, or a custom Bicep/ARM template

You can check the versioning settings and configure the Minimum TLS version if necessary.

You might need to set the blob service properties to an earlier version manually using the Azure Storage REST API. Use the Set Blob Service Properties API to specify the API version you need.

Refer: https://learn.microsoft.com/en-us/azure/frontdoor/front-door-faq

I hope this helps! If these answers your query, do click the "Upvote" and click "Accept the answer" of which might be beneficial to other community members reading this thread.

If the above is unclear or you are unsure about something, please add a comment below.

Thomas Boutell 45 Reputation points

2025-07-16T18:21:41.2766667+00:00

Thanks. To be clear, are you saying that creating a brand new storage account today via the Azure console and following that up by clicking the provided button to add Front Door just doesn't work right now? Or is there somewhere I can change the API version used by newly created storage accounts?
Thomas Boutell 45 Reputation points

2025-07-16T18:22:12.97+00:00

Does it have to do with the age of my overall Azure account? Can I click a "please don't lock me down to ancient APIs for new stuff" button somewhere? 😀
G Sree Vidya 4,005 Reputation points Microsoft External Staff Moderator

2025-07-18T23:24:12.5033333+00:00

Hi Thomas Boutell

Apologies for the delay!

Yes, there are currently scenarios where creating a brand-new Storage Account via the Azure Portal and then immediately using the "Add Front Door" button may result in errors particularly if the underlying API version used by the portal or automation defaults to an older version that doesn't support or recognize newer properties like EnforceMtls.

Do let me know if you have further questions, we will be happy assist you.
Kishor kumar Reddy Akki 10 Reputation points

2025-07-21T10:52:04.5733333+00:00

Hi Sree Vidya,

Thanks for your update.

We have created a new storage account via the Azure portal, and after associating it with existing Azure Front Door, we are encountering an MTLS (Mutual TLS) error. Could you please advise if there’s a known fix or recommended workaround for this?

get error <code id='' style='white-space:pre-wrap'><div>Property EnforceMtls is not allowed to set in current API Version</div></code></br> (Code: BadRequest).
Thomas Boutell 45 Reputation points

2025-07-21T16:16:03.0633333+00:00

OK, thanks for confirming I'm not crazy!

To be transparent, we're normally an AWS shop. I was testing to confirm an issue for a self-hosted client, and we found another way to carry out the test. So I'm not going to go forward with this right now.

But, it's helpful to know that if we choose to use Azure in the future it is not currently simple and straightforward to set up blob storage with a matching front door CDN.
Kishor kumar Reddy Akki 10 Reputation points

2025-07-23T09:18:33.3433333+00:00

Hi @G Sree Vidya

Any Update?

We have created a brand-new storage account via the Azure portal, and after associating it with existing Azure Front Door, we are encountering an MTLS (Mutual TLS) error. Could you please advise if there’s a known fix or recommended workaround for this?

get error <code id='' style='white-space:pre-wrap'><div>Property EnforceMtls is not allowed to set in current API Version</div></code></br> (Code: BadRequest).
Thomas Boutell 45 Reputation points

2025-07-29T12:10:50.81+00:00

Thank you, this does get me further. Click "Redeploy," then make sure you edit the template (it doesn't walk you clearly down a path to this, but the option is there), then remove the line you mentioned and the deployment reports success.

On the first try to actually access a URL I got:

Page not found

Oops! We weren't able to find your Azure Front Door Service configuration. If it's a new configuration that you recently created, it might not be ready yet. You should check again in a few minutes. If the problem persists, please contact Azure support.

This was another annoying limitation: "completing" a deployment doesn't mean anything is actually complete (:

However 15 minutes later I was able to access my content.

Thanks again for your help! I hope Microsoft fixes this bug in the "default path" for setting up front door soon.
Thomas Boutell 45 Reputation points

2025-07-29T12:13:05.64+00:00

Daniel T., would you please submit your comment as an answer so I can mark it as the Accepted Answer? It provides enough guidance to complete the task, unlike the previously accepted answer. Thanks!

Share via

Trying to add Front Door to a brand new blob storage account, I get: "Property EnforceMtls is not allowed to set in current API Version"

2 answers

Your answer