diff --git a/.gitignore b/.gitignore
index e43b0f98..2608ec26 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1 +1,2 @@
 .DS_Store
+.vscode
\ No newline at end of file
diff --git a/.vscode/settings.json b/.vscode/settings.json
deleted file mode 100755
index cb720b7f..00000000
--- a/.vscode/settings.json
+++ /dev/null
@@ -1,11 +0,0 @@
-{
-    "markdownlint.config": {
-        "MD028": false,
-        "MD025": {
-            "front_matter_title": ""
-        }
-    },
-    "githubPullRequests.ignoredPullRequestBranches": [
-        "master"
-    ]
-}
\ No newline at end of file
diff --git a/blog/_posts/2025-01-06-eks-to-aks-series-part2.md b/blog/_posts/2025-01-06-eks-to-aks-series-part2.md
new file mode 100644
index 00000000..938eb0c7
--- /dev/null
+++ b/blog/_posts/2025-01-06-eks-to-aks-series-part2.md
@@ -0,0 +1,25 @@
+---
+title: "Mastering the Move: EKS to AKS by Example - Part 2"
+description: "Learn how to replicate an Amazon Elastic Kubernetes Service (EKS) web application with AWS Web Application Firewall (WAF) using Azure Web Application Firewall (WAF) and Azure Application Gateway in Azure Kubernetes Service (AKS)"
+date: 2025-01-06
+author: Kenneth Kilty
+categories: general
+---
+
+## Introduction
+
+Welcome back to our series on migrating Amazon EKS workloads to Azure Kubernetes Service (AKS). In [Part 1](https://azure.github.io/AKS/2024/08/01/eks-to-aks-series-part1) we explored migrating and Event Driven Workload using Karpenter and KEDA from EKS to AKS. Next, we look into a more complex migration scenario with a common Kubernetes workload the [n-tier web application](https://learn.microsoft.com/azure/architecture/guide/architecture-styles/n-tier).
+
+## EKS to AKS - Web Application Scenario
+
+This new [article](https://learn.microsoft.com/azure/aks/eks-web-overview) guides you through replicating an Amazon Elastic Kubernetes Service (EKS) web application with AWS Web Application Firewall (WAF) using Azure Web Application Firewall (WAF) and Azure Application Gateway in Azure Kubernetes Service (AKS). This sample uses a WAF to protect a [Yelb](https://github.com/mreferre/yelb/) web-based application running in a Kubernetes cluster.
+
+In this guide, we explore the deployment process, starting with understanding the conceptual differences between EKS and AKS for the web application workload infrastructure. We then move on to architecting the workload for Azure, updating the app code for compatibility with Azure APIs, and preparing for deployment using the Azure CLI. Finally, we deploy the replicated workload in AKS and test it to ensure it functions as expected.
+
+The guide also include detailed AWS service by Azure service discussion and details alternative solutions for managing ingress including [Application Gateway Ingress Controller (AGIC)](https://learn.microsoft.com/azure/application-gateway/ingress-controller-overview), [Azure Application Gateway for Containers](https://learn.microsoft.com/azure/application-gateway/for-containers/overview), [Azure Front Door (AFD)](https://learn.microsoft.com/azure/frontdoor/front-door-overview), and a [NGINX ingress controller](https://github.com/kubernetes/ingress-nginx) with end-to-end TLS configured using [Azure Key Vault](https://learn.microsoft.com/azure/key-vault/general/basic-concepts).
+
+## Looking Forward
+
+Our next article will explore migrating an EKS AI/ML workload to AKS. We'll look at migration challenges common with AI/ML workloads like cost optimization, efficient scaling, and GPU usage.
+
+As always, we are interested to hear about the migration challenges and scenarios you encounter, so we can continue to enhance the features and documentation for AKS to ease the transition from on-premises or other clouds to Azure. Please share your ideas using one of the contact methods below.
diff --git a/blog/_posts/2025-01-13-ray-on-aks.md b/blog/_posts/2025-01-13-ray-on-aks.md
new file mode 100644
index 00000000..94a93c51
--- /dev/null
+++ b/blog/_posts/2025-01-13-ray-on-aks.md
@@ -0,0 +1,23 @@
+---
+title: "Ray on AKS"
+description: ""
+date: 2025-01-13
+author: Kenneth Kilty
+categories: ai
+---
+
+We've released new guidance for running Ray on AKS!
+
+## Open Source Ray on AKS
+
+Ray is an open-source project developed at UC Berkeley's RISE Lab that provides a unified framework for scaling AI and Python applications. It consists of a core distributed runtime and a set of AI libraries designed to accelerate machine learning workloads. Ray may be run on Kubernetes via the KubeRay operator which simplifies the process of deploying and managing Ray clusters on Kubernetes.
+
+Check out our new guide, "[Deploy a Ray cluster on Azure Kubernetes Service (AKS)](https://learn.microsoft.com/azure/aks/ray-overview)," which walks you through deploying the necessary AKS infrastructure using Terraform to support a Ray cluster. This guide also includes a sample CPU-based project that demonstrates distributed training of a PyTorch model on Fashion MNIST with Ray Train on AKS.
+
+## RayTurbo by Anyscale on AKS
+
+For customers requiring commercial support, [RayTurbo](https://www.anyscale.com/product/platform/rayturbo) by [Anyscale](https://www.anyscale.com/) is supported on Azure Kubernetes Service (AKS). For more information regarding RayTurbo on AKS, reach out [directly to Anyscale](https://www.anyscale.com/book/demo?utm_source=azure&utm_medium=blog&utm_campaign=aks_rayturbo_blog).
+
+Ray is the AI Compute Engine powering workloads with leading performance. RayTurbo, Anyscale's optimized Ray engine, delivers better performance, scale, reliability, and efficiency for AI workloads.
+
+We look forward to seeing what amazing Ray and RayTurbo workloads you run on AKS!