Apr 03 2023
03:48 AM
- last edited on
Mar 05 2024
02:36 PM
by
TechCommunityAP
Apr 03 2023
03:48 AM
- last edited on
Mar 05 2024
02:36 PM
by
TechCommunityAP
Hello All,
Whenerver I use the "Archive Files" task in the Azure DevOps build pipeline, upon release, I get the following error on my azurewebsite: You do not have permission to view this directory or page.
However, when I use the Copy Files" task as a workaround, the website works just fine. The problem is that this task takes almost 10x as long as the Archive Files task. Any help will be appreciated in resolving this issue.
Apr 03 2023 05:49 PM
Are you saying webapp, can try to check the log below:
Login to Azure > App Services > Your Web App > App Service logs, turn on Detailed Error Messages or turn on all of the logging options
Apr 05 2023 09:33 PM
Apr 05 2023 09:52 PM - edited Apr 06 2023 06:00 AM
Solution@techieg4 FInally resolved it by unchecking the "Prepend root folder name to archive path" checkbox (see image below), which was zipping up everything within a "build" folder and deploying it as such. So, the website could only see the "build" directory in wwwroot, which triggered the error message since browsing to the url was trying to access this folder rather than the index.html that was supposed to be at the wwwroot.. Once I unchecked that checkbox, no more zipping up in the "build" folder and zipped files get deployed in wwwroot as it should. All is well!
Jan 03 2024 08:14 AM
I am using AzureResourceManagerTemplateDeployment@3 task to deploy an azure ad b2c tenant using the release pipeline.
When I was manually running the script using my local PowerShell then it was running smoothly but in release pipeline, I got the same error as yours:
Now the thing is that I tried giving every related admin rights like subscription owner and ad b2c global administrator. I wasn't able to resolve the issue. Could you please help me with this?
Apr 05 2023 09:52 PM - edited Apr 06 2023 06:00 AM
Solution@techieg4 FInally resolved it by unchecking the "Prepend root folder name to archive path" checkbox (see image below), which was zipping up everything within a "build" folder and deploying it as such. So, the website could only see the "build" directory in wwwroot, which triggered the error message since browsing to the url was trying to access this folder rather than the index.html that was supposed to be at the wwwroot.. Once I unchecked that checkbox, no more zipping up in the "build" folder and zipped files get deployed in wwwroot as it should. All is well!