AuthenticationFailed Error in Azure DevOps Pipeline with Bicep Template

Question

AuthenticationFailed Error in Azure DevOps Pipeline with Bicep Template

Nitin Itare 25

An existing storage account has public access disabled and private endpoints enabled for blob, queue, table, and web services. The Azure DevOps pipeline is utilizing the Azure managed DevOps pool linked to a VNet, with VNet peering established with all other VNets.

While using a Bicep template to create new containers in the existing storage account, the 'what if' command is being executed in the pipeline before deployment. However, the following error is encountered:

DeploymentWhatIfResourceError - The request to predict template deployment changes to scope '/providers/Microsoft.Management/managementGroups/mg-mylz' has failed due to a resource error. See details for more information.

AuthenticationFailed - Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.

What could be the cause of this issue?

Hari Babu Vattepally 3,270 Reputation points Microsoft External Staff Moderator

2025-04-15T15:21:33.8266667+00:00
Hi @Nitin Itare ,

We see that the DeploymentWhatIfResourceError you are encountering in your Azure DevOps pipeline while executing the 'what if' command with a Bicep template might be due to the configuration of your existing storage account. Since public access is disabled and private endpoints are enabled, the pipeline may lack the necessary permissions or access to interact with the storage account resources.

When using a Bicep template, the deployment might fail to retrieve necessary information about existing resources due to storage account firewall restrictions or insufficient permissions for the Azure DevOps pipeline to access the storage account.

To fix this issue, make sure the Azure DevOps pipeline has the required permissions to access the storage account and that the private endpoints are properly configured to allow access from the Azure DevOps environment.

For more additional information, please refer the below documentation:

Troubleshoot common Azure deployment errors

Develop a deployment script in Bicep

I hope the above helps in addressing your query.

Please let us know in the comments below, if the issue is resolved or still persists. We will be glad to assist you closely.

Please do consider to “up-vote” wherever the information provided helps you, this can be beneficial to other community members. Accepted answers show up at the top, resulting in improved discoverability for others.
Nitin Itare 25 Reputation points

2025-04-15T15:33:10.1266667+00:00

I am not sure if that's the actual error or misleading error. When I tried creating one container it is running fine (no what if or authentication error) but when multiple containers it is running into error, which doesn't make any sense.

Also FYI I am using AVM bicep module for storage account, version 0.9.1
https://github.com/Azure/bicep-registry-modules/tree/main/avm/res/storage/storage-account
Nitin Itare 25 Reputation points

2025-04-15T16:18:38.6666667+00:00

@Hari Babu Vattepally could you please check my previous comment.
Hari Babu Vattepally 3,270 Reputation points Microsoft External Staff Moderator

2025-04-16T10:47:16.4833333+00:00
Hi @Nitin Itare ,

It seems like you are facing an authentication issue, when trying to deploy multiple containers using Bicep template in Azure DevOps.

Please follow the below suggestions to get the issue resolved:

Make sure the identity used for authentication has the necessary permissions to deploy multiple containers. Assign the AcrPull role to the managed identity if you're pulling images from Azure Container Registry (ACR).

Make sure you are using the latest version of the AVM Bicep module. Version 0.9.1 may have known issues or limitations. Please check the module repository for any updates or patches.

When you're setting up multiple containers, make sure they don't depend on each other without you knowing. If the module tries to create resources at the same time without the right order, it might cause errors. Please include explicit dependencies in your Bicep template to ensure the correct sequencing of resources.

If making multiple containers in one go is causing problems, try breaking the deployment into smaller batches. This can help pinpoint the issue and prevent any throttling or concurrency troubles.

Azure has certain limitations on the number of resources you can deploy at the same time. If you're attempting to deploy multiple containers simultaneously, you might be reaching a limit. Check the Azure documentation for quotas related to the resources you're trying to create.

If the problem continues, please report it on the module's GitHub repository, including detailed information about your use case, error messages, and configuration. The maintainers or community may offer insights or solutions.

I hope by following the above will help in resolving the issue.

Please let us know if the issue is resolved or still persists. We will glad to assist you closely.
Nitin Itare 25 Reputation points

2025-04-16T12:37:00.4033333+00:00

@Hari Babu Vattepally It was just a syntax mistake with container name. I have a space at the end of one of the container name. Simply wasted two days of time to figure it out and all credits to the error message which is misleading.
What is the meaning of using the what-if tool to validate if it can't even find such a silly mistakes and should be giving an error like container name should not contain space or syntax error etc. I hope it can be further improved.
Hari Babu Vattepally 3,270 Reputation points Microsoft External Staff Moderator

2025-04-16T15:38:39.2933333+00:00

Hi @Nitin Itare ,

We are glad to know that the issue has been resolved and thank you for sharing the solution with the community here. However, please give your feedback here about the product please provide feedback to Microsoft through Azure Feedback Portal. Sharing detailed feedback can help highlight the importance of this issue and potentially expedite the development of a solution.

It is important to communicate the impact and urgency of this matter clearly to Microsoft, as user feedback plays a crucial role in their prioritization process. By doing so, you contribute to the improvement of their services, which can benefit all users facing similar challenges.

Accepted answer

0 additional answers

Your answer

Hari Babu Vattepally 3,270 Reputation points Microsoft External Staff Moderator

2025-04-15T15:21:33.8266667+00:00

Hi @Nitin Itare ,

We see that the DeploymentWhatIfResourceError you are encountering in your Azure DevOps pipeline while executing the 'what if' command with a Bicep template might be due to the configuration of your existing storage account. Since public access is disabled and private endpoints are enabled, the pipeline may lack the necessary permissions or access to interact with the storage account resources.

When using a Bicep template, the deployment might fail to retrieve necessary information about existing resources due to storage account firewall restrictions or insufficient permissions for the Azure DevOps pipeline to access the storage account.

To fix this issue, make sure the Azure DevOps pipeline has the required permissions to access the storage account and that the private endpoints are properly configured to allow access from the Azure DevOps environment.

For more additional information, please refer the below documentation:

Troubleshoot common Azure deployment errors

Develop a deployment script in Bicep

I hope the above helps in addressing your query.

Please let us know in the comments below, if the issue is resolved or still persists. We will be glad to assist you closely.

Please do consider to “up-vote” wherever the information provided helps you, this can be beneficial to other community members. Accepted answers show up at the top, resulting in improved discoverability for others.
Nitin Itare 25 Reputation points

2025-04-15T15:33:10.1266667+00:00

I am not sure if that's the actual error or misleading error. When I tried creating one container it is running fine (no what if or authentication error) but when multiple containers it is running into error, which doesn't make any sense.

Also FYI I am using AVM bicep module for storage account, version 0.9.1
https://github.com/Azure/bicep-registry-modules/tree/main/avm/res/storage/storage-account
Nitin Itare 25 Reputation points

2025-04-15T16:18:38.6666667+00:00

@Hari Babu Vattepally could you please check my previous comment.
Hari Babu Vattepally 3,270 Reputation points Microsoft External Staff Moderator

2025-04-16T10:47:16.4833333+00:00

Hi @Nitin Itare ,

It seems like you are facing an authentication issue, when trying to deploy multiple containers using Bicep template in Azure DevOps.

Please follow the below suggestions to get the issue resolved:

Make sure the identity used for authentication has the necessary permissions to deploy multiple containers. Assign the AcrPull role to the managed identity if you're pulling images from Azure Container Registry (ACR).

Make sure you are using the latest version of the AVM Bicep module. Version 0.9.1 may have known issues or limitations. Please check the module repository for any updates or patches.

When you're setting up multiple containers, make sure they don't depend on each other without you knowing. If the module tries to create resources at the same time without the right order, it might cause errors. Please include explicit dependencies in your Bicep template to ensure the correct sequencing of resources.

If making multiple containers in one go is causing problems, try breaking the deployment into smaller batches. This can help pinpoint the issue and prevent any throttling or concurrency troubles.

Azure has certain limitations on the number of resources you can deploy at the same time. If you're attempting to deploy multiple containers simultaneously, you might be reaching a limit. Check the Azure documentation for quotas related to the resources you're trying to create.

If the problem continues, please report it on the module's GitHub repository, including detailed information about your use case, error messages, and configuration. The maintainers or community may offer insights or solutions.

I hope by following the above will help in resolving the issue.

Please let us know if the issue is resolved or still persists. We will glad to assist you closely.
Nitin Itare 25 Reputation points

2025-04-16T12:37:00.4033333+00:00

@Hari Babu Vattepally It was just a syntax mistake with container name. I have a space at the end of one of the container name. Simply wasted two days of time to figure it out and all credits to the error message which is misleading.
What is the meaning of using the what-if tool to validate if it can't even find such a silly mistakes and should be giving an error like container name should not contain space or syntax error etc. I hope it can be further improved.
Hari Babu Vattepally 3,270 Reputation points Microsoft External Staff Moderator

2025-04-16T15:38:39.2933333+00:00

Hi @Nitin Itare ,

We are glad to know that the issue has been resolved and thank you for sharing the solution with the community here. However, please give your feedback here about the product please provide feedback to Microsoft through Azure Feedback Portal. Sharing detailed feedback can help highlight the importance of this issue and potentially expedite the development of a solution.

It is important to communicate the impact and urgency of this matter clearly to Microsoft, as user feedback plays a crucial role in their prioritization process. By doing so, you contribute to the improvement of their services, which can benefit all users facing similar challenges.

Answer 1

Hi @Nitin Itare

I'm glad that you were able to resolve your issue and thank you for posting your solution, so that others experiencing the same thing can easily reference this!

Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to "Accept " the answer. Accepted answers show up at the top, resulting in improved discoverability for others.

Issue: "Authentication Failed Error in Azure DevOps Pipeline with Bicep Template".

Solution: "The issue turned out to be a simple syntax error in the container name—there was an unintended space at the end of the name. Which resolved the issue by clearing the space".

If you have any further questions, please let us know in the comments how we can assist. We are here to help you and strive to make your experience better and greatly value your feedback.

Please let us know if you have any further queries. I’m happy to assist you further.

Please do not forget to "Accept the answer” and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

User's image

Share via

AuthenticationFailed Error in Azure DevOps Pipeline with Bicep Template

0 additional answers

Your answer