Fueling the Agentic Web Revolution with NLWeb and PostgreSQL
We’re excited to announce that NLWeb (Natural Language Web), Microsoft’s open project for natural language interfaces on websites now supports PostgreSQL. With this enhancement, developers can leverage PostgreSQL and NLWeb to transform any website into an AI-powered application or Model Context Protocol (MCP) server. This integration allows organizations to utilize a familiar, robust database as the foundation for conversational AI experiences, streamlining deployment and maximizing data security and scalability. Soon, autonomous agents, not just human users, will consume and interpret website content, transforming how information is accessed and utilized online. During Microsoft //Build 2025, Microsoft introduced the era of the open agentic web, in which the internet is an open agentic web a new paradigm in which autonomous agents seamlessly interact across individual, organizational, team and end-to-end business contexts. To realize the future of an open agentic web, Microsoft announced the NLWeb project. NLWeb transforms any website to an AI-powered application with just a few lines of code and by connecting to an AI model and a knowledge base. In this post, we’ll cover: What NLWeb is and how it works with vector databases How pgvector enables vector similarity search in PostgreSQL for NLWeb Get started using NLWeb with Postgres Let’s dive in and see how Postgres + NLWeb can redefine conversational web interfaces while keeping your data in a familiar, powerful database. What is NLWeb? A Quick Overview of Conversational Web Interfaces NLWeb is an open project developed by Microsoft to simplify adding conversational AI interfaces to websites. How NLWeb works under the hood: Processes existing data/website content that exists in semi-structured formats like Schema.org, RSS, and other data that websites already publish Embeds and indexes all the content in a vector store (i.e PostgreSQL with pgvector) Routes user queries through several processes which handle natural langague understanding, reranking and retrieval. Answers queries with an LLM The result is a high-quality natural language interface on top of web data, giving developers the ability to let users “talk to” web data. By default, every NLWeb instance is also a Model Context Protocol (MCP) server, allowing websites to make their content discoverable and accessible to agents and other participants in the MCP ecosystem if they choose. Importantly, NLWeb is platform-agnostic and supports many major operating systems, AI models, and vector stores and the NLWeb project is modular by design, so developers can bring their own retrieval system, model APIs, and define their own extensions. NLWeb with PostgreSQL PostgreSQL is now embedded into the NLWeb reference stack as a native retriever, creating a scalable and flexible path for deploying NLWeb instances using open-source infrastructure. Retrieval Powered by pgvector NLWeb leverages pgvector, a PostgreSQL extension for efficient vector similarity search, to handle natural language retrieval at scale. By integrating pgvector into the NLWeb stack, teams can eliminate the need for external vector databases. Web data stored in PostgreSQL becomes immediately searchable and usable for NLWeb experiences, streamlining infrastructure and enhancing security. PostgreSQL's robust governance features and wide adoption align with NLWeb’s mission to enable conversational AI for any website or content platform. With pgvector retrieval built in, developers can confidently launch NLWeb instances on their own databases no additional infrastructure required. Implementation example We are going to use NLWeb and Postgres, to create a conversational AI app and MCP server that will let us chat with content from the Talking Postgres with Claire Giordano Podcast! Prerequisites An active Azure account. Enable and configure the pg_vector extensions. Create an Azure AI Foundry project. Deploy models gpt-4.1, gpt-4.1-mini and text-embedding-3-small. Install Visual Studio Code. Install the Python extension. Install Python 3.11.x. Install the Azure CLI (latest version). Getting started All the code and sample datasets are available in this GitHub repository. Step 1: Setup NLWeb Server 1. Clone or download the code from the repo. git clone https://github.com/microsoft/NLWeb cd NLWeb 2. Open a terminal to create a virtual python environment and activate it. python -m venv myenv source myenv/bin/activate # Or on Windows: myenv\Scripts\activate 3. Go to the 'code/python' folder in NLWeb to install the dependencies. cd code/python pip install -r requirements.txt 4. Go to the project root folder in NLWeb and copy the .env.template file to a new .env file cd ../../ cp .env.template .env 5. In the .env file, update the API key you will use for your LLM endpoint of choice and update the Postgres connection string. For example: AZURE_OPENAI_ENDPOINT="https://TODO.openai.azure.com/" AZURE_OPENAI_API_KEY="<TODO>" # If using Postgres connection string POSTGRES_CONNECTION_STRING="postgresql://<HOST>:<PORT>/<DATABASE>?user=<USERNAME>&sslmode=require" POSTGRES_PASSWORD="<PASSWORD>" 6. Update your config files (located in the config folder) to make sure your preferred providers match your .env file. There are three files that may need changes. config_llm.yaml: Update the first line to the LLM provider you set in the .env file. By default it is Azure OpenAI. You can also adjust the models you call here by updating the models noted. By default, we are assuming 4.1 and 4.1-mini. config_embedding.yaml: Update the first line to your preferred embedding provider. By default it is Azure OpenAI, using text-embedding-3-small. config_retrieval.yaml: Update the first line to postgres. You should update write_endpoint to postgres and You should update postgres retrieval endpoint is enabled to 'true' in the following list of possible endpoints. Step 2: Initialize Postgres Server Go to the 'code/python/misc folder in NLWeb to run Postgres initializer. NOTE: If you are using Azure Postgres Flexible server make sure you have `vector` extension allow-listed and make sure the database has the vector extension enabled, cd code/python/misc python postgres_load.py Step 3: Ingest Data from Talk Postgres Podcast Now we will load some data in our local vector database to test with. We've listed a few RSS feeds you can choose from below. Go to the 'code/python folder in NLWeb and run the command. The format of the command is as follows (make sure you are still in the 'python' folder when you run this): python -m data_loading.db_load <RSS URL> <site-name> Talking Postgres with Claire Giordano Podcast: python -m data_loading.db_load https://feeds.transistor.fm/talkingpostgres Talking-Postgres (Optional) You can check the documents table in your Postgres database and verify the table looks like the one below. To verify all the data from the website was uploaded. Test NLWeb Server Start your NLWeb server (again from the 'python' folder): python app-file.py Go to http://localhost:8000/ Start ask questions about the Talking Postgres with Claire Giordano Podcast, you may try different modes. Trying List Mode: Sample Prompt: “I want to listen to something that talks about the advances in vector search such as DiskANN” Trying Generate Mode Sample Prompt: “What did Shireesh Thota say about the future of Postgres?” Running NLWeb with MCP 1. If you do not already have it, install MCP in your venv: pip install mcp 2. Next, configure your Claude MCP server. If you don’t have the config file already, you can create the file at the following locations: macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json The default MCP JSON file needs to be modified as shown below: macOS Example Configuration { “mcpServers”: { “ask_nlw”: { “command”: “/Users/yourname/NLWeb/myenv/bin/python”, “args”: [ “/Users/yourname/NLWeb/code/chatbot_interface.py”, “—server”, “http://localhost:8000”, “—endpoint”, “/mcp” ], “cwd”: “/Users/yourname/NLWeb/code” } } } Windows Example Configuration { “mcpServers”: { “ask_nlw”: { “command”: “C:\\Users\\yourusername\\NLWeb\\myenv\\Scripts\\python”, “args”: [ “C:\\Users\\yourusername\\NLWeb\\code\\chatbot_interface.py”, “—server”, “http://localhost:8000”, “—endpoint”, “/mcp” ], “cwd”: “C:\\Users\\yourusername\\NLWeb\\code” } } } Note: For Windows paths, you need to use double backslashes (\\) to escape the backslash character in JSON. 3. Go to the 'code/python’ folder in NLWeb and run the command. Enter your virtual environment and start your NLWeb local server. Make sure it is configured to access the data you would like to ask about from Claude. # On macOS source ../myenv/bin/activate python app-file.py # On Windows ..\myenv\Scripts\activate python app-file.py 4. Open Claude Desktop. It should ask you to trust the 'ask_nlw' external connection if it is configured correctly. After clicking yes and the welcome page appears, you should see 'ask_nlw' in the bottom right '+' options. Select it to start a query. 5. To query NLWeb, just type 'ask_nlw' in your prompt to Claude. You'll notice that you also get the full JSON script for your results. Remember, you must have your local NLWeb server started to use this option. Learn More Vector Store in Azure Postgres Flexible Server Generative AI in Azure Postgres Flexible Server NLWeb GitHub repo includes: A reference server for handling natural language queries PGvector integrationVideo Tutorial: How to Migrate Your WordPress Site to Azure for Nonprofits
Before you migrate your WordPress site, ensure you have deployed a WordPress site on Azure. If you're unfamiliar with this process, scroll down to the reference section at the bottom of this blog. There is an article that will guide you through creating a WordPress site in Azure, complete with a helpful video. Why Azure for Nonprofits? Azure offers various benefits for nonprofits, including cost savings, scalability, and robust security features. Migrating your WordPress site to Azure can help you leverage these advantages to better serve your community. Step-by-Step Guide Access the WordPress Admin Portal: Go to your personal WordPress site and navigate to the admin portal by adding /wp-admin to your site's URL. Install the WP Migration Plugin: Select Plugins > Add New. Search for "WP Migration" and press enter. Install and activate the "All-in-One WP Migration and Backup" plugin. Export Your Website: Click on the plugin itself where it says "All-in-One WP Migration". Select Export > Export Site to File. Download the exported file. Access the WordPress Site on Azure: Navigate to the admin portal of your WordPress site on Azure by adding /wp-admin to your site's URL. Install the WP Migration Plugin on Azure: Select Plugins > Add New. Search for "WP Migration". Install and activate the plugin. Import Your Website: Click on the plugin and select Import. Choose Import from File and select the file you downloaded earlier. Handling File Size Limits If you encounter a file size limit error (WordPress has a 50 MB limit), you can either purchase the unlimited extension or manually increase the limit: Access Azure Portal: Go to your Azure portal and type in "App Services". Select your app service. Use SSH to Modify File Size Limits: Scroll down to Deployment Tools and click on SSH. Click on Go to access the backend of the app service. Create a file in the home site wwwroot directory named .user.ini. Edit the File: Use the command nano /home/site/wwwroot/.user.ini. Add the following lines to increase the upload and post max size: upload_max_filesize = 1G post_max_size = 1G Save the file by pressing Ctrl + X, then Y, and Enter. Verify and Import: Refresh your WordPress site on Azure. Import the file again, and it should bypass the previous limit. Final Steps Once the migration is complete, you may want to delete the .user.ini file you created earlier. Use the command: rm /home/site/wwwroot/.user.ini References techcommunity.microsoft.com/blog/nonprofittechies/deploying-a-wordpress-site-on-microsoft-azure-a-guide-for-non-profits-with-video/4415254?previewMessage=true Resolving Host Restrictions on File Sizes Exceeding 50 MB in WordPress on Azure for Nonprofits | Microsoft Community HubUsing GitHub Copilot: Code Suggestions for Nonprofits
What Is GitHub Copilot's Code Suggestions Feature? At its core, GitHub Copilot is an AI pair programmer powered by OpenAI. It analyzes your code, learns from your patterns, and provides intelligent suggestions in real time. The Code Suggestions feature is particularly useful for generating code snippets, automating repetitive tasks, and even writing entire functions or classes based on descriptive comments. This dramatically reduces the time and effort needed for coding and debugging. For nonprofit organizations, this means more time can be spent on impactful projects rather than navigating technical roadblocks. Whether your team is building a donor management system, a volunteer scheduling app, or an advocacy platform, GitHub Copilot can help bring these visions to life with efficiency and precision. Step-By-Step Guide: Using GitHub Copilot with Visual Studio Step 1: Install GitHub Copilot Ensure you have a GitHub account with an active Copilot subscription. Download and install Visual Studio or Visual Studio Code, both of which are compatible with GitHub Copilot. Install the GitHub Copilot extension from the Visual Studio or Visual Studio Code Extensions Marketplace. Step 2: Set Up GitHub Copilot Once the extension is installed, open Visual Studio or Visual Studio Code. Log into your GitHub account to authenticate Copilot. Follow the prompts to enable Copilot in your environment. Step 3: Start Writing Code Begin typing code or comments in your editor. For example, typing a comment like // Create a function to calculate total donations will prompt Copilot to suggest a function tailored to that description. You can accept the suggestion using the Tab key or refine it further. Step 4: Explore Customization Adjust Copilot’s behavior by modifying its settings. You can enable or disable inline suggestions, tweak its verbosity, and choose how much automation you want in your workflow. Step 5: Iterate and Collaborate As you write code, GitHub Copilot will continuously provide relevant suggestions, helping you work smarter and faster. Collaborate with your team by sharing code snippets and ensuring everyone benefits from Copilot’s insights. Unlocking Innovation for Nonprofits By automating mundane tasks and providing intelligent coding support, GitHub Copilot encourages developers to think bigger and aim higher. Nonprofits can channel their resources into high-impact initiatives, confident that their technical tools will keep pace with their ambitions. Call to Action GitHub Copilot is more than a tool; it’s a partner in innovation, empowering nonprofit organizations to maximize their impact and achieve their missions more efficiently. Whether you’re a seasoned developer or just starting your coding journey, GitHub Copilot can help bring your projects to life. Ready to transform your coding experience? Visit GitHub Copilot to learn more, explore pricing for nonprofits, and start your free trial today. Take the first step toward a more productive future and ensure your nonprofit’s technology is as impactful as its mission.Understanding DNS: A Nonprofit's Guide to Website Security and Accessibility
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. What is DNS? DNS, or Domain Name System, is often referred to as the internet's "phonebook." Think of it this way: when you want to visit a website, like www.example.org, you type in the domain name. However, computers don’t understand domain names—they communicate using numbers, called IP addresses, like 192.168.1.1. DNS acts as the translator, converting the user-friendly domain name into the machine-friendly IP address, ensuring you land on the correct website. For example, if you type in your nonprofit’s domain, let’s say www.mycharity.org, the DNS system takes that name, finds the matching IP address, and directs the internet to deliver your website to the user. Without DNS, navigating the web would mean memorizing strings of numbers for every site you wanted to visit—something no one wants to do! Why DNS Matters for Nonprofits A reliable DNS is essential for nonprofits for several reasons: 1. Website Accessibility Your website is often the first point of contact for donors, volunteers, and the communities you serve. If your DNS isn’t functioning correctly, it can lead to downtime, making your site inaccessible. This can result in lost donations, missed opportunities, and frustration for users trying to learn more about your mission. 2. Security A secure DNS setup helps protect your website from cyber threats like phishing attacks or DNS hijacking, where bad actors redirect users to malicious websites. A compromised DNS can damage your nonprofit’s reputation and erode trust among your supporters. 3. Improved User Experience A fast DNS ensures that your website loads quickly. Slow load times can frustrate users and may even discourage potential donors or partners from exploring your site further. Common DNS Issues Nonprofits Face—and How to Fix Them Let’s look at some common DNS-related problems and their solutions: 1. Website Downtime Issue: Your website suddenly goes offline, and users cannot access it. Solution: This could be due to an expired domain or issues with your DNS provider. Make sure your domain name is renewed promptly and work with a reputable DNS provider that offers high reliability and uptime guarantees. 2. Misconfigured DNS Records Issue: Users report being redirected to the wrong website or encountering errors. Solution: Double-check your DNS records, particularly the A records (which map your domain to your IP address) and CNAME records (used for subdomains). Tools like DNSChecker.org can help you verify your configurations. 3. Slow Load Times Issue: Your website loads slowly, frustrating potential donors. Solution: Invest in a DNS provider with a global network of servers. This ensures faster resolution times, especially for users accessing your site from different parts of the world. 4. Security Threats Issue: You suspect your DNS may have been hijacked or compromised. Solution: Implement DNSSEC (DNS Security Extensions) to add an extra layer of protection. Additionally, enable two-factor authentication on your DNS management account to prevent unauthorized changes. Tips for Nonprofits to Manage Their DNS Effectively Managing your DNS may sound intimidating, but with the right approach, it can be straightforward. Here are some tips to help your nonprofit succeed: Choose a Reliable DNS Provider: Look for providers with strong uptime records, robust security features, and excellent customer support. Regularly Monitor Your DNS Settings: Periodically check your DNS records to ensure everything is configured correctly and no unauthorized changes have been made. Educate Your Team: Make sure your staff or volunteers understand the basics of DNS and know who to contact in case of an issue. Enable Automatic Renewals: Avoid domain expiration by enabling automatic renewals for your domain registration. Backup Your Settings: Keep a record of your DNS settings so you can quickly restore them if needed. Conclusion In today’s digital age, having a reliable and secure DNS is crucial for nonprofits. It ensures your website remains accessible, secure, and user-friendly, helping you better serve your community and achieve your mission. By understanding how DNS works and addressing issues proactively, your nonprofit can create a strong online presence and build trust among your supporters. Remember, you don’t have to be a tech expert to manage your DNS effectively. With the right resources and support, you can empower your organization to navigate the world of DNS with confidence.Boosting Nonprofits with Github Copilot
What is Github Copilot? Github Copilot, developed by OpenAI and Github, is an AI-powered assistant that integrates seamlessly into popular code editors such as Visual Studio Code, Neovim, and JetBrains. It leverages advanced machine learning to suggest code snippets, provide auto-completions, and even generate entire functions based on the developer’s context and intent. Think of it as your intelligent pair programmer, available 24/7, to enhance your productivity and creativity. Key Features of Github Copilot Code Suggestions: Provides real-time code suggestions directly in your editor, reducing the need for extensive searches or documentation reviews. Auto-completion: Completes lines or entire blocks of code, saving time and effort. Multi-language Support: Supports a wide range of programming languages, making it versatile for developers with varied expertise. Context-aware Recommendations: Adapts to your coding style and context, offering tailored suggestions that align with your project’s needs. Learning and Adaptation: Becomes smarter with usage, ensuring better and more accurate recommendations over time. Benefits of Github Copilot for Nonprofits For nonprofits, every resource counts. Github Copilot doesn’t just help write code faster; it empowers organizations to focus on what truly matters—their mission. Here’s how it can be a game-changer for nonprofits: Improved Efficiency: By handling repetitive coding tasks, Github Copilot frees up time for developers to concentrate on strategic and impactful projects. Enhanced Collaboration: Teams can use the tool to standardize code across projects, improving consistency and reducing the learning curve for new members. Resource Optimization: Nonprofits often operate with lean teams. Copilot helps bridge gaps in technical expertise, allowing less experienced developers to achieve more. Accessibility: Developers with limited experience can leverage Copilot’s advanced capabilities to tackle complex coding challenges, leveling the playing field. Innovation: By reducing the time spent on mundane tasks, organizations have more bandwidth to focus on innovative solutions aligned with their mission. Practical Applications for Nonprofits Wondering how Github Copilot can be applied to the nonprofit sector? Here are some practical examples: Building Sophisticated Websites Nonprofits can use Github Copilot to efficiently develop and maintain websites that serve as their digital headquarters. Whether it’s crafting interactive donation pages or creating compelling narratives for their causes, Copilot ensures smooth and efficient coding. Managing Donor Databases With Copilot, developers can quickly set up and optimize donor management systems, ensuring secure and streamlined data handling. The AI assistant can generate scripts for querying, organizing, and analyzing donor information. Automating Workflows From automating routine administrative tasks to setting up email campaigns, Github Copilot can significantly reduce manual effort while maintaining accuracy. Developing Mobile Applications Mission-driven nonprofits can leverage Copilot to create user-friendly mobile apps that connect with their target audiences, providing updates, fundraising tools, and volunteering opportunities. Enhancing Cybersecurity Copilot can help organizations write robust security protocols to safeguard sensitive data, ensuring compliance with data protection regulations. Ready to Transform Your Nonprofit with Github Copilot? Github Copilot is more than just a coding assistant—it’s a bridge to innovation and efficiency for nonprofits. If you’re intrigued by its potential, we invite you to explore Github Copilot and sign up for a free trial. See firsthand how it can revolutionize your workflows and empower your team to achieve more. Stay tuned for future blog posts, where we’ll delve deeper into Github Copilot’s features and share step-by-step guides on integrating it into your nonprofit’s workflows. Don’t miss the chance to elevate your organization to new heights! Resources to Get Started For nonprofits eager to harness the power of Github Copilot, there’s a wealth of resources available to make your journey seamless. Here are some key links and communities to get you started: Official Github Copilot Documentation: A comprehensive guide to installing, configuring, and using Github Copilot effectively. Community Forums: Join a vibrant community of developers and nonprofit organizations. Share tips, ask questions, and learn from others' experiences. Github Learning Lab: Explore interactive modules and exercises tailored to help organizations of all sizes master Github Copilot. Microsoft Learn: Access free, interactive learning paths and resources offered by Microsoft to build your technical skills, including guides and tutorials related to GitHub and AI-driven tools.Resolving Host Restrictions on File Sizes Exceeding 50 MB in WordPress on Azure for Nonprofits
Encountering an error due to host restrictions on file sizes exceeding 50 MB can be frustrating, especially for nonprofits using WordPress on Azure. This article provides detailed instructions on how to resolve this issue effectively. Understanding the Error When you try to upload a file larger than 50 MB, you might encounter errors such as Request body too large or HTTP 502. These errors occur because Azure imposes limits on the size of files that can be uploaded to its services. Steps to Resolve the Issue Log into the Azure Portal Access the Azure portal by navigating to portal.azure.com. Use the search bar at the top of the portal to search for "App Services". From the list of App Services, select the one associated with your application. SSH into the App Service: Scroll down to the Development Tools section in the left-hand menu. Select SSH to open an SSH session directly in the Azure portal. Click Go to connect to the web-based console interface of your app. Adjust App Service Settings: Use the following command to create a .user.ini file in the wwwroot directory: nano /home/site/wwwroot/.user.ini Add the following lines to the file. For Windows, use Control + Shift + V to paste inside the nano editor: upload_max_filesize = 1024M post_max_size = 1024M For Windows, press Control + X to exit the nano editor. Press Y to confirm saving the changes. Press Enter to save the file. Check Your Wordpress Site go into your wp-admin page Select Media then add Media then you will notice that the upload file has been changed Revert the Change: To revert the change, return to the Azure Web App command line and use the following command: rm /home/site/wwwroot/.user.ini Conclusion By following these steps, nonprofits using WordPress on Azure can effectively resolve host restrictions on file sizes exceeding 50 MB, ensuring smoother file uploads and better application performance.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 LearnYour Guide to Azure Storage Options
Storage Made Simple Nonprofits often manage sensitive and crucial data, ranging from donor information to financial records and program details. Azure Storage offers a plethora of options that cater to the unique needs of nonprofits, ensuring that their data is stored securely and efficiently. By leveraging Azure's diverse storage solutions, nonprofits can benefit from scalable storage accounts, various tier options that optimize cost, and advanced lifecycle management to streamline data retention and deletion processes. Azure's robust encryption and security measures further protect data integrity, ensuring compliance with regulations. Nonprofits can ensure that their valuable data is not only safe but also accessible and manageable, helping them focus on their mission-driven work without worrying about data-related issues. Types of Storage Azure Storage offers various types of storage solutions to meet different requirements. These solutions are designed to support different use cases. Below is a brief description of the different types of storage: Blob Storage: Ideal for storing unstructured data such as documents, images, and media files. It supports massive amounts of data with easy access. File Storage: Provides fully managed file shares in the cloud that can be accessed via the SMB protocol. Perfect for lift-and-shift applications. Queue Storage: Enables message queuing for large workloads and is useful for decoupling application components, ensuring smooth communication between services. Table Storage: Stores large amounts of structured data with a NoSQL key-value store. Suitable for flexible datasets and rapid development scenarios. Disk Storage: Offers high-performance block storage for virtual machines. Ensures data durability and supports a wide range of I/O demands. Azure Container Storage: The perfect solution for Kubernetes orchestration and management for container applications. Utilizing rapid scale out of pods. Ideal for scalability and stateful applications. To maximize cost efficiency, nonprofits can leverage the following: Utilize tiered storage options to balance cost and performance based on data access patterns. Implement lifecycle management policies to automate data retention and deletion, reducing storage costs. Take advantage of scalable storage accounts to avoid over-provisioning and only pay for what they use. Encryption & Security Security and encryption are paramount for safeguarding sensitive information in Azure storage. Azure provides robust encryption mechanisms to ensure data protection across all storage types. File Storage, Queue Storage, Table Storage, Disk Storage, and Azure Container Storage all support encryption at rest, using Microsoft-managed keys or customer-managed keys for added control. Advanced features such as Azure Key Vault integration enhance security by allowing centralized management of encryption keys and secrets. Transport Layer Security (TLS) is also utilized to secure data in transit, ensuring that all communications are encrypted and secure. Organizations must ensure that their data is not only accessible but also protected from unauthorized access and tampering. Implementing encryption and security measures helps in maintaining compliance with regulatory standards and safeguarding the integrity of critical information. When planning for storage solutions, it's crucial to factor in these security aspects to develop a comprehensive strategy that includes encryption, secure access protocols, and regular audits to identify and mitigate potential vulnerabilities. Lifecycle Management Lifecycle Management is a crucial strategy for organizations seeking to optimize their data storage solutions. It involves the automatic transitioning of data through various storage tiers based on predefined policies, which are tailored to the access patterns and retention requirements of the data. By implementing lifecycle management policies, organizations can ensure that frequently accessed data remains on high-performance, costlier storage, while infrequently accessed data is moved to more economical storage options. This approach not only reduces storage costs but also enhances the efficiency of data retrieval processes. Furthermore, lifecycle management includes automated deletion policies for obsolete data, thereby freeing up storage space and ensuring compliance with data retention regulations. By adopting a comprehensive lifecycle management plan, organizations can effectively manage their storage resources, maintain data integrity, and ensure that their storage infrastructure scales with their evolving needs. Conclusion In conclusion, optimizing Azure storage solutions requires a balanced approach that integrates cost-effective strategies, robust security measures, and efficient lifecycle management. By leveraging tiered storage, automating data retention and deletion policies, and ensuring comprehensive encryption, organizations can achieve a secure, scalable, and economical storage environment. Through strategic planning and implementation, they can not only meet their current needs but also adapt to future demands, thereby ensuring that their data remains accessible, protected, and efficiently managed. Hyperlinks Azure Storage Documentation Hub | Microsoft Learn Introduction to Azure Storage - Cloud storage on Azure | Microsoft Learn Storage account overview - Azure Storage | Microsoft Learn Describe Azure storage services - Training | 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 Hub
