Assuming you are creating a new package version in the portal, are you updating the pool spec to reflect the new version? Such changes will only beĪpplied to new compute nodes joining the pool, or on a reboot. It sounds like this might be an issue where you are specifying app packages at the pool level. Revving the program's internal version number and re-uploading in place. From your description, I think this is what you're doing, but just wanted to double check that you weren't just The package itself a different version number - that is, specifying a new version number in the portal (or PowerShell or whatever).
To confirm, by 'new versions' I mean are you uploading a new zip file and giving
