An Azure service that enables the connection of on-premises networks to Azure through site-to-site virtual private networks.
Hello chenouili
An IKE Phase 1 DELETE message sent by Azure does not necessarily indicate an Azure VPN Gateway issue. It can be part of normal Security Association (SA) expiration, rekeying, Dead Peer Detection (DPD), or gateway failover.
Azure VPN Gateway uses a fixed IKE Phase 1 lifetime of 28,800 seconds (8 hours), which cannot be modified.
Verify in your end:
- Identify the disconnection interval. If tunnels disconnect approximately every 8 hours, investigate Phase 1 rekeying first. Compare the FortiGate Phase 1 lifetime and rekey timing with Azure's fixed lifetime.
- Verify IKE/IPsec settings: IKE version, encryption/integrity algorithms, DH/PFS groups, Phase 2 lifetime, and traffic selectors. Both peers must have compatible settings.
- Check DPD and network stability. Azure recommends a DPD timeout of approximately 30–45 seconds. Also verify UDP 500/4500 connectivity and NAT-T behavior.
- Enable Azure VPN Gateway diagnostic logs, especially
IKEDiagnosticLogandTunnelDiagnosticLog, and correlate the exact disconnect timestamps with FortiGate IKE debug logs. This helps distinguish failed rekeying, DPD timeouts, and Azure gateway failover.
Do not assume that Azure caused the failure simply because FortiGate received a DELETE message. The preceding IKE exchanges and Azure diagnostics are needed to determine why the SA was deleted.
If both FortiGate tunnels disconnect simultaneously, also investigate Azure gateway maintenance/failover and any shared network dependencies.
If the logs show Azure initiating unexpected DELETE messages without SA expiration, DPD failure, or failover, open an Azure VPN Gateway support request with the exact UTC timestamps and correlated logs.
Official Microsoft documentation: