To begin with, I have read and followed this article. http://blogs.msdn.com/b/mast/archive/2014/07/01/unable-to-add-vm-agent-extension-to-azure-vm.aspx.
However, removing the VM from an availability group, adding the Access Agent, and re-adding the VM to the availability group seems to work for a while. It appears as if, once the VM is restarted (via the portal), it again make the Access Agent "not ready" with the error above (title).
I have uninstalled and reinstalled the Access Agent all three ways that I know of:
1. Using PowerShell
2. Using the MSI
3. Using the preview portal.
I get the same results each way.
Any guidance or suggestions would be greatly appreciated.