This seems like a bigger problem in that none of the production settings are being honored at all.
I think I know what the problem is. https://github.com/ManageIQ/manageiq-providers-azure/blob/master/config/settings.yml#L32 contains an empty Array as the default, and the production.yml override is being evaluated at a lower precedence for some reason.
https://github.com/ManageIQ/manageiq/pull/16535
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/63759e4176421b7189af7fe7aa1c83e60f322a81 commit 63759e4176421b7189af7fe7aa1c83e60f322a81 Author: Jason Frey <jfrey> AuthorDate: Mon Nov 27 18:07:12 2017 -0500 Commit: Jason Frey <jfrey> CommitDate: Mon Nov 27 18:11:10 2017 -0500 Fix issue where plugin settings had higher precedence than manageiq One of the side effects of this is that in production deployments with overrides, the overrides were being clobbered by the plugins. https://bugzilla.redhat.com/show_bug.cgi?id=1517938 lib/vmdb/settings.rb | 16 +++++++--------- 1 file changed, 7 insertions(+), 9 deletions(-)