The problem described in #18543 was caused by the use of @ConfigurationProperties when the intention was to use constructor binding. The result was Framework trying to create the bean and failing as its constructor's dependencies could not be satisfied. We may be able to improve NoSuchBeanDefinitionFailureAnalyzer to look for @ConfigurationProperties and suggest adding @ConstructorBinding as a possible course of action.