Function App Deployment issue - Wiz Disk Analyzer Scanner details

Question

Function App Deployment issue - Wiz Disk Analyzer Scanner details

Twisha Mistry 46 Microsoft External Staff

Yesterday, starting around 9:00 AM, we encountered issues deploying the Function App through the DevOps pipeline. Under normal circumstances, the pipeline completes deployment within approximately one minute. However, yesterday the deployment duration increased to over 10 minutes in some instances, and in others it failed with the error:

Error: Failed to deploy web package to App Service. Conflict (CODE: 409).

Although the zip deployment was initiated within 30 seconds, the deployment either took more than 10 minutes to complete or failed with the above error. Upon investigation, we identified that the Wiz Disk Analyzer was running in the background. Additionally, the App Service Plan CPU utilization was consistently high, reaching 98–99%, which likely contributed to the deployment failures and delays.

Twisha Mistry 46 Reputation points Microsoft External Staff

2026-01-09T08:37:46.95+00:00
Hi @Pravallika
1. There are no changes made in the pipelines.

This ASP has 3 Functions Apps which are deployed in the same pipeline sequentially.

ASP is under S1. As mentioned, the usual usage is about 70-85% with regards to CPU percentage consumption

The only operation we found in the activity log was - Command - Wiz Disk Analyzer which was failing.
Twisha Mistry 46 Reputation points Microsoft External Staff

2026-01-09T11:26:56.7833333+00:00

@Pravallika KV We connected over the Teams calls and I have explained the details in depth. Also, I have shared all required information. Request you to kindly prioritize and help us with the details.

Pravallika KV 15,460 Microsoft External Staff Moderator

Hi @Twisha Mistry ,

For the time when the function deployment was delayed, we see below exceptions with the code.

at System.Enum.TryParseByValueOrName[TUnderlying,TStorage](RuntimeType enumType, ReadOnlySpan`1 value, Boolean ignoreCase, Boolean throwOnFailure, TUnderlying& result),   at System.Enum.TryParse(Type enumType, ReadOnlySpan`1 value, Boolean ignoreCase, Boolean throwOnFailure, Object& result),   at Microsoft.Extensions.Configuration.ConfigurationBinder.TryConvertValue(Type type, String value, String path, Object& result, Exception& error)

Stack:    at System.Convert.ToBoolean(String value)
   at CSU.UAT.WebApplication.Helpers.Implementations.ADOWorkItemsHelper..ctor(AzureKeyVaultApplicationSecrets secretsProvider, ApplicationStaticConfiguration configuration, ITelemetryClient telemetry, IBlobStorageServiceClient blobStorageServiceClient, IDistributedCache cache, ICacheManager redisCache, ICommonServicesHelper commonServicesHelper, IECIFWorkscopeHelper ecifWorkscopeHelper, IAccessTokenService accessTokenService) in D:\a\_work\1\XXXX:line 132

   at CSU.UAT.FnApp.SyncActions.Implementations.MSXRealTimeDataSync..ctor(ApplicationStaticConfiguration configuration, AzureKeyVaultApplicationSecrets secretsProvider, ITelemetryClient telemetry, IAccessTokenService accessTokenService) in D:\a\_work\XXXXX
   at CSU.UAT.FnApp.SyncActions.MSXRealtimeSyncAppListActionIds..ctor(ApplicationStaticConfiguration configuration, AzureKeyVaultApplicationSecrets secretsProvider, HttpClient httpClient, ITelemetryClient telemetry, IAccessTokenService accessTokenService) in D:\a\_work\1\s\CXXXX\:line 21

At the time of deployment, these were the processes running for a long time.

Please check the complete inner message and process details I have shared offline.

Pravallika KV 15,460 Reputation points Microsoft External Staff Moderator

2026-01-12T06:13:54.1+00:00

Hi @Twisha Mistry ,

Following up to see if the answer provided was helpful. If this answers your query, do click Accept Answer and Yes, if you have any further queries do let us know.

Answer accepted by question author

0 additional answers

Your answer

Twisha Mistry 46 Reputation points Microsoft External Staff

2026-01-09T08:37:46.95+00:00

Hi @Pravallika
1. There are no changes made in the pipelines.

This ASP has 3 Functions Apps which are deployed in the same pipeline sequentially.

ASP is under S1. As mentioned, the usual usage is about 70-85% with regards to CPU percentage consumption

The only operation we found in the activity log was - Command - Wiz Disk Analyzer which was failing.
Twisha Mistry 46 Reputation points Microsoft External Staff

2026-01-09T11:26:56.7833333+00:00

@Pravallika KV We connected over the Teams calls and I have explained the details in depth. Also, I have shared all required information. Request you to kindly prioritize and help us with the details.
Pravallika KV 15,460 Reputation points Microsoft External Staff Moderator

2026-01-09T12:54:15.1166667+00:00

Hi @Twisha Mistry ,

For the time when the function deployment was delayed, we see below exceptions with the code.

at System.Enum.TryParseByValueOrName[TUnderlying,TStorage](RuntimeType enumType, ReadOnlySpan`1 value, Boolean ignoreCase, Boolean throwOnFailure, TUnderlying& result), at System.Enum.TryParse(Type enumType, ReadOnlySpan`1 value, Boolean ignoreCase, Boolean throwOnFailure, Object& result), at Microsoft.Extensions.Configuration.ConfigurationBinder.TryConvertValue(Type type, String value, String path, Object& result, Exception& error)

Stack: at System.Convert.ToBoolean(String value) at CSU.UAT.WebApplication.Helpers.Implementations.ADOWorkItemsHelper..ctor(AzureKeyVaultApplicationSecrets secretsProvider, ApplicationStaticConfiguration configuration, ITelemetryClient telemetry, IBlobStorageServiceClient blobStorageServiceClient, IDistributedCache cache, ICacheManager redisCache, ICommonServicesHelper commonServicesHelper, IECIFWorkscopeHelper ecifWorkscopeHelper, IAccessTokenService accessTokenService) in D:\a\_work\1\XXXX:line 132 at CSU.UAT.FnApp.SyncActions.Implementations.MSXRealTimeDataSync..ctor(ApplicationStaticConfiguration configuration, AzureKeyVaultApplicationSecrets secretsProvider, ITelemetryClient telemetry, IAccessTokenService accessTokenService) in D:\a\_work\XXXXX at CSU.UAT.FnApp.SyncActions.MSXRealtimeSyncAppListActionIds..ctor(ApplicationStaticConfiguration configuration, AzureKeyVaultApplicationSecrets secretsProvider, HttpClient httpClient, ITelemetryClient telemetry, IAccessTokenService accessTokenService) in D:\a\_work\1\s\CXXXX\:line 21

At the time of deployment, these were the processes running for a long time.

Please check the complete inner message and process details I have shared offline.
Pravallika KV 15,460 Reputation points Microsoft External Staff Moderator

2026-01-12T06:13:54.1+00:00

Hi @Twisha Mistry ,

Following up to see if the answer provided was helpful. If this answers your query, do click Accept Answer and Yes, if you have any further queries do let us know.

Answer 1

Hi @Twisha Mistry ,

Thanks for reaching out to Microsoft Q&A.

As discussed offline, I am summarizing the analysis and findings regarding the deployment issue you experienced.

The deployment delays and intermittent failures were primarily caused by high CPU usage and IO contention at the OS level due to Wiz Disk Analyzer running in the background. These consumed resources needed by the App Service worker processes, slowing down zip deployment operations and occasionally causing conflicts during file writes.

Analysis:

Function App CPU: The max observed CPU for your function app was 31.58% (not 98-99%)
Worker Density: The worker hosts ~39 app pools. Total measured IIS process CPU peaked at ~165% (which for a multi-core system is still within normal bounds)
"Wiz Disk Analyzer" CPU: The platform telemetry does not capture OS-level processes like Wiz Disk Analyzer. The 98-99% CPU the customer saw was likely from OS-level agents running outside IIS worker processes
Deployment slowdown correlation: The slowest deployment (152 seconds) occurred at 14:30 UTC, when Worker CPU was elevated at 143% - this correlates with increased load

Conclusion:

The Wiz Disk Analyzer (or other OS-level scanning tools) consuming 98-99% CPU would explain:

Slow deployments (IO and CPU contention during file operations)
The customer-observed high CPU (at VM/OS level, not IIS process level)
The intermittent nature (scans run periodically)

Recommendation:

As informed earlier, you should work with your security team to schedule Wiz scans during off-peak hours or throttle the scanner's resource consumption.

Hope this helps!

If the resolution was helpful, kindly take a moment to click on and click on Yes for was this answer helpful. And, if you have any further query do let us know.

Share via

Function App Deployment issue - Wiz Disk Analyzer Scanner details

0 additional answers

Your answer