3/14: Major progress with having CAPZ successfully provision VMs. Prior to this VMs were failing with unhelpful error which was ultimately caused by missing os disk! CAPZ is able to create machines which look good in the cloud, but working through an issue where CAPZ does not declare the VMs created because it has a client error when trying to reconcile tags. Once VM issue is resolved, we should be able to take the PR upstream. Also worked through several installer-specific infrastructure issues. It seems that none of the newer azure storage SDK packages, which we used to write the installer azure infrastructure provisioning support overriding API versions compatible with Azure Stack, so I needed to rewrite storage account, ignition upload, and managed disk creation specifically for Azure Stack with the old sdk. This is all done at the PoC level so wil need some further refactoring. There's a lot of work to be done, but the unknowns are decreasing significantly. 2/12: PoC has successfully provisioned non-VM infrastructure but CAPZ fails to provision VMs with an uninformative "500 Internal Service error." Debugging has yielded no results. During upcoming sprint planning, we will consider implementing SDK-based VM provisioning so that we can land the rest of the azure stack implementation while buying time to continue to debug the CAPZ VM issue.