app services
213 TopicsAzure App Service Environments Internal and External access
I am looking to deploy a internal Intranet site and an external internet site and i would like to try and use Azure Web Apps to do this. The intranet should only be accessible from internal networks however the public facing website will obviously need to be accessible from anywhere. At the moment it is looking like i would need to deploy an App Service Environment and host the intranet site in there but it would be nice if i could then create a separate app and host that from within the same ASE. I suspect i could do it if i put a web application gateway on the network with a public IP but i want to try and avoid that as it is additional management and overhead. How have others done this? Do you just host Web Apps using multiple app service plans?2.7KViews0likes1CommentAzure support team not responding to support request
I am posting here because I have not received a response to my support request despite my plan stating that I should hear back within 8 hours. It has now gone a day beyond that limit, and I am still waiting for assistance with this urgent matter. This issue is critical for my operations, and the delay is unacceptable. The ticket/reference number for my original support request was 2410100040000309. And I have created a brand new service request with ID 2412160040010160. I need this addressed immediately.994Views2likes11Commentsπ Azure Application Gateway: Smart Load Balancing & Security
Ensuring high availability and efficient load balancing is crucial for web applications. Azure offers several traffic management solutions, including Application Gateway, Front Door, Load Balancer, and Traffic Manager. Today, let's focus on why Application Gateway stands out as a powerful tool for managing web traffic. π Why we should use Azure Application Gateway? πΉ Layer 7 Load Balancing: Unlike Layer 3 or 4 solutions, Application Gateway makes intelligent routing decisions based on HTTP request properties. For example, requests to /images/ can be directed to dedicated image servers, while /videos/ traffic is routed to specialized video servers. πΉ SSL/TLS Termination (Offloading): Reduces processing load on backend servers by decrypting traffic at the gateway before forwarding it unencrypted. Note: This might conflict with compliance requirements, so verify your appβs security needs !! πΉ Autoscaling: Dynamically scales up or down based on traffic patterns, ensuring cost-effective resource utilization. πΉ Zone Redundancy: Operates across multiple Availability Zones, enhancing fault tolerance without needing separate gateways in each zone. πΉ Web Application Firewall (WAF): Provides centralized security against common exploits like SQL injection and cross-site scripting (XSS). Built on OWASP 3.1 (WAF_v2), it can function in Detection Mode (alerting admins) or Prevention Mode (blocking threats proactively). πΉ URL-Based Routing: Enables smart traffic distribution by directing different types of content to the most appropriate backend pools. Example: http://contoso.com/video/* β VideoServerPool πΉ Multiple-Site Hosting: Hosts multiple web applications on a single gateway, routing requests based on hostname or domain. Example: http://contoso.com β ContosoServerPool πΉ Redirection & Rewrite Capabilities: β Redirect HTTP β HTTPS to enforce encrypted traffic. β Rewrite HTTP headers & URLs to enhance security (e.g., add HSTS or remove sensitive response headers). πΉ Cookie-Based Session Affinity: Ensures users maintain session continuity by always connecting to the same backend server. Useful when session state is stored locally. βοΈ How to Deploy & Configure Azure Application Gateway βοΈ β Dedicated Subnet: Create a subnet (e.g., myAGSubnet) within a Virtual Network. β Frontend IP: Define whether to use a public or private IP or both (If you configured multiple listeners) to receive client requests. β Backend Pool: Assign backend servers via NICs, Virtual Machine Scale Sets, public/internal IPs, or FQDNs. β HTTP/HTTPS Listener: Specify which port (e.g., 80, 443) will handle incoming requests. β Routing Rules: Set up domain-based (host-based routing) or path-based routing logic. πΉ Host-Based Routing means routing traffic based on the hostname in the HTTP request header πΉ Path-based Routing allows you to direct traffic to different backend pools based on the URL path in the request. β Health Probes: Ensure backend servers are online using TCP or HTTP-based monitoring.203Views1like1CommentApplying DevOps Principles on Lean Infrastructure. Lessons From Scaling to 102K Users.
Hi Azure Community, I'm a Microsoft Certified DevOps Engineer, and I want to share an unusual journey. I have been applying DevOps principles on traditional VPS infrastructure to scale to 102,000 users with 99.2% uptime. Why am I posting this in an Azure community? Because I'm planning migration to Azure in 2026, and I want to understand: What mistakes am I already making that will bite me during migration? THE CURRENT SETUP Platform: Social commerce (West Africa) Users: 102,000 active Monthly events: 2 million Uptime: 99.2% Infrastructure: Single VPS Stack: PHP/Laravel, MySQL, Redis Yes - one VPS. No cloud. No Kubernetes. No microservices. WHY I HAVEN'T USED AZURE YET Honest answer: Budget constraints in emerging market startup ecosystem. At our current scale, fully managed Azure services would significantly increase monthly burn before product-market expansion. The funding we raised needs to last through growth milestones. The trade: I manually optimize what Azure would auto-scale. I debug what Application Insights would catch. I do by hand what Azure Functions would automate. DEVOPS PRACTICES THAT KEPT US RUNNING Even on single-server infrastructure, core DevOps principles still apply: CI/CD Pipeline (GitHub Actions) β’ 3-5 deployments weekly β’ Zero-downtime deploys β’ Automated rollback on health check failures β’ Feature flags for gradual rollouts Monitoring & Observability β’ Custom monitoring (would love Application Insights) β’ Real-time alerting β’ Performance tracking and slow query detection β’ Resource usage monitoring Automation β’ Automated backups β’ Automated database optimization β’ Automated image compression β’ Automated security updates Infrastructure as Code β’ Configs in Git β’ Deployment scripts β’ Environment variables β’ Documented procedures Testing & Quality β’ Automated test suite β’ Pre-deployment health checks β’ Staging environment β’ Post-deployment verification KEY OPTIMIZATIONS Async Job Processing β’ Upload endpoint: 8 seconds β 340ms β’ 4x capacity increase Database Optimization β’ Feed loading: 6.4 seconds β 280ms β’ Strategic caching β’ Batch processing Image Compression β’ 3-8MB β 180KB (94% reduction) β’ Critical for mobile users Caching Strategy β’ Redis for hot data β’ Query result caching β’ Smart invalidation Progressive Enhancement β’ Server-rendered pages β’ 2-3 second loads on 4G WHAT I'M WORRIED ABOUT FOR AZURE MIGRATION This is where I need your help: Architecture Decisions β’ App Service vs Functions + managed services? β’ MySQL vs Azure SQL? β’ When does cost/benefit flip for managed services? Cost Management β’ How do startups manage Azure costs during growth? β’ Reserved instances vs pay-as-you-go? β’ Which Azure services are worth the premium? Migration Strategy β’ Lift-and-shift first, or re-architect immediately? β’ Zero-downtime migration with 102K active users? β’ Validation approach before full cutover? Monitoring & DevOps β’ Application Insights - worth it from day one? β’ Azure DevOps vs GitHub Actions for Azure deployments? β’ Operational burden reduction with managed services? Development Workflow β’ Local development against Azure services? β’ Cost-effective staging environments? β’ Testing Azure features without constant bills? MY PLANNED MIGRATION PATH Phase 1: Hybrid (Q1 2026) β’ Azure CDN for static assets β’ Azure Blob Storage for images β’ Application Insights trial β’ Keep compute on VPS Phase 2: Compute Migration (Q2 2026) β’ App Service for API β’ Azure Database for MySQL β’ Azure Cache for Redis β’ VPS for background jobs Phase 3: Full Azure (Q3 2026) β’ Azure Functions for processing β’ Full managed services β’ Retire VPS QUESTIONS FOR THIS COMMUNITY Question 1: Am I making migration harder by waiting? Should I have started with Azure at higher cost to avoid technical debt? Question 2: What will break when I migrate? What works on VPS but fails in cloud? What assumptions won't hold? Question 3: How do I validate before cutting over? Parallel infrastructure? Gradual traffic shift? Safe patterns? Question 4: Cost optimization from day one? What to optimize immediately vs later? Common cost mistakes? Question 5: DevOps practices that transfer? What stays the same? What needs rethinking for cloud-native? THE BIGGER QUESTION Have you migrated from self-hosted to Azure? What surprised you? I know my setup isn't best practice by Azure standards. But it's working, and I've learned optimization, monitoring, and DevOps fundamentals in practice. Will those lessons transfer? Or am I building habits that cloud will expose as problematic? Looking forward to insights from folks who've made similar migrations. --- About the Author: Microsoft Certified DevOps Engineer and Azure Developer. CTO at social commerce platform scaling in West Africa. Preparing for phased Azure migration in 2026. P.S. I got the Azure certifications to prepare for this migration. Now I need real-world wisdom from people who've actually done it!148Views0likes1CommentIs there no way to get better support for Azure - esp for SEV A tickets
We have had a sev A ticket open for over 5 days, and are incurring thousands in losses every day, and despite assurances from the Azure Support that it is being solved in hours and then having confirmations that it is solved, the issue is still not solved. I have asked numerous times to get our teams in touch with actual microsoft employees, not front end contractors, who is more like level 1 support, and just running messages between customer and back end team, and really are powerless to handle any suport issues themselves, and they are on complete mercy of "other teams" yet as a customer, apparantly we cant even get on a call with these other teams, and the poor front end contractors are getting the brunt of our pain. Absolutely are in the dark, as to what is actually happening in the back end, other than "trust me bro" we are working on it. No eta, no explanation.. hard to fathom how this can go on like this165Views2likes5CommentsPDF generation in Azure App Service
I'm looking for a solid option for PDF generation that is compatible with running within the constraints of Azure App Service or Azure Functions. I know of several options but am curious what others are using and having solid reliable success with?7.1KViews2likes4CommentsReplicate workload from VMWare to Azure using Azure Site Recovery(ASR)
Hello, I am working on a project to replicate worklooad hosted on a VMWare to Azure Site Recovery for disaster recovery purpose. Current Environment: More than 80 VMs hosted on VMWare managed by VMWare Sphere running both Linux and Windows OS.. Databases: Oracle DB, Microsoft SQL and MySQL Requirements: seamless failover and disaster recovery requirements. scalable setup No down-time integrate identity and access mgt. integration with Microsoft Entra ID. RTO < 2 hrs and RPO > 15 minutes Backup: critical database backup every 3 hours App servers: Daily*incremental) and weekly (full) Transaction Logs: every 10 mins backup config. should be Daily Questions I have confirmed ASR supports fail back from Azure- on premise(VMWare specifically). Hence ASR(Azure site recovery) will be used for the project. However, what is the seamless method to replicate the databases(Oracle, Microsoft SQL and MySQL). https://learn.microsoft.com/en-us/azure/site-recovery/vmware-azure-failback What is the best approach to replicate the Application Servers? integrating existing on-premise 3rd party network security tool for firewall etc instead of the azure cloud native security tool. recommendation?? cost optimization techniques/recommendations Best practices for conducting non-destructive DR drills.215Views0likes2CommentsIngesting Logs through Azure Private Link
Hi, We are currently using Azure Private Link within our environment and we are attempting to ingest logs into Log Analytics. When I reached out to Microsoft Support, it appears that the CCF connectors will not work using Private Link and the Azure Functions connectors are becoming depricated. Has anyone else run into this issue and what is the solution for getting logs into Sentinel through the Private Link, specifically API log sources? Did this require a custom app for each of these log sources or some sort of custom script that lives on an AMA host within the Private Link to ingest the logs? Any advice here would be greatly appeciated. Thank you,131Views0likes4CommentsRemote debug options for Linux container on App Services
We run .Net hosted on Linux Docker containers running in App Service. This makes debugging very difficult as while there is an option for remote debugging, this is only for Windows containers. https://learn.microsoft.com/en-us/visualstudio/debugger/remote-debugging-azure-app-service?view=visualstudio The only option I can find for Linux is the one detailed in the link below from 2018 which involves running an SSH server in the Docker container and using an extension which doesn't seem to have a stable version. az extension add --name webapp az : WARNING: No stable version of 'webapp' to install. Preview versions allowed. https://azure.github.io/AppService/2018/05/07/New-SSH-Experience-and-Remote-Debugging-for-Linux-Web-Apps.html Are there any currently supported options for remote debugging in Linux containers? Are there any plans to introduce the remote debug feature for Linux App Services?108Views0likes3CommentsWhen Words Matter Noise-Free, Domain-Specific Voice Recognition with Azure Custom Speech
As voice-driven technologies continue to transform how users interact with applications, delivering accurate, natural, and noise-resilient speech recognition has become essential. From virtual assistants and customer service bots to voice-controlled industrial systems, users expect speech interfaces that just work β even in noisy environments or when complex technical terms are spoken. Thatβs where Azure Custom Speech comes in. It allows you to tailor Azureβs Speech-to-Text service for your specific domain by training it to handle background noise, unique terminology, and diverse accents β enabling seamless and reliable voice experiences across industries. https://dellenny.com/when-words-matter-noise-free-domain-specific-voice-recognition-with-azure-custom-speech/46Views0likes0Comments