You need to enable JavaScript to run this app.
优惠活动
大模型
产品
解决方案
定价
更多

Azure App Service点击Application settings提示资源未找到问题求助

Troubleshooting "Resource Not Found" Error in Azure App Service Application Settings

Hey there, let's walk through the most likely reasons you're seeing this error when trying to access your App Service's Application Settings in the Azure Portal—especially since your app was running stably until recently:

  • Temporary Portal UI or Backend Glitch
    Azure Portal occasionally hits temporary blips with its management endpoints or UI caching. Try these quick fixes first: refresh the page, open the Portal in an incognito/private window, clear your browser's cache and cookies, or wait 15-30 minutes before retrying. Sometimes old session data gets stuck and causes false "resource not found" messages.

  • Unintentional or Automated Resource Changes
    Even if you didn't modify anything, check if:

    • Someone on your team (or an automated script/CI/CD pipeline) renamed the App Service, moved it to a different resource group/subscription, or temporarily stopped it. Head to the App Service's Overview page to confirm its state is Running and its details match what you expect.
    • Your App Service hit a resource quota limit (like CPU/memory or storage), which can restrict access to management pages even if the app itself keeps running. Check the Alerts section for any quota-related warnings.
  • Changed RBAC Permissions
    Azure sometimes returns "resource not found" instead of a direct permission error if your account's access was modified. Verify that you still have at least Reader or Contributor permissions on the App Service or its parent resource group. Try logging in with an account that has full admin access to see if the error goes away.

  • Regional Service Outage
    Check the Azure Status Dashboard to see if there's a reported issue with App Service management services in your app's region. If there's an ongoing outage, the Azure team is likely already working on it—you'll just need to wait for the service to recover.

  • Corrupted Resource Metadata
    In rare cases, the App Service's backend metadata might get corrupted, preventing the Portal from loading the settings page. Test if you can access the application settings via Azure CLI using this command:

    az webapp config appsettings list --name <your-app-name> --resource-group <your-resource-group>
    

    If the CLI returns the settings successfully, the issue is likely with the Portal or resource metadata. Submit a support ticket to Azure to have them investigate and fix the metadata.

If none of these steps resolve the issue, gather details like the exact error timestamp, your app's region, and any browser console logs (from F12 tools) and share them with Azure Support for deeper troubleshooting.

内容的提问来源于stack exchange,提问作者Slicc

相关产品推荐
方舟 Agent Plan

超全模态模型 × Harness 升级,最新支持 Deepseek-V4.1-Flash、GLM-5.3 系列、Doubao-Seedream-5.0-pro、Kimi-K3 (部分), 限时 9.9 元起

最近更新时间:2026.05.15 04:18:22