Comment 4 for bug 1843634

The original description certainly indicates that cloud-init still writes an "empty" resolv.conf file. However this issues has been addressed for a while thus something does not fit together. It makes no sense that this would only show up in Azure and in the bug that triggered investigation and ultimately led to a fix it has been confirmed as fixed.