@Sheethal Pai Thank you for reaching out to Microsoft Q&A, apologize for any inconvenience caused on this.
As mentioned in this documentation, it looks like you are running the webjob under the default location of d:\home\site\wwwroot\app_data\jobs... and using Run-From-Package. The start\stop mechanism requires write access to add the disable.job for stopping a continuous WebJob and deleting it when starting it. This will not succeed when the location is read-only.
Just want to check whether web Jobs that were deployed through azure DeVops were you able to see them under web Jobs section in the azure portal of your web app. If yes, you can add any of the below app setting to stop the webjob.
- WEBJOBS_STOPPED - Set this setting to 1 to disable running any job (will also stop all currently running jobs).
- WEBJOBS_DISABLE_SCHEDULE - Set this to 1 to turn off all scheduled triggering. Unlike with WEBJOBS_STOPPED, Web Jobs can still be manually invoked.
Refer to this GitHub documentation from more information.
Alternatively, you can use the Invoke-AzResourceAction (this documentation is using Invoke-AzureRMResouceAction use Az cmdlets instead of AzureRM cmdlets) or Web Apps - Stop Continuous Web Job REST API to stop the webjob.
Feel free to reach out to me if you have any further questions on this.