This sure looks like a variant of exactly the same problem you had before:
The giveaway here is:
org.neo4j.kernel.impl.store.UnderlyingStorageException: java.io.IOException: Permission denied
Again, I'm not sure how Azure storage works, but that's where to look. This suggests that when you scaled to zero and then scaled back to 1, something about the file permissions changed. I don't really know what would have happened, because it probably has to do with either the way you set up the kubernetes pod, or the way Azure storage works. But at a minimum -- that error is ultra clear. The Neo4j process inside of the docker container doesn't have permissions to write data to necessary files.
Something changed in the scaling operation.