diff --git a/0_Azure/4_AzureDevOps/demos/0_Overview.md b/0_Azure/4_AzureDevOps/demos/0_Overview.md
new file mode 100644
index 000000000..b2a5ed5e5
--- /dev/null
+++ b/0_Azure/4_AzureDevOps/demos/0_Overview.md
@@ -0,0 +1,124 @@
+# Azure DevOps - Overview
+
+Costa Rica
+
+[](https://github.com/)
+[brown9804](https://github.com/brown9804)
+
+Last updated: 2025-04-23
+
+----------
+
+List of References (Click to expand)
+
+- [Extensions overview](https://learn.microsoft.com/en-us/azure/devops/extend/overview?view=azure-devops)
+- [Extensions for Azure DevOps VS marketplace](https://marketplace.visualstudio.com/azuredevops/)
+- [Azure DevOps About GitHub integration](https://learn.microsoft.com/en-us/azure/devops/cross-service/github-integration?view=azure-devops)
+- [Planning and tracking work for your team or project](https://docs.github.com/en/issues/tracking-your-work-with-issues/configuring-issues/planning-and-tracking-work-for-your-team-or-project)
+- [Best Practices for Managing Multiple Teams with GitHub Issues and Projects (V2)](https://github.com/orgs/community/discussions/137358)
+- [FAQs about working across projects](https://learn.microsoft.com/en-us/azure/devops/project/work-across-projects-faqs?view=azure-devops)
+- [Migrating repositories from Azure DevOps to GitHub Enterprise Cloud](https://docs.github.com/en/migrations/using-github-enterprise-importer/migrating-from-azure-devops-to-github-enterprise-cloud/m)
+- [Azure DevOps Cross-Organization Reporting and Analysis using Power BI](https://devblogs.microsoft.com/premier-developer/azure-devops-cross-organization-reporting-and-analysis-using-power-bi/)
+
+Table of Contents (Click to expand)
+
+- [Overview](#overview)
+- [Azure Boards](#azure-boards)
+- [Azure Repos](#azure-repos)
+- [Azure Pipelines](#azure-pipelines)
+- [Azure Test Plans](#azure-test-plans)
+- [Azure Artifacts](#azure-artifacts)
+
+Features
+
+ - **Kanban Boards**: Visualize work items and their flow through various stages. Teams can customize columns to reflect their workflow and easily move tasks across the board.
+ - **Scrum Boards**: Manage sprints and backlogs, track progress, and plan iterations. Scrum boards help teams organize work into manageable chunks and deliver incremental value.
+ - **Work Item Tracking**: Create and manage work items such as user stories, tasks, bugs, and features. Work items can be linked to code changes, builds, and releases.
+ - **Backlogs**: Prioritize and manage the product backlog. Teams can break down features into user stories and tasks, estimate effort, and plan sprints.
+ - **Sprints**: Plan and manage sprint cycles, track sprint progress, and review completed work. Teams can use sprint planning tools to allocate work and monitor velocity.
+ - **Customizable Workflows**: Tailor workflows to match team processes. Customize states, transitions, and rules for work items to ensure they align with team practices.
+
+Features
+
+ - **Git Repositories**: Host and manage Git repositories. Teams can clone, commit, push, and pull code changes, and collaborate using branches and pull requests.
+ - **Team Foundation Version Control (TFVC)**: An alternative to Git, TFVC is a centralized version control system. It allows teams to manage code with check-ins and branching.
+ - **Pull Requests**: Facilitate code reviews and collaboration. Developers can create pull requests to propose code changes, review code, discuss modifications, and merge changes.
+ - **Branch Policies**: Enforce best practices and quality standards. Teams can set policies for branch protection, requiring code reviews, and ensuring builds pass before merging.
+ - **Code Reviews**: Conduct thorough code reviews to ensure code quality and adherence to standards. Reviewers can comment on code, suggest changes, and approve or reject pull requests.
+Features
+
+ - **Build Automation**: Automate the building of code. Pipelines can compile code, run tests, and produce artifacts for deployment.
+ - **Release Pipelines**: Automate the deployment process. Teams can define release pipelines to deploy applications to various environments, such as development, staging, and production.
+ - **Deployment to Various Environments**: Deploy applications to multiple environments, including on-premises servers, cloud services, and containers. Pipelines support deployment to Azure, AWS, GCP, Kubernetes, and more.
+ - **Integration with Multiple Tools and Services**: Integrate with a wide range of tools and services, such as GitHub, Docker, Jenkins, and Terraform. Pipelines can trigger builds and deployments based on code changes and other events.
+ - **Support for Various Programming Languages and Platforms**: Build and deploy applications written in different languages, including .NET, Java, Node.js, Python, and PHP. Pipelines support Windows, Linux, and macOS platforms.
+
+Features
+
+ - **Manual Testing**: Create and execute manual test cases. Testers can document test steps, expected results, and actual outcomes.
+ - **Automated Testing**: Integrate automated tests into CI/CD pipelines. Teams can run automated tests as part of the build and release process to ensure code quality.
+ - **Test Case Management**: Organize and manage test cases, test suites, and test plans. Teams can track test coverage, prioritize tests, and manage test execution.
+ - **Test Execution**: Execute tests and record results. Testers can run tests manually or automatically, capture test results, and log defects.
+ - **Reporting**: Generate reports and dashboards to track test progress, test results, and quality metrics. Teams can use these insights to make informed decisions and improve software quality.
+
+Features
+
+ - **Package Feeds**: Create and manage package feeds for different package types, including Maven, npm, NuGet, and Python. Teams can publish, consume, and share packages.
+ - **Versioning**: Manage package versions to ensure compatibility and stability. Teams can use versioning to track changes and maintain different versions of packages.
+ - **Dependency Management**: Manage dependencies between packages. Teams can define dependencies, resolve conflicts, and ensure that applications use the correct versions of packages.
+ - **Integration with CI/CD Pipelines**: Integrate package management with CI/CD pipelines. Teams can automate the publishing and consumption of packages as part of the build and release process.
+