Hi @航 鈴木,
You're currently restricting access to your Azure Web App using a whitelist of internal network IPs under:
Settings > Networking > Access restrictions
This works well inside your corporate network, but you want to allow specific users to securely access the Web App from outside (e.g., remote work, travel). Whitelisting external user IPs is not practical, since those IPs are often dynamically assigned via DHCP. You thought about using a jump server (bastion host), but securing access to that jump server is a challenge in itself.
Instead of relying on static IP-based restrictions, you can enable authentication and identity-based access controls, which scale much better and offer enterprise-grade security.
- Configure your Web App to require login using Azure AD. This ensures only authenticated users can access it, regardless of where they're connecting from. Secure an app with Azure AD authentication - Azure App Service
- Use Azure AD Conditional Access to define policies such as: Allow access only from compliant devices, Block access from unknown countries, Require MFA for external users, require access from Intune-managed or Hybrid Azure AD joined devices Conditional Access in Azure Active Directory
- If you want network-level control in addition to identity controls, use Azure Private Endpoint to expose the app only in your VNet, and users can connect securely via VPN or Azure Virtual Desktop. Private Endpoint for Azure App Service
- Or use Azure Front Door with Web Application Firewall (WAF) and IP restrictions. Restrict access with Front Door and WAF
Why This is a Better Approach:
Feature | IP Whitelisting | Azure AD + Conditional Access |
---|---|---|
Dynamic user IPs support | no | yes |
Per-user access control | no | yes |
MFA and device compliance | no | yes |
Scalable and maintainable | no | yes |
If the answer is helpful, please click Accept Answer and kindly upvote it so that other people who faces similar issue may get benefitted from it.
Let me know if you have any further Queries.