Microsoft Azure — an archived discussion from the APG vNext support community.
About This Topic
This thread covers microsoft azure in the context of APG vNext, the ASP.NET forum and community platform. The community includes APG developers and experienced administrators who can help with similar questions.
APG vNext Support
- Knowledge Base — documented solutions
- FAQ — frequently asked questions
- Installation Guide
- Upgrade Guide
- Support Forum
Deploying APG vNext on Microsoft Azure
APG vNext can be deployed on Microsoft Azure using Azure App Service for the web application layer and Azure SQL Database for the relational database tier. Azure provides a managed infrastructure that handles server patching, auto-scaling, built-in backup, and global distribution through Azure CDN, making it a strong choice for communities that need reliable uptime and low-latency access for geographically distributed members.
Azure App Service Configuration
Create an Azure App Service plan at the B2 tier or higher for a production forum. The Free and Shared tiers are insufficient for production because they do not support custom domains, SSL certificates, or the Always On setting that prevents application pool recycling during periods of low traffic. Enable Always On under App Service Configuration > General Settings to prevent the forum from cold-starting when users visit after a quiet period, which would cause a noticeable delay on the first request after the pool has been recycled by the Azure infrastructure.
Azure SQL Database Setup
Create an Azure SQL Database using the General Purpose tier with at least 2 vCores for a production forum. The Serverless tier is not recommended for APG vNext because the auto-pause feature causes cold start delays that affect forum responsiveness. Configure the connection string in Azure App Service Application Settings rather than in web.config directly, using the Azure SQL connection string format with Integrated Security=False and the SQL administrator credentials. Azure SQL does not support Windows Integrated Authentication from App Service without additional network configuration.
Azure CDN for Static Assets
Configure Azure CDN to cache and serve APG vNext's static assets including CSS, JavaScript, images, and user-uploaded attachments. Point the CDN origin at your App Service endpoint and configure the appropriate cache rules for each asset type. Static assets with versioned URLs can be cached indefinitely. Page HTML should not be CDN-cached to ensure members always see current content. CDN distribution significantly reduces the load on your App Service instance and improves page load times for users accessing the forum from geographic regions far from your primary Azure region.
Deployment and CI/CD
Use Azure DevOps or GitHub Actions to automate APG vNext deployments from a source code repository to Azure App Service. Configure deployment slots to enable a blue-green deployment pattern where new versions are deployed to a staging slot, validated, and then swapped to production with zero downtime. This approach allows you to roll back a bad deployment instantly by swapping the slots back, providing a safety net for every APG vNext upgrade or configuration change deployed to the platform.
APG vNext's configuration options for this feature are designed to be flexible enough to accommodate the needs of small hobbyist communities as well as large enterprise deployments running on dedicated server hardware. When in doubt about the right settings for your specific deployment context, consult the official APG vNext documentation in the Knowledge Base or ask in the community support forum where experienced administrators share their configurations and provide guidance based on real-world deployment experience across many different server environments and community sizes. APG vNext's configuration options for this feature are designed to be flexible enough to accommodate the needs of small hobbyist communities as well as large enterprise deployments running on dedicated server hardware. When in doubt about the right settings for your specific deployment context, consult the official APG vNext documentation in the Knowledge Base or ask in the community support forum where experienced administrators share their configurations and provide guidance based on real-world deployment experience across many different server environments and community sizes. APG vNext's configuration options for this feature are designed to be flexible enough to accommodate the needs of small hobbyist communities as well as large enterprise deployments running on dedicated server hardware. When in doubt about the right settings for your specific deployment context, consult the official APG vNext documentation in the Knowledge Base or ask in the community support forum where experienced administrators share their configurations and provide guidance based on real-world deployment experience across many different server environments and community sizes. APG vNext's configuration options for this feature are designed to be flexible enough to accommodate the needs of small hobbyist communities as well as large enterprise deployments running on dedicated server hardware. When in doubt about the right settings for your specific deployment context, consult the official APG vNext documentation in the Knowledge Base or ask in the community support forum where experienced administrators share their configurations and provide guidance based on real-world deployment experience across many different server environments and community sizes.Looking for more help? Browse the support forum or check the Knowledge Base.