Azure WebApp - Issues Detected, Status Unknown

Question

Azure WebApp - Issues Detected, Status Unknown

piotr-p 205

Hi Guys!

I am trying deploy WebApp in Poland Central and I am getting Issues Detected, Status Unknown. I tried to Repair it by restart but it doesnt help. In the same APP plan I have another webapp which is up and runing. I am unable to create a new one.

Golla Venkata Pavani 6,085 Reputation points Microsoft External Staff Moderator

2026-05-27T15:09:05.4533333+00:00
Hi @piotr-p

Thanks for reaching out about the "Issues Detected, Status Unknown" problem with your Web App in Poland Central. I understand it's frustrating, especially when the App Service Plan is healthy and your other app is running fine.

This status often appears when the platform has trouble determining the exact health of a specific app instance. The quickest and most effective way to diagnose this is by using Azure's built-in diagnostics.

Recommended steps:

In your affected Web App, go to Diagnose and solve problems in the left menu.

Start with the Web App Down or Not Responding troubleshooter under Availability & Performance. It usually points out the root cause quickly, whether it's a startup issue, configuration problem, or instance-level glitch.

If that doesn't resolve it, try a full Stop (wait 30–60 seconds) followed by Start, rather than just Restart. You can also restart the entire App Service Plan to force fresh instances.

While you're there, check the Resource health blade for more details on the "Unknown" status.

Review Logs

Enable and check Application Logging and Web Server Logging.

Use Log Stream or Advanced Tools (Kudu) > Log Stream to see real-time errors.

Check Deployment Center for failed deployments.

Reference:
https://learn.microsoft.com/en-us/azure/app-service/overview-diagnostics
https://learn.microsoft.com/en-us/troubleshoot/azure/app-service/troubleshoot-instance-related-issues-on-azure-app-service
Could you please provide app name to investigate the issue further.
Kindly let us know if the above helps or you need further assistance on this issue.

Please "upvote" if the information helped you. This will help us and others in the community as well.
piotr-p 205 Reputation points

2026-05-28T09:15:34.8066667+00:00

Hi there!

I have done all of steps including hard stop for a while and it doesn't help. The only thing which is helping is first open URL and then magically the WebApp is starting correctly but never by simply kliking "Start". Even when the "Always on" is turn on, the same thing is happening. Only opening url after stop can make it up and running. More details in PM.
Golla Venkata Pavani 6,085 Reputation points Microsoft External Staff Moderator

2026-06-02T20:27:00.9766667+00:00
Hi @piotr-p

From the deep investigation, We found that the behavior you're seeing (app starts reliably only after you manually hit the URL, but not via the Start button, even with Always On enabled) is typically caused by a slow container startup. Azure performs an internal warm-up probe right after the container launches, and if your app doesn't respond within the default 230-second limit, the platform marks it as failed, resulting in the "Issues Detected" and "Status Unknown" state.

Recommended FixThe most effective solution is to increase the container startup timeout using an application setting:

Go to your Web App > Configuration > Application settings.

Click New application setting and add:

Name: WEBSITES_CONTAINER_START_TIME_LIMIT

Value: 900 (15 minutes, you can go up to 1800 if needed)

Click OK, then Save.

Restart the Web App.

This setting gives your app more time to fully initialize before Azure's health check kicks in.

Reference:
https://learn.microsoft.com/en-us/azure/app-service/reference-app-settings#container-settings
https://learn.microsoft.com/en-us/troubleshoot/azure/app-service/faqs-app-service-linux-new
Quick Additional Tips

Make sure Always On is enabled under Configuration > General settings.

Optionally, add a fast health endpoint and set WEBSITE_WARMUP_PATH (e.g., /health) so the warm-up probe succeeds quicker.

After applying the change, monitor the Log stream during startup to see if anything specific is taking a long time.

Kindly let us know if the above helps or you need further assistance on this issue.

Please "upvote" if the information helped you. This will help us and others in the community as well.
piotr-p 205 Reputation points

2026-06-03T09:09:57.34+00:00

Sorry, but I don't believe this is the root cause. The proxy-2 application is essentially a copy of the proxy application—both have identical settings, configurations, and resource allocations, yet only the new instance is affected.

Furthermore, proxy-2 was initially restored from a backup of proxy. When the issue first appeared, the application was deleted and recreated from scratch, but the problem persisted. This suggests that the issue is not related to the application's configuration or deployment process. Both are on the same app plan.

1 answer

Your answer

Golla Venkata Pavani 6,085 Reputation points Microsoft External Staff Moderator

2026-05-27T15:09:05.4533333+00:00

Hi @piotr-p

Thanks for reaching out about the "Issues Detected, Status Unknown" problem with your Web App in Poland Central. I understand it's frustrating, especially when the App Service Plan is healthy and your other app is running fine.

This status often appears when the platform has trouble determining the exact health of a specific app instance. The quickest and most effective way to diagnose this is by using Azure's built-in diagnostics.

Recommended steps:

In your affected Web App, go to Diagnose and solve problems in the left menu.

Start with the Web App Down or Not Responding troubleshooter under Availability & Performance. It usually points out the root cause quickly, whether it's a startup issue, configuration problem, or instance-level glitch.

If that doesn't resolve it, try a full Stop (wait 30–60 seconds) followed by Start, rather than just Restart. You can also restart the entire App Service Plan to force fresh instances.

While you're there, check the Resource health blade for more details on the "Unknown" status.

Review Logs

Enable and check Application Logging and Web Server Logging.

Use Log Stream or Advanced Tools (Kudu) > Log Stream to see real-time errors.

Check Deployment Center for failed deployments.

Reference:
https://learn.microsoft.com/en-us/azure/app-service/overview-diagnostics
https://learn.microsoft.com/en-us/troubleshoot/azure/app-service/troubleshoot-instance-related-issues-on-azure-app-service
Could you please provide app name to investigate the issue further.
Kindly let us know if the above helps or you need further assistance on this issue.

Please "upvote" if the information helped you. This will help us and others in the community as well.
piotr-p 205 Reputation points

2026-05-28T09:15:34.8066667+00:00

Hi there!

I have done all of steps including hard stop for a while and it doesn't help. The only thing which is helping is first open URL and then magically the WebApp is starting correctly but never by simply kliking "Start". Even when the "Always on" is turn on, the same thing is happening. Only opening url after stop can make it up and running. More details in PM.
Golla Venkata Pavani 6,085 Reputation points Microsoft External Staff Moderator

2026-06-02T20:27:00.9766667+00:00

Hi @piotr-p

From the deep investigation, We found that the behavior you're seeing (app starts reliably only after you manually hit the URL, but not via the Start button, even with Always On enabled) is typically caused by a slow container startup. Azure performs an internal warm-up probe right after the container launches, and if your app doesn't respond within the default 230-second limit, the platform marks it as failed, resulting in the "Issues Detected" and "Status Unknown" state.

Recommended FixThe most effective solution is to increase the container startup timeout using an application setting:

Go to your Web App > Configuration > Application settings.

Click New application setting and add:

Name: WEBSITES_CONTAINER_START_TIME_LIMIT

Value: 900 (15 minutes, you can go up to 1800 if needed)

Click OK, then Save.

Restart the Web App.

This setting gives your app more time to fully initialize before Azure's health check kicks in.

Reference:
https://learn.microsoft.com/en-us/azure/app-service/reference-app-settings#container-settings
https://learn.microsoft.com/en-us/troubleshoot/azure/app-service/faqs-app-service-linux-new
Quick Additional Tips

Make sure Always On is enabled under Configuration > General settings.

Optionally, add a fast health endpoint and set WEBSITE_WARMUP_PATH (e.g., /health) so the warm-up probe succeeds quicker.

After applying the change, monitor the Log stream during startup to see if anything specific is taking a long time.

Kindly let us know if the above helps or you need further assistance on this issue.

Please "upvote" if the information helped you. This will help us and others in the community as well.
piotr-p 205 Reputation points

2026-06-03T09:09:57.34+00:00

Sorry, but I don't believe this is the root cause. The proxy-2 application is essentially a copy of the proxy application—both have identical settings, configurations, and resource allocations, yet only the new instance is affected.

Furthermore, proxy-2 was initially restored from a backup of proxy. When the issue first appeared, the application was deleted and recreated from scratch, but the problem persisted. This suggests that the issue is not related to the application's configuration or deployment process. Both are on the same app plan.

Answer 1

Use the following steps to troubleshoot and collect data for this issue:

Check whether the problem is regional or platform-related:
- Verify if deployments or app creation in other regions (for example, a different nearby region) succeed. If they do, the issue might be specific to Poland Central capacity or infrastructure.
- Check Azure status for any ongoing outages or incidents affecting Poland Central.
Verify the App Service Plan and resource health:
- In the Azure portal, open the existing App Service Plan used by the working web app and confirm it is in a healthy/running state and not at capacity (CPU, memory, or quota limits).
- Confirm the plan’s pricing tier is not hitting quotas that could prevent additional web apps from being created.
Try basic mitigation actions on the plan and app:
- Restart the App Service Plan’s existing apps from the Azure portal.
- If feasible, temporarily scale the App Service Plan up to a higher tier and retry creating the new web app. Insufficient capacity can cause creation or deployment issues similar to 5xx/"unknown" states.
Collect detailed diagnostics before contacting support:
- If creation fails via Azure portal, reproduce the issue and capture a browser trace.
- If using Azure CLI or PowerShell, rerun the failing command with verbose logging and save the full output.
- If the failure occurs as part of an ARM/Bicep/template deployment:
  - Go to Resource group → Deployments in the Azure portal.
  - Locate the failed deployment and note the detailed error message and correlation ID.
If the issue persists only in Poland Central and not in other regions, open a Microsoft support ticket and attach:
- Browser trace from the portal.
- CLI/PowerShell verbose logs.
- ARM deployment error details and correlation ID.

These artifacts allow Microsoft support to investigate backend capacity or platform issues that can cause "Issues Detected, Status Unknown" and app creation failures in a specific region.

References:

Share via

Azure WebApp - Issues Detected, Status Unknown

1 answer

Your answer