Thinking more about this, I believe it is a valid design choice to have the IOptionsAccessor give you just be a singleton and return always the same option object snapshotted the first time it was accessed. If anything, it should perform well for the most common case :smile: Then you need to push other more "dynamic" requirements somewhere else. I am just a bit disappointed that we will need to come up with yet another pattern or custom solution for those. It looks to me that enabling scoped IOptionsSetups would have addressed those scenarios.