Unable to reach specific destination/subnet within Azure

PA-VM is deployed within a VNET in Azure and traffic from host residing in directly connected subnet with default route as the firewall interface is unable to reach a destination IP. 
 

• Log in to the firewall CLI and execute below CLI command:

> show counter global filter delta yes

name             value rate severity category aspect description
--------------------------------------------------------------------------------
pkt_recv            6  0 info   packet    pktproc   Packets received
flow_policy_nofwd   6  0 drop   flow      session   Session setup: no destination zone from forwarding

• Above CLI output shows packets were dropped during session establishment as the destination zone was not found during forwarding lookup

• Verify if routes exist for the destination in question using below CLI:

> show routing route destination 4.2.2.2/32

VIRTUAL ROUTER: default (id 1)
  ==========
destination                                 nexthop                                 metric flags      age   interface          next-AS   
total routes shown: 

• Above CLI output confirms routes are not present for the destination.

• Verify if default route is present on the routing table using “show routing route”

• Platform: VM-Series Firewall
• PAN-OS / Plugin Version: 8.1.10 / -
• Deployment: Azure

• Route for the destination is missing on the RIB (Routing Information Base)

1. Configure a static route for the destination pointing towards the first IP of the Azure subnet in which the egress interface resides
2. Alternatively, if default route itself is missing, either configure the default route as the first IP of the egress interface subnet or enable “Automatically create default route pointing to default gateway provided by server” option under Network > Interfaces > ethernet1/x > IPv4 to learn the default route from the egress subnet