In Static Web App Configuration tab Apply button stays disabled

Question

In Static Web App Configuration tab Apply button stays disabled

Pavlin Penev 40

Hello,

A while ago we've put a password protection to a Static Web App through the Configuration tab. Since we came up to a moment we don't need it anymore we want to remove it. For us to do this we went to the corresponding app's Configuration tab and clicked the Disabled radio button on the password protection section. The Discard button turned out enabled but the Apply one stayed grayed out not letting us save the changes made. First we checked the IAM role assignments - no changes have been made there so we shouldn't experience issues on that account. After that we checked other Static Web Apps we have deployed - the issue persists throughout all of them. No Apply button available. Tried other configurations and they are working. This occurs only at the Configuration tab. We tried different browsers, tried with the other settings in the tab, tried clearing the cache and no solution found yet.

Does someone have any idea what the issue is?

Thank you

Pavlin Penev 40 Reputation points

2026-03-26T13:46:34.2433333+00:00
Hello @Golla Venkata Pavani ,

Thank you for your quick reply.

Sadly I can provide you with this as feedback to your answer:

As I mentioned in my question description we want to remove the password so we made an active change to the configuration state and still not Apply button available. We also tried toggling the other settings to force the change detection.

We've done a hard refresh and cache clear and still nothing

We've triggered a redeploy, no conflicting authentication or routing rules and still no active Apply button

I want to remind also on the issue that we've tried this with not just one but multiple Static Web Apps deployed and the issue persists everywhere. Even on apps that we've password protected and managed to disable it in the past.

Thank you in advance!
Golla Venkata Pavani 3,415 Reputation points Microsoft External Staff Moderator

2026-04-09T10:16:27.4266667+00:00
Hi @Pavlin Penev ,

Thank you for reaching us regarding the issue that what you’re seeing is a known Azure portal behavior related to how Static Web Apps detect configuration changes, specifically for password protection.

This behavior is a known, occasional Azure portal UI limitation when disabling Password protection in Configuration > General settings for Azure Static Web Apps.

According to Microsoft documentation:

Password protection is supported only on the Standard plan and is configured through the Azure portal UI.

Azure Static Web Apps apply configuration changes only when the portal detects a change in the effective configuration state, not merely a UI toggle . If password protection is already effectively disabled, selecting Disabled again may not register as a configuration change. In this case, Discard becomes active (UI interaction occurred), but Apply remains grayed out because there is no detected change to save.

This behavior is limited to the password protection setting and is not caused by IAM/RBAC permissions, browser cache, or other configuration sections. Recommended resolution steps:

Force the portal to detect a configuration change (most effective)

Set Password protection to Disabled. Make a small temporary change to another field in the same General settings tab (for example, briefly edit a value and revert it). Once a configuration delta is detected, the Apply button becomes enabled. Click Apply to save.

Hard refresh and retry

Perform a hard refresh (Ctrl + F5 on Windows), then repeat the steps above to allow the portal UI to re‑sync with the effective configuration state.

Alternative: trigger a redeployment

Ensure your staticwebapp.config.json file does not contain conflicting authentication or routing rules. Commit a small change or redeploy the app from source control. A new deployment causes Azure Static Web Apps to re‑evaluate the effective configuration, which can clear lingering portal state .

Reference: https://dori-uw-1.kuma-moon.com/en-us/azure/static-web-apps/password-protection https://dori-uw-1.kuma-moon.com/en-us/azure/static-web-apps/configuration#restrictions

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.

Answer accepted by question author

1 additional answer

Your answer

Pavlin Penev 40 Reputation points

2026-03-26T13:46:34.2433333+00:00

Hello @Golla Venkata Pavani ,

Thank you for your quick reply.

Sadly I can provide you with this as feedback to your answer:

As I mentioned in my question description we want to remove the password so we made an active change to the configuration state and still not Apply button available. We also tried toggling the other settings to force the change detection.

We've done a hard refresh and cache clear and still nothing

We've triggered a redeploy, no conflicting authentication or routing rules and still no active Apply button

I want to remind also on the issue that we've tried this with not just one but multiple Static Web Apps deployed and the issue persists everywhere. Even on apps that we've password protected and managed to disable it in the past.

Thank you in advance!

Answer 1

Hi @Pavlin Penev ,

Thank you for reaching us regarding the issue that what you’re seeing is a known Azure portal behavior related to how Static Web Apps detect configuration changes, specifically for password protection.

This is a known issue. A fix has been identified, and a repair item has been raised. The internal team is currently working on it. In the meantime, using Azure CLI can help mitigate the issue.

If the answer is helpful, Please do click "Accept the answer” and Yes, this can be beneficial to other community members.

If you have any other questions, let me know in the "comments" and I would be happy to help you.

Answer 2

The Apply button in the Static Web Apps Configuration blade only becomes enabled when the portal detects a pending configuration change that it can submit. For password protection, the change must meet the feature’s validation rules before Apply is enabled.

For password protection specifically:

Password protection is only available for Static Web Apps on the Standard plan.
When enabling or changing password protection, the Visitor password must:
- Be at least eight characters long
- Contain a capital letter
- Contain a lowercase letter
- Contain a number
- Contain a symbol
When disabling password protection (selecting Disabled), the portal must still recognize that the configuration state has changed from a previously saved value. If the current effective configuration is already “Disabled” (for example, due to a prior change or a delayed portal refresh), toggling the radio button may not register as a change and the Apply button remains disabled.

Given that other configuration changes in the same blade do enable Apply, and the issue appears only for password protection across multiple apps, the behavior is most likely due to:

The portal not detecting a net change in the password protection setting (already effectively disabled), or
A transient portal-side issue or caching delay where the UI does not refresh the current state correctly.

Workarounds and checks:

Confirm plan and feature state
- Verify that each Static Web App is on the Standard plan, as password protection is a Standard-plan feature.
Force a detectable change
- Temporarily switch password protection to Protect both production and staging environments, enter a valid password that meets the complexity requirements, and check whether Apply becomes enabled.
- If Apply enables, save, then switch back to Disabled and save again.
Use an alternate browser/session
- Open the Azure portal in a different browser or a private/incognito window to avoid stale cached UI state and try the same steps.

If the portal still never enables Apply for any change to password protection across multiple Static Web Apps, this indicates a portal-side issue rather than a configuration or RBAC problem. In that case, capture the portal notification details (if any error appears) and open a support request so the issue can be investigated on the service side.

References:

Share via

In Static Web App Configuration tab Apply button stays disabled

1 additional answer

Your answer