| Description | This article describes the reason for communication to link-local address 169.254.169.254 from FortiGate VM on public cloud (Azure). |
| Scope | FortiGate VM on Azure cloud. |
| Solution |
This IP 169.254.169.254 is the Azure Instance Metadata Service (IMDS) endpoint. IMDS is a REST API that's available at a well-known, non-routable IP address (169.254.169.254). When a VM or VMSS instance tries to query metadata (licensing, config injection, identity tokens, instance info, bootstrap information, etc.), it contacts 169.254.169.254. If that connection times out, it means the VM cannot reach IMDS, which normally should always be reachable from inside the VM instance.
In FortiOS, the status of the service can be verified by running the following command:
diagnose debug cloudinit show
Additionally, the following debug commands can be used to check the service status or for any errors:
diagnose debug reset
For example, if the metadata connection fails, the following error will be visible in the debug logs:
2025-10-23 11:06:21 azd connection timeout: 169.254.169.254:80:169.254.169.254
In the above example, logs FortiGate VM on Azure did not receive any response to its query to the Azure metadata service hosted on link-local address 169.254.169.254, resulting in a connection timeout. |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.