![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(291.2, 64%, 38%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKK%3C/text%3E%3C/svg%3E)
Azure Migrate
A central hub of Azure cloud migration services and tools to discover, assess, and migrate workloads to the cloud.
849 questions
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(185.6, 63%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAG%3C/text%3E%3C/svg%3E)
Welcome to Microsoft Q&A Forum, thank you for posting your query here!
Yes, you can proceed with the replication even though the IP address 168.63.129.16 is not accessible from the Internet or on-premises locations. This IP address is used by Azure for various internal operations, such as health probes and DNS resolution, and it is expected to be inaccessible from external networks
The "Azure ready" state in the Azure Migrate portal indicates that the VM assessment has successfully validated the necessary prerequisites for migration
Why You Can Ignore This for Now:
1.Azure Metadata Endpoint is Azure-Only:
- The IP address 168.63.129.16 serves as a metadata endpoint in Azure, and it is only accessible from within the Azure network. You're on-premises VM cannot communicate with it, which is why the Azure Linux Agent (waagent) logs these errors. Refer: https://zcusa.951200.xyz/en-us/azure/virtual-network/what-is-ip-address-168-63-129-16?utm_source=chatgpt.com
2.No Impact on Migration:
- This issue does not affect the replication or migration process. Azure Migrate will still capture and replicate the VM's configuration and disks to Azure Storage without requiring connectivity to 168.63.129.16.
3.Post-Migration Resolution:
- Once the VM is successfully migrated to Azure and powered on, it will have access to the Azure network and should be able to communicate with the metadata endpoint. The waagent should function normally at that point.
Please let me know if any face any challenges while performing migration i am happy to assist you further
let us know if you have any further queries. I’m happy to assist you further.
Please do not forget to "Accept the answer” and upvote it wherever the information provided helps you, this can be beneficial to other community members.it would be greatly appreciated and helpful to others.