Deploying a Web App on Azure App Service
At the heart of this post is Kairos IMS, an innovative Impact Management System designed to empower human-serving nonprofits and social impact organizations. Co-developed by the Urban League of Broward County and our trusted technology partner, Impactful, Kairos IMS reduces administrative burdens, enhances holistic care, and enables organizations to leverage data for increased agility and seamless service delivery. In this blog series, we’ll take a closer look at the powerful technologies that fuel Kairos IMS, from Azure services to security frameworks, offering insight into how modern infrastructure supports mission-driven impact. Click here to learn more. Azure App Service is a powerful platform for building, deploying, and scaling web apps. It supports multiple languages and frameworks, making it a versatile choice for developers. In this guide, we'll walk you through the process of deploying a web app on Azure App Service. Step 1: Prerequisites Before you start, ensure you have the following: An Azure account with an active subscription. If you don't have one, you can create a free account. Your web app code ready for deployment. Visual Studio or any other development environment you prefer. Step 2: Create an App Service Log in to the Azure Portal: Go to portal.azure.com and sign in with your Azure account Create a Resource: Click on "Create a resource" and select "Web App." Creating Your Web App: Subscription: Choose your subscription. Resource Group: Select an existing resource group or create a new one. App Name: Enter a unique name for your app. Publish: Choose "Code" if you're deploying code directly, or "Docker Container" if you're using a container. Runtime Stack: Select the runtime stack that matches your web app (e.g., .NET, Node.js, Python). Region: Choose the region closest to your users. Pricing Plans: When creating your Web App, Azure will also ask you to create or select an App Service Plan, which defines the pricing tier and performance level for your app. Finish the steps and click "Review + create." 4. Completing Deployment: You will see a message letting you know your deployment is complete. Step 3: Deploy Your Web App Deployment Center: Once your deployment is complete, click on "Go to Resources" and navigate to the "Deployment Center" in your App Service. Source Control: Choose your source control method (e.g., GitHub, Bitbucket, Azure Repos). 3. Build Provider: Select the build provider (e.g., GitHub Actions, Azure Pipelines). 4. Configure Settings: Follow the prompts to configure your deployment settings. This includes connecting your repository and setting up continuous integration/continuous deployment (CI/CD) pipelines. Step 4: Monitor and Scale Your App Monitor: Use Azure Monitor to keep track of your app's performance and health. Set up alerts to notify you of any issues. To learn more about Azure Monitor, please visit: Monitor Azure App Service - Azure App Service | Microsoft Learn Scale: Azure App Service allows you to scale your app based on demand. Navigate to the "Scale up" or "Scale out" options to adjust your app's resources. To learn more about scaling, please visit: Scale up features and capacities - Azure App Service | Microsoft Learn Step 5: Manage Your App App Settings: Configure application settings, connection strings, and environment variables in the "Configuration" section. To learn more about configuring your app settings, please visit: Configure an App Service App - Azure App Service | Microsoft Learn SSL Certificates: Secure your app with SSL certificates. Navigate to "TLS/SSL settings" to configure SSL bindings. To learn more about SSL Certificates, please visit: https://learn.microsoft.com/en-us/azure/app-service/configure-ssl-bindings Conclusion Deploying a web app on Azure App Service is a streamlined process that integrates well with various development tools and workflows. By following these steps, you can easily deploy, monitor, and scale your web app, ensuring a robust and reliable online presence.Deploying a Web App on Azure App Service: A Comprehensive Guide
At the heart of this post is Kairos IMS, an innovative Impact Management System designed to empower human-serving nonprofits and social impact organizations. Co-developed by the Urban League of Broward County and our trusted technology partner, Impactful, Kairos IMS reduces administrative burdens, enhances holistic care, and enables organizations to leverage data for increased agility and seamless service delivery. In this blog series, we’ll take a closer look at the powerful technologies that fuel Kairos IMS, from Azure services to security frameworks, offering insight into how modern infrastructure supports mission-driven impact. Click here to learn more. Azure App Service is a powerful platform for building, deploying, and scaling web apps. It supports multiple languages and frameworks, making it a versatile choice for developers. In this guide, we'll walk you through the process of deploying a web app on Azure App Service. Step 1: Prerequisites Before you start, ensure you have the following: An Azure account with an active subscription. If you don't have one, you can create a free account. Create Your Azure Free Account Or Pay As You Go | Microsoft Azure Your web app code ready for deployment. Visual Studio or any other development environment you prefer. Step 2: Create an App Service Log in to the Azure Portal: Go to portal.azure.com and sign in with your Azure account. Create a Resource: Click on "Create a resource" and select "App Service." 3. Configure your Web App: Choose your subscription, resource group, App Name, publish, runtime stack, region, and etc. Once you have went through/reviewed all the necessary tab, select "review + create" to create your web app. Step 3: Deploy Your Web App Deployment Center: Navigate to the "Deployment Center" in your App Service. Source Control: Choose your source control method (e.g., GitHub, Bitbucket, Azure Repos). Build Provider: Select the build provider (e.g., GitHub Actions, Azure Pipelines). Configure Settings: Follow the prompts to configure your deployment settings. This includes connecting your repository and setting up continuous integration/continuous deployment (CI/CD) pipelines. Step 4: Monitor and Scale Your App Monitor: Use Azure Monitor to keep track of your app's performance and health. Set up alerts to notify you of any issues. Scale: Azure App Service allows you to scale your app based on demand. Navigate to the "Scale up" or "Scale out" options to adjust your app's resources. Step 5: Manage Your App App Settings: Configure application settings, connection strings, and environment variables in the "Configuration" section. SSL Certificates: Secure your app with SSL certificates. Navigate to "TLS/SSL settings" to configure SSL bindings. Conclusion Deploying a web app on Azure App Service is a streamlined process that integrates well with various development tools and workflows. By following these steps, you can easily deploy, monitor, and scale your web app, ensuring a robust and reliable online presence.Build faster with this simple AZD template for FastAPI on Azure App Service
The world of DevOps and deployment configuration options just keeps growing, but you just want to build your web app and get it out to the world! I created this Simple FastAPI AZD template for Azure App Service to help you get to the fun part while deploying it for free. Learn why and how to give it a go!Step-by-Step Guide: Migrating Your Nonprofit's WordPress Site to Azure
Migrating your nonprofit's WordPress site to Azure can significantly enhance its performance, security, and scalability. This guide will help you navigate the process smoothly, ensuring your website is up and running on Azure with minimal disruption. Why Migrate to Azure? Azure offers a range of benefits for nonprofits, including cost-effective solutions, robust security features, and the ability to scale resources as needed. By migrating to Azure, your nonprofit can leverage these advantages to better serve your mission and community. Prerequisites Before you begin, ensure you have: An Azure account and subscription (nonprofits can access Azure credits and grants). Administrative access to your current WordPress site. A backup of your WordPress site. Step 1: Backup Your WordPress Site Visit the wp-admin: To visit the admin portal of your current WordPress site, put /wp-admin after your website url. If your website is www.example.com just add www.example.com/wp-admin Using All-In-One WP Migration Plugin Press on Plugin then add Plugin Search for All-In-One WP Migration Left click on the plugin. Select export and use the plugin to create a backup of your site by exporting it to a file. Step 2: Deploy WordPress on Azure Create a Web App: Follow the first 2 articles from the series that will help you create a WordPress Site in Azure: Deploying Your Nonprofit's Website on Azure (Part 1) | Microsoft Community Hub Deploying Your Nonprofit's Website on Azure (Part 2) | Microsoft Community Hub Deploy WordPress: Use the All-In-One WP Migration plugin to import your site into the new Azure web app. Install the plugin on the new WordPress instance, then import the backup file you created earlier. If you encounter an error due to host restrictions on file sizes exceeding 50 MB, please refer to this article for detailed instructions on how to resolve the issue:Resolving Host Restrictions on File Sizes Exceeding 50 MB in WordPress on Azure for Nonprofits | Microsoft Community Hub. Step 3: Test and Optimize Test Your Site: Thoroughly test your WordPress site on Azure to ensure everything is functioning correctly. Check for broken links, missing files, and performance issues. Optimize Performance: Use Azure Monitor and Application Insights to identify and resolve any performance bottlenecks. Configure Auto-Scaling: Set up auto-scaling rules to automatically adjust resources based on traffic and demand. Step 4: Update DNS and Go Live Update DNS Records: Update your domain's DNS records to point to the new Azure web app. This may involve updating A records, CNAME records, or other DNS settings. Monitor the Transition: Keep a close eye on your site during the transition period to quickly address any issues that arise. Go Live: Once everything is working smoothly, officially switch over to the new Azure-hosted WordPress site. For steps on how to add a DNS record. follow this article: Deploying Your Nonprofit's Website on Azure (Part 3) | Microsoft Community Hub Conclusion Migrating your nonprofit's WordPress site to Azure can provide numerous benefits, including improved performance, enhanced security, and greater scalability. By following this step-by-step guide, you can ensure a smooth and successful migration, allowing your nonprofit to better serve its mission and community.Exploring Azure App Service
App Service – Managed Platform Building applications takes a lot of planning and consideration before you are unveiling your website. Continuous integration, dependencies, security measures, are vital to secure and scale applications. If you want to just focus on the code and not the infrastructure you may be looking at solutions that can help you do what you do best. Azure App Service is a fully managed platform offered by Microsoft Azure that allows developers to build, deploy, and scale web apps, mobile apps, and API apps effortlessly. As part of the Azure cloud platform, it provides a range of features and services designed to support the creation of a wide variety of applications, from simple websites to complex, multi-tiered solutions. Features & Capabilities Scalability: Automatically scale your applications up or down to handle varying loads efficiently. High Availability: Ensure your applications are always up and running with built-in high availability features and SLA guarantees. Continuous Integration & Deployment: Integrate with popular CI/CD tools such as GitHub, Azure DevOps, and Bitbucket to automate build and deployment processes. Global Reach: Deploy your applications in data centers all over the world to provide low-latency experiences for users everywhere. Security: Protect your applications with built-in security measures, including custom domains, SSL certificates, and authentication options. Hybrid Connections: Connect your Azure App Service applications to on-premises resources, enabling seamless hybrid cloud scenarios. Development Language Support: Develop applications using a variety of languages, including .NET, Java, Node.js, Python, PHP, and Ruby. Integrated Monitoring & Diagnostics: Gain insights into your application’s performance and health with integrated monitoring, logging, and diagnostics tools. Serverless Code: Run serverless functions with Azure Functions, integrated directly into Azure App Service for rapid and efficient code execution. Dev/Test Environments: Create isolated environments for development and testing to ensure your applications are production ready. Customizable PaaS: Leverage fully managed PaaS that allows customization to meet specific application requirements. Photo by Anna Nekrashevich Azure App Service Plans Explained Azure App Service Plans offer a range of pricing tiers designed to fit various app hosting needs. These plans allow you to scale your applications seamlessly, from small workloads to large enterprise-level applications. There are multiple plans to choose from based on your needs: Shared Free: The Free plan is ideal for experimenting with Azure App Service or for small, personal projects. It offers limited features and resources, making it suitable for basic web applications that do not require high performance or scalability. Shared: The Shared plan provides more resources and capabilities than the Free plan, but still shares resources with other applications. This plan is suitable for small to medium-sized applications that need more power but do not require dedicated resources. Dedicated Basic: The Basic plan offers dedicated resources for your applications, providing better performance and scalability. It is suitable for small to medium-sized applications that require dedicated resources without the need for advanced features. Standard: The Standard plan builds on the Basic plan by offering additional features such as auto scaling and integrated backup. This plan is ideal for medium-to-large-sized applications that need consistent performance and advanced features. Premium: The Premium plan provides even more resources and features, including advanced auto-scaling and higher performance. It is designed for large-scale applications that require high availability and advanced capabilities. PremiumV2: The PremiumV2 plan enhances the Premium plan with improved performance and additional features, making it suitable for mission-critical applications that demand the highest levels of performance and reliability. PremiumV3: The PremiumV3 plan is the latest and most advanced offering, providing the highest levels of performance, scalability, and features. It is designed for enterprise-level applications that require the utmost in reliability and capability. Isolated IsolatedV2: The IsolatedV2 plan offers dedicated resources in a completely isolated environment, ensuring maximum security and performance. It is ideal for applications that require stringent security measures and the highest levels of isolation from other resources by Kevin Ku Development Testing The Free tier of Azure App Service provides an excellent starting point for developers to plan and test their applications. Ideal for small, personal projects, this plan offers limited resources and features, making it perfect for experimenting with basic web applications. Developers can utilize this tier to explore the capabilities of Azure App Service, identifying potential improvements and refining their applications before transitioning to higher-tier plans that offer enhanced performance and scalability. The Free tier allows developers to deploy up to 10 apps with 1 GB of storage each, offering sufficient space to test various configurations and functionalities. By leveraging the Free tier, developers can gain valuable insights into the platform's integration with other Azure services, such as Azure SQL Database, Application Insights, and Azure DevOps, enabling them to streamline their development workflows and optimize their applications end-to-end. Conclusion In summary, Azure App Service offers a range of plans to cater to various application needs, from the free tier for development and testing to the robust PremiumV3 and IsolatedV2 plans for mission-critical and highly secure applications. Each plan provides unique features and performance levels, enabling developers and organizations to choose the most suitable plan for their specific requirements. By understanding the capabilities and benefits of each plan, users can effectively leverage Azure App Service to build, deploy, and scale their applications with confidence. Hyperlinks Azure App Service documentation - Azure App Service | Microsoft Learn Azure App Service Plans - Azure App Service | Microsoft Learn Basic web application - Azure Reference Architectures | Microsoft Learn Getting started with Azure App Service - Azure App Service | Microsoft LearnModernizing Legacy Applications in your Nonprofit
In this blog, we’ll explore how nonprofits can modernize their existing applications to enhance security without starting from scratch. By leveraging Microsoft Azure’s powerful tools, organizations can strengthen their defenses, improve performance, and ensure their applications remain secure and scalable for the future. Securing Legacy Applications Without Rebuilding from Scratch For many nonprofits, starting over isn’t an option—they need to secure and modernize the applications they already have. Fortunately, Microsoft Azure provides solutions that help organizations enhance security without requiring a complete rebuild: ✅ Containerization with Azure Kubernetes Service (AKS) – Nonprofits can containerize legacy applications and host them in a secure, scalable environment, reducing vulnerabilities without rewriting the entire application. This approach helps keep security updates and compliance requirements in check while maintaining the existing software functionality. ✅ Incremental Modernization with Cloud-Native Services – Instead of a full-scale rebuild, nonprofits can gradually modernize their applications by integrating cloud-native services. This could involve migrating databases to Azure SQL, implementing API-driven architectures, or introducing automation through Azure Logic Apps. This phased approach enhances security, improves performance, and allows for future scalability without disrupting core operations. ✅ Azure SQL Database – Helps nonprofits move from outdated, on-premises databases to a fully managed cloud database, reducing maintenance efforts while improving security, performance, and compliance. ✅ Azure API Management – Allows organizations to connect legacy systems with modern cloud-based services by securely exposing APIs, enabling seamless integration and extended functionality. Understanding Your Options When considering the modernization of legacy applications, there are several strategies that organizations can adopt, each with its own benefits and considerations: Rehost (Lift-and-Shift) This strategy is all about speed and simplicity. It involves moving applications from their current environment to a new one with minimal or no changes to the code. This allows organizations to quickly transition to the cloud without altering the core functionality of their applications. Replatform Replatforming sits between rehosting and refactoring. It requires making some code changes so that applications can take advantage of cloud technologies. This approach allows organizations to benefit from cloud capabilities without needing a complete overhaul of their applications. Refactor (or Repackage) Refactoring focuses on enhancing productivity and speed by making minimal code changes. This strategy ensures that applications can connect easily to a cloud-first environment, optimizing their performance and scalability. Rearchitect For organizations that need enhanced cloud scalability, rearchitecting is the way to go. This approach involves modifying and extending the application's functionality and code to better utilize cloud resources, ensuring improved performance and scalability. Rebuild (or Rewrite) When existing applications have limited functionality or lifespan, rebuilding them using cloud solutions might be necessary. Although this approach requires significant effort, it provides a fresh start with modern capabilities and extended lifespans. Replace If an application no longer meets current or future business needs, even after rebuilding, replacing it with a ready-made solution may be the best option. This approach can be quicker than rebuilding and allows organizations to focus on other priorities. However, it may also pose challenges such as business process interruptions and limitations on future modernization efforts. Nonprofit Considerations Wrapping up, we agree that nonprofits rely on technology to drive their missions, but outdated applications can pose serious security risks. We've covered how organizations don’t have to start from scratch to modernize and secure their systems. By leveraging Microsoft Azure’s powerful tools—like containerization, cloud-native services, and secure database management—nonprofits can enhance security, improve performance, and ensure long-term scalability. Here is one thing to consider: Nonprofits may not have the technical team to assist with these processes, but understanding these strategies is crucial. This knowledge can empower them in conversations with development partners, ensuring they are fully aware and engaged throughout the modernization journey. By being informed, nonprofits can make better decisions, ask the right questions, and collaborate effectively with their partners to achieve their modernization goals. Modernization isn’t just about keeping up with technology; it’s about protecting the trust nonprofits have built with their donors, volunteers, and communities. Whether it’s securing legacy applications or embedding security into new software development through the Secure Software Development Lifecycle (SSDLC), taking proactive steps today ensures a more resilient and secure future. On the contrary, for nonprofits that do want to start over from scratch with building new applications, integrating security from the start is essential. Learn more about how SSDLC can strengthen your organization’s software security here: Building Secure Software from the Ground Up: Why It Matters for Nonprofits | Microsoft Community Hub Want to explore nonprofit application modernization further? Check out this guide: What is Application Modernization? | Microsoft Azure.Building Secure Software from the Ground Up: Why It Matters for Nonprofits
What Is the Secure Software Development Lifecycle (SSDLC)? The Secure Software Development Lifecycle (SSDLC) integrates security into every phase of the traditional Software Development Lifecycle (SDLC). Instead of treating security as a final step before software deployment, SSDLC ensures that security measures are embedded from day one. This approach reduces vulnerabilities and strengthens nonprofit organizations against cyber threats. Key Phases of SSDLC and Why They Matter Planning & Requirements Identify security risks before development begins: This involves understanding potential threats and vulnerabilities that could affect the software. Define compliance needs: Ensure that the software meets regulatory requirements such as GDPR, HIPAA, and donor data protection. Design Use secure architecture principles to mitigate risks: Design the software with security in mind, incorporating principles that reduce potential risks. Implement encryption, authentication, and access control measures: Ensure that data is protected through encryption, and that only authorized users can access the system. Development Follow secure coding best practices: Prevent vulnerabilities like SQL injection, cross-site scripting (XSS), and unauthorized access by adhering to secure coding standards. Use automated security scanning tools: Detect issues early in the development process by employing tools that automatically scan for security vulnerabilities. Testing Conduct penetration testing, security audits, and code reviews: Uncover weaknesses by thoroughly testing the software's security. Simulate cyberattacks to test software resilience: Ensure the software can withstand real-world attacks by simulating various cyber threats. Deployment & Maintenance Monitor for security threats and apply regular updates: Continuously watch for potential security issues and keep the software up-to-date with the latest patches. Conduct incident response drills: Prepare for potential breaches by regularly practicing how to respond to security incidents. How Nonprofits Can Implement SSDLC with the Right Tools Understanding SSDLC is one thing—putting it into practice effectively is another. Many nonprofits lack dedicated cybersecurity teams or technical expertise, making it difficult to integrate security throughout the development process. This is where Microsoft’s Security Development Lifecycle (SDL) comes in. Leveraging Microsoft’s Security Development Lifecycle (SDL) Practices Microsoft’s Security Development Lifecycle (SDL) is a structured approach that aligns with SSDLC principles, providing security best practices and tools to help organizations—including nonprofits—develop secure applications. Some of the key SDL practices that nonprofits should incorporate include: 🔹 Perform Security Design Review and Threat Modeling – Nonprofits often handle sensitive data, such as donor information and beneficiary details. Conducting thorough security design reviews and identifying potential security risks early in the development cycle through threat modeling helps protect this sensitive information and ensures compliance with regulations. 🔹 Require Use of Proven Security Features, Languages, and Frameworks – Nonprofits may have limited resources, so it's crucial to use reliable security features, programming languages, and frameworks that are known to minimize vulnerabilities. This ensures that the software is built on a secure foundation without requiring extensive custom security solutions. 🔹 Perform Security Testing – Regularly run comprehensive security tests, including penetration tests and vulnerability assessments, to identify and address security flaws. This practice is essential for nonprofits to maintain the trust of their donors and beneficiaries by ensuring that their data is secure. 🔹 Implement Security Monitoring and Response – Continuously monitor for security threats and have a robust incident response plan in place to address potential breaches. Nonprofits need to be prepared to quickly detect and effectively manage any security incidents to minimize the impact on their operations and stakeholders. 🔹 Provide Security Training – Educate and train staff on security best practices and the importance of maintaining a secure development lifecycle. Nonprofits often rely on volunteers and staff who may not have extensive technical backgrounds, so ongoing security training is crucial to prevent security breaches and ensure everyone understands their role in maintaining security. This list showcases some of the essential SDL practices that can greatly benefit nonprofits. For a comprehensive overview, please view the following resources: Microsoft Security Development Lifecycle Practices. Learn how Microsoft supports secure software development as part of a cybersecurity solution - Training | Microsoft Learn Microsoft Tools That Support Secure Development To help nonprofits implement SSDLC and SDL, Microsoft offers several security-focused tools that integrate directly into the software development process. ✔ Microsoft Defender for DevOps – Protects code repositories and CI/CD pipelines from security threats, ensuring security is embedded throughout the development lifecycle. ✔ Azure DevOps Security Tools – Integrates security checks into DevOps workflows with automated scanning for vulnerabilities in code, dependencies, and containerized applications. ✔ Microsoft Defender for Cloud – Provides real-time security monitoring, threat detection, and compliance management for cloud-based applications. This helps nonprofits maintain continuous security visibility across Azure and hybrid environments. ✔ Azure Key Vault – Secures application secrets, encryption keys, and certificates, preventing unauthorized access to sensitive credentials used in nonprofit applications. ✔ Azure Web Application Firewall (WAF) – Helps protect nonprofit web applications from common threats like SQL injection, cross-site scripting (XSS), and bot attacks by filtering and monitoring traffic. ✔ Azure Policy – Automates security compliance checks within Azure environments, ensuring nonprofit applications and services follow best security practices throughout their lifecycle. Bringing It All Together For nonprofits, cybersecurity isn’t just an IT issue—it’s a mission-critical priority. A data breach can compromise donor trust, expose sensitive beneficiary information, and disrupt critical operations. By integrating Microsoft’s SDL practices and security tools into the Secure Software Development Lifecycle (SSDLC), nonprofits can: ✅ Proactively reduce cybersecurity risks before they become major threats. ✅ Protect donor and beneficiary data from unauthorized access. ✅ Ensure compliance with data privacy regulations. ✅ Strengthen trust with stakeholders who rely on them. By leveraging Microsoft’s security tools, nonprofits can build safer, more resilient applications—even without large security teams. This blog discusses building applications and incorporating security from the very beginning phases of development. If you are a nonprofit with applications that you may not have the budget to rebuild from the ground up, you can learn about modernizing and upgrading the security for your legacy applications here: Modernizing Legacy Applications in your Nonprofit | Microsoft Community HubImplementing Disaster Recovery for Azure App Service Web Applications
Starting March 31, 2025, Microsoft will no longer automatically place Azure App Service web applications in disaster recovery mode in the event of a regional disaster. This change emphasizes the importance of implementing robust disaster recovery (DR) strategies to ensure the continuity and resilience of your web applications. Here’s what you need to know and how you can prepare. Understanding the Change Azure App Service has been a reliable platform for hosting web applications, REST APIs, and mobile backends, offering features like load balancing, autoscaling, and automated management. However, beginning March 31, 2025, in the event of a regional disaster, Azure will not automatically place your web applications in disaster recovery mode. This means that you, as a developer or IT professional, need to proactively implement disaster recovery techniques to safeguard your applications and data. Why This Matters Disasters, whether natural or technical, can strike without warning, potentially causing significant downtime and data loss. By taking control of your disaster recovery strategy, you can minimize the impact of such events on your business operations. Implementing a robust DR plan ensures that your applications remain available and your data remains intact, even in the face of regional outages. Common Disaster Recovery Techniques To prepare for this change, consider the following commonly used disaster recovery techniques: Multi-Region Deployment: Deploy your web applications across multiple Azure regions. This approach ensures that if one region goes down, your application can continue to run in another region. You can use Azure Traffic Manager or Azure Front Door to route traffic to the healthy region. Multi-region load balancing with Traffic Manager and Application Gateway Highly available multi-region web app Regular Backups: Implement regular backups of your application data and configurations. Azure App Service provides built-in backup and restore capabilities that you can schedule to run automatically. Back up an app in App Service How to automatically backup App Service & Function App configurations Active-Active or Active-Passive Configuration: Set up your applications in an active-active or active-passive configuration. In an active-active setup, both regions handle traffic simultaneously, providing high availability. In an active-passive setup, the secondary region remains on standby and takes over only if the primary region fails. About active-active VPN gateways Design highly available gateway connectivity Automated Failover: Use automated failover mechanisms to switch traffic to a secondary region seamlessly. This can be achieved using Azure Site Recovery or custom scripts that detect failures and initiate failover processes. Add Azure Automation runbooks to Site Recovery recovery plans Create and customize recovery plans in Azure Site Recovery Monitoring and Alerts: Implement comprehensive monitoring and alerting to detect issues early and respond promptly. Azure Monitor and Application Insights can help you track the health and performance of your applications. Overview of Azure Monitor alerts Application Insights OpenTelemetry overview Steps to Implement a Disaster Recovery Plan Assess Your Current Setup: Identify all the resources your application depends on, including databases, storage accounts, and networking components. Choose a DR Strategy: Based on your business requirements, choose a suitable disaster recovery strategy (e.g., multi-region deployment, active-active configuration). Configure Backups: Set up regular backups for your application data and configurations. Test Your DR Plan: Regularly test your disaster recovery plan to ensure it works as expected. Simulate failover scenarios to validate that your applications can recover quickly. Document and Train: Document your disaster recovery procedures and train your team to execute them effectively. Conclusion While the upcoming change in Azure App Service’s disaster recovery policy may seem daunting, it also presents an opportunity to enhance the resilience of your web applications. By implementing robust disaster recovery techniques, you can ensure that your applications remain available and your data remains secure, no matter what challenges come your way. Start planning today to stay ahead of the curve and keep your applications running smoothly. Recover from region-wide failure - Azure App Service Reliability in Azure App Service Multi-Region App Service App Approaches for Disaster Recovery Feel free to share your thoughts or ask questions in the comments below. Let's build a resilient future together! 🚀Deploy your ASP.NET Core Web API with the help of GitHub Copilot for Azure in Visual Studio Code.
Introducing GitHub Copilot for Azure, your personal assistant to streamline the deployment process. It provides you with clear, step-by-step instructions to deploy your applications and assists with troubleshooting, making your development journey smoother and more efficient. In this blog, we’ll explore how to deploy an ASP.NET Core API to Azure using GitHub Copilot for Azure in Visual Studio Code. By leveraging Copilot’s AI capabilities, I’ll guide it with prompts to streamline the deployment process. Together, we’ll learn how to transform a locally developed API into a cloud-hosted solution with ease. Prerequisites An Azure account and a subscription. Create Azure for free or pay as you go A GitHub account and GitHub Copilot Subscription. creating-an-account-on-GitHub and quick start on copilots Visual Studio code. See more info on setting up vs code GitHub Copilot and GitHub Copilot Chat Extension. Set up GitHub Copilot in VS Code and Getting started with Copilot Chat in VS Code .NET SDK. Download it here, C# Dev-kit Extension in VS Code. More on C# Dev-kit Prepare I will be deploying the TodoApi developed with ASP.NET Core. The source code is available on GitHub. Follow these steps to have the project on your local machine. Head to the GitHub repo: Github-Copilot-for-Azure-TodoApi-Sample Clone the Repository on your terminal or download as Zip: git clone https://github.com/kemboi590/Github-Copilot-for-Azure-TodoApi-Sample-.git Change directory to the cloned folder: cd Github-Copilot-for-Azure-TodoApi-Sample- Install required Packages: dotnet restore Open with Visual Studio Code: code . Here is an illustration of the steps: Run the application - Open the inbuilt terminal on Visual Studio Code and type the following: dotnet run The API is now running and we can test it using REST Client. Calling REST APIs From the IDE Install the rest client extension. - Open the extension and search for Rest Client and install it. Open TodoApi.http file and start testing the routes: GitHub Copilot Set up When you install GitHub Copilot Extension, you also get GitHub Copilot Chat, a conversational extension that provides conversational AI assistance Go to extensions Search for GitHub Copilot Install GitHub Copilot for Azure GitHub Copilot for Azure extension is designed to help streamline the process of developing for Azure. On extensions, search for GitHub Copilot for Azure Install the extension Start your Conversation with GitHub Copilot for Azure extension Open the chat, use the shortcut keys: ctr + shift + I or open chat by clicking on the chat Icon. To use GitHub Copilot for Azure use azure then describe what you want it to help you with. I will share with you my prompts that I am using so that you can use them as well. Note: Your GitHub Copilot for Azure may not give the same output as mine. Here are the steps to Deploy our WebApp. Describe what you want GitHub Copilot for Azure to help you with. - Give a clear information so that the copilot will get to respond better. - Try this prompt: @Azure I have developed an ASP.NET Core web API using Visual Studio Code, which is a simple TodoAPI with CRUD Functionalities with no database, I would like to deploy it on azure with your help because I have no experience. Which services should I use and which options do I have to have it on azure - GitHub Copilot for Azure Suggest that for an API, we should use Azure App Services Let’s ask for more details @Azure to deploy Azure App services on Visual Studio Code, which are the available options? We now have three options, o Using Visual Studio Code Extension – App Service Extension o Manual Process – On Azure Portal o Automated CI/CD Pipeline on GitHub App Service Extension - I will go with the first Option (Using Visual Studio Code– App Service Extension) Asking for more steps I will ask GitHub Copilot to give me some steps I will use to deploy using App Service Extension @Azure Guide me on the steps using App Service Extension - Open the extensions and install App Service Extension - You will be requested to sign in to your azure account. Ensure you have azure subscription so that you can be able to deploy your API. Working with Azure tools - You will note that Azure icon is available is the side bar - Click on it and you will see the App Services under your subscription. Create an App Service Web App from the available options - Click on App Service and click on Create button (+) to create an App Service Web App. Web App Name - Give a unique name of your new web app and click Enter - I will name mine azure-copilot-demo Choose Runtime Stack - If you are following along with TodoApi project, select .NET 9 and click Enter. Select Pricing Tier Let’s ask copilot of these pricing tiers: @Azure While selecting the pricing tiers, i see three options. Free F1 Basic B1 Premium P1V2 Which one do I select I will select Basic (B1) because I consider my project small-to-medium applications and low-traffic production workloads. Web App created on the Terminal for Azure - It will take some few seconds for the web app to be created Publish your App - Want to know why should you publish your project? - Let’s ask GitHub copilot for Azure for clarification: @Azure what does this command do? - Open the terminal on the folder with the project and type the following command: dotnet publish -c Release -o ./bin/Publish New bin/publish Folder has been created - The folder contains our project which is now ready to deploy Deploy - Right Click on the new web app (azure-copilot-demo) on the list and choose deploy to web app - Browse the /bin/publish folder and select it: Deployment success - It will take some few mins for the Web App to be deployed. Check on your terminal for Azure. - Wait for some time then your web pp will be running on Azure. Working with deployed Web App - I will also use REST Client to test the deployed web App on Visual Studio Code. - The end pot I will be using will be: https://azure-copilot-demo.azurewebsites.net/ - Without starting the server this time, replace the Host Address with the one you got after deploying the web App. POST Request: - Test the other routes and they should all be working just fine. Conclusion We have been able to deploy our TodoApi with the help of GitHub Copilot for Azure. I hope you had a great time following a long and were able to deploy your application as well. You are not limited to deploying the Web Apps alone with the help of GitHub Copilot for Azure. Feel free to explore other services and remember to share feedback. Resources Get started with GitHub Copilot for Azure Preview Get started with GitHub Copilot Training Module on Microsoft Learn Example prompts for learning about Azure and your application with GitHub Copilot for Azure Preview
