Nothing special for azure, and I assume the source package was not built against the previous version, hence the verification is triggered again.
Nothing special for azure, and I assume the source package was not built against the previous version, hence the verification is triggered again.