Hello @CHUNSIK KIM ,
Azure PaaS services are multi-tenant shared services and they exist outside your Vnet and span across the Microsoft network but a Firewall or NVA is always deployed within your Vnet.
Connectivity to Microsoft online services (Office 365 and Azure PaaS services) occurs through Microsoft peering. And this traffic goes through the Azure backbone and not through your Vnet.
Please refer the diagram in the following article for clarity : https://learn.microsoft.com/en-us/azure/expressroute/expressroute-circuit-peerings#routingdomains
Hence, the traffic on Microsoft peering would take the Microsoft backbone network and communicate directly with PaaS service resources.
However, if you would like to access the Azure PaaS Services from your on-premises privately, you may opt for Azure Private link/Endpoint. There's no need to set up public/Microsoft peering or traverse the internet to reach the service. Private Link provides a secure way to migrate workloads to Azure.
Please refer : https://learn.microsoft.com/en-us/azure/private-link/private-link-overview
https://learn.microsoft.com/en-us/azure/private-link/private-endpoint-overview
Hope this helps!
Kindly let us know if the above helps or you need further assistance on this issue.
----------------------------------------------------------------------------------------------------------------
Please don’t forget to "Accept the answer" wherever the information provided helps you, this can be beneficial to other community members.