The option "Slot setting" is no longer obeyed for Application Settings which is only defined in one slot RRS feed

  • General discussion

  • One of our sites has been updated (update that also contains .net 4.7.2) and now we experience an altered behavior related to Application Settings when swapping slots.

    If you have an Application Setting on "warm-up" slot, that is marked with "Slot setting" set to true and this setting does not exists on the Production slot, then during swap this setting is applied to the Production slot also.
    This is not the case in the previous version.

    Since I am not allowed to upload images here you can see on the github where I first posted it for Azure portal example:



    This was not a nice surprise that all our web jobs no longer is running in production.

    I can create the same Application Setting on production and assign it to 0, then it is not overwritten. But the documentation does not tell that this is the case.

    From kudo:

    Build: 78.11022.3613.0 (525cf0677f)

    Azure App Service: 78.0.8598.65 (rd_websites_stable.181025-1653)

    Our other sites still use version 77.x, where it is working.



    Wednesday, October 31, 2018 2:26 PM

All replies

  • Hi Mikkel,

    We are investigating and will update this thread as we make findings. It definitely does look like a regression in the latest update.

    For now, you are using the best workaround by explicitly setting it to 0 on Production.


    Wednesday, October 31, 2018 2:52 PM
  • Hi Mikkel,

    The issue has been confirmed, and a fix is on the way. It should be deployed in the next day or two.

    Thanks for reporting this to us!


    Thursday, November 1, 2018 12:02 AM
  • Hi David,

    Awesome and thanks for quick response


    Thursday, November 1, 2018 6:40 AM
  • Mikkel, the fix has now been deployed, so you should no longer be experiencing this issue.


    Friday, November 2, 2018 3:56 AM
  • Not sure if this fix is related but also experiencing issues with Slot settings now after the 4.7.2 update. 


    Basically our production slot values overwrote our staging slot values so both instances had the same slot values. Bit of a major bug, this then also caused issues swap slots with internal error within the portal.

    Our App Service instance is pretty old , its been using the same configuration for 2+ years now.   

    The fix at the moment was to setup a brand new app service. 


    Micatio Software Free IIS Azure Web Log App

    Friday, November 2, 2018 11:01 PM
  • @Ron: are you still seeing issues now if you set the values correctly and try again? And did the staging slot have different values for the affected app setting, or did it not have that app setting at all?


    Friday, November 2, 2018 11:11 PM
  • Hi David,

    I can confirm it is working as expected again.



    Monday, November 5, 2018 10:31 AM