Share via

Not able to save Application firewall rules after introducing "Max Client Connection Lifetime setting".

Gopi Krishna Thotakura 0 Reputation points
2025-07-03T03:42:14.6533333+00:00

Not able to save Application firewall rules after introducing "Max Client Connection Lifetime setting". Looks like a bug in azure Web PubSub Service.

User's image

Azure Web PubSub
Azure Web PubSub
An Azure service that provides real-time messaging for web applications using WebSockets and the publish-subscribe pattern.

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Shree Hima Bindu Maganti 5,480 Reputation points Microsoft External Staff Moderator
    2025-07-07T16:54:26.81+00:00

    Hi @Gopi Krishna Thotakura
    If you are unable to save Application Firewall rules after setting the Max Client Connection Lifetime in Azure Web PubSub, this may be due to a known limitation or bug in the Azure portal. The Max Client Connection Lifetime determines how long a client connection can stay active before needing to reconnect, with valid values ranging from 0 (to disable the limit) up to 604800 seconds (7 days). Using incorrect or unsupported values can cause saving issues.

    As outlined in Microsoft documentation, this setting is part of the Application Firewall for Azure Web PubSub, which helps manage connections and messages through policies. You can set maxClientConnectionLifetimeInSeconds using ARM templates or Bicep files, as described in the Microsoft.SignalRService/webPubSub resource schema.

    If the Azure Portal UI is causing problems, try configuring the setting via ARM template deployment or Azure CLI as an alternative.
    Let me know if you have any further assistance needed.

    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.