diff --git a/content/registry/packages/azure-native/how-to-guides/azure-cs-aks-managed-identity.md b/content/registry/packages/azure-native/how-to-guides/azure-cs-aks-managed-identity.md
new file mode 100644
index 000000000000..879c2d3f950f
--- /dev/null
+++ b/content/registry/packages/azure-native/how-to-guides/azure-cs-aks-managed-identity.md
@@ -0,0 +1,77 @@
+---
+title: "Azure Kubernetes Service (AKS) Cluster using the native Azure Provider | C#"
+h1: "Azure Kubernetes Service (AKS) Cluster using the native Azure Provider"
+linktitle: "Azure Kubernetes Service (AKS) Cluster using the native Azure Provider"
+meta_desc: "Azure Kubernetes Service (AKS) Cluster using the native Azure Provider How-to Guide using C#"
+no_edit_this_page: true
+cloud: azure
+language: cs
+layout: package
+---
+
+
+
+
+
+
+ View Code
+
+
+
+
+
+
+
+This example deploys an AKS cluster, creates an Azure User Assigned Managed Identity, and sets credentials to manage access to the cluster.
+
+## Deploying the App
+
+To deploy your infrastructure, follow the below steps.
+
+### Prerequisites
+
+1. [Install Pulumi](https://www.pulumi.com/docs/get-started/install/)
+1. [Configure Azure Credentials](https://www.pulumi.com/docs/intro/cloud-providers/azure/setup/)
+
+### Steps
+
+After [cloning](https://github.com/pulumi/examples#checking-out-a-single-example) this repo, from this working directory, run these commands:
+
+1. Create a new stack, which is an isolated deployment target for this example:
+
+ ```bash
+ $ pulumi stack init dev
+ ```
+
+1. Set the Azure region location to use:
+
+ ```
+ $ pulumi config set azure-native:location westus2
+ ```
+
+1. Stand up the cluster by invoking pulumi
+ ```bash
+ $ pulumi up
+ ```
+
+1. After 3-4 minutes, your cluster will be ready, and the kubeconfig YAML you'll use to connect to the cluster will be available as an [Output](https://www.pulumi.com/docs/concepts/inputs-outputs/#outputs). You can save this kubeconfig to a file like so:
+
+ ```bash
+ $ pulumi stack output kubeconfig --show-secrets > kubeconfig.yaml
+ ```
+
+ Once you have this file in hand, you can interact with your new cluster as usual via `kubectl`:
+
+ ```bash
+ $ KUBECONFIG=./kubeconfig.yaml kubectl get nodes
+ ```
+
+1. From there, feel free to experiment. Simply making edits and running `pulumi up` will incrementally update your stack.
+
+1. Once you've finished experimenting, tear down your stack's resources by destroying and removing it:
+
+ ```bash
+ $ pulumi destroy --yes
+ $ pulumi stack rm --yes
+ ```
+
diff --git a/content/registry/packages/azure-native/how-to-guides/azure-go-aks-managed-identity.md b/content/registry/packages/azure-native/how-to-guides/azure-go-aks-managed-identity.md
new file mode 100644
index 000000000000..b751f9bf16f2
--- /dev/null
+++ b/content/registry/packages/azure-native/how-to-guides/azure-go-aks-managed-identity.md
@@ -0,0 +1,77 @@
+---
+title: "Azure Kubernetes Service (AKS) Cluster using the native Azure Provider | Go"
+h1: "Azure Kubernetes Service (AKS) Cluster using the native Azure Provider"
+linktitle: "Azure Kubernetes Service (AKS) Cluster using the native Azure Provider"
+meta_desc: "Azure Kubernetes Service (AKS) Cluster using the native Azure Provider How-to Guide using Go"
+no_edit_this_page: true
+cloud: azure
+language: go
+layout: package
+---
+
+
+
+
+
+
+ View Code
+
+
+
+
+
+
+
+This example deploys an AKS cluster, creates an Azure User Assigned Managed Identity, and sets credentials to manage access to the cluster.
+
+## Deploying the App
+
+To deploy your infrastructure, follow the below steps.
+
+### Prerequisites
+
+1. [Install Pulumi](https://www.pulumi.com/docs/get-started/install/)
+1. [Configure Azure Credentials](https://www.pulumi.com/docs/intro/cloud-providers/azure/setup/)
+
+### Steps
+
+After [cloning](https://github.com/pulumi/examples#checking-out-a-single-example) this repo, from this working directory, run these commands:
+
+1. Create a new stack, which is an isolated deployment target for this example:
+
+ ```bash
+ $ pulumi stack init dev
+ ```
+
+1. Set the Azure region location to use:
+
+ ```
+ $ pulumi config set azure-native:location westus2
+ ```
+
+1. Stand up the cluster by invoking pulumi
+ ```bash
+ $ pulumi up
+ ```
+
+1. After 3-4 minutes, your cluster will be ready, and the kubeconfig YAML you'll use to connect to the cluster will be available as an [Output](https://www.pulumi.com/docs/concepts/inputs-outputs/#outputs). You can save this kubeconfig to a file like so:
+
+ ```bash
+ $ pulumi stack output kubeconfig --show-secrets > kubeconfig.yaml
+ ```
+
+ Once you have this file in hand, you can interact with your new cluster as usual via `kubectl`:
+
+ ```bash
+ $ KUBECONFIG=./kubeconfig.yaml kubectl get nodes
+ ```
+
+1. From there, feel free to experiment. Simply making edits and running `pulumi up` will incrementally update your stack.
+
+1. Once you've finished experimenting, tear down your stack's resources by destroying and removing it:
+
+ ```bash
+ $ pulumi destroy --yes
+ $ pulumi stack rm --yes
+ ```
+
diff --git a/content/registry/packages/azure-native/how-to-guides/azure-py-aks-managed-identity.md b/content/registry/packages/azure-native/how-to-guides/azure-py-aks-managed-identity.md
new file mode 100644
index 000000000000..71f7ed612b72
--- /dev/null
+++ b/content/registry/packages/azure-native/how-to-guides/azure-py-aks-managed-identity.md
@@ -0,0 +1,77 @@
+---
+title: "Azure Kubernetes Service (AKS) Cluster using the native Azure Provider | Python"
+h1: "Azure Kubernetes Service (AKS) Cluster using the native Azure Provider"
+linktitle: "Azure Kubernetes Service (AKS) Cluster using the native Azure Provider"
+meta_desc: "Azure Kubernetes Service (AKS) Cluster using the native Azure Provider How-to Guide using Python"
+no_edit_this_page: true
+cloud: azure
+language: py
+layout: package
+---
+
+
+
+
+
+
+ View Code
+
+
+
+
+
+
+
+This example deploys an AKS cluster, creates an Azure User Assigned Managed Identity, and sets credentials to manage access to the cluster.
+
+## Deploying the App
+
+To deploy your infrastructure, follow the below steps.
+
+### Prerequisites
+
+1. [Install Pulumi](https://www.pulumi.com/docs/get-started/install/)
+1. [Configure Azure Credentials](https://www.pulumi.com/docs/intro/cloud-providers/azure/setup/)
+
+### Steps
+
+After [cloning](https://github.com/pulumi/examples#checking-out-a-single-example) this repo, from this working directory, run these commands:
+
+1. Create a new stack, which is an isolated deployment target for this example:
+
+ ```bash
+ $ pulumi stack init dev
+ ```
+
+1. Set the Azure region location to use:
+
+ ```
+ $ pulumi config set azure-native:location westus2
+ ```
+
+1. Stand up the cluster by invoking pulumi
+ ```bash
+ $ pulumi up
+ ```
+
+1. After 3-4 minutes, your cluster will be ready, and the kubeconfig YAML you'll use to connect to the cluster will be available as an [Output](https://www.pulumi.com/docs/concepts/inputs-outputs/#outputs). You can save this kubeconfig to a file like so:
+
+ ```bash
+ $ pulumi stack output kubeconfig --show-secrets > kubeconfig.yaml
+ ```
+
+ Once you have this file in hand, you can interact with your new cluster as usual via `kubectl`:
+
+ ```bash
+ $ KUBECONFIG=./kubeconfig.yaml kubectl get nodes
+ ```
+
+1. From there, feel free to experiment. Simply making edits and running `pulumi up` will incrementally update your stack.
+
+1. Once you've finished experimenting, tear down your stack's resources by destroying and removing it:
+
+ ```bash
+ $ pulumi destroy --yes
+ $ pulumi stack rm --yes
+ ```
+
diff --git a/content/registry/packages/azure-native/how-to-guides/azure-ts-aks-managed-identity.md b/content/registry/packages/azure-native/how-to-guides/azure-ts-aks-managed-identity.md
new file mode 100644
index 000000000000..db43e33801e7
--- /dev/null
+++ b/content/registry/packages/azure-native/how-to-guides/azure-ts-aks-managed-identity.md
@@ -0,0 +1,77 @@
+---
+title: "Azure Kubernetes Service (AKS) Cluster using the native Azure Provider | TypeScript"
+h1: "Azure Kubernetes Service (AKS) Cluster using the native Azure Provider"
+linktitle: "Azure Kubernetes Service (AKS) Cluster using the native Azure Provider"
+meta_desc: "Azure Kubernetes Service (AKS) Cluster using the native Azure Provider How-to Guide using TypeScript"
+no_edit_this_page: true
+cloud: azure
+language: ts
+layout: package
+---
+
+
+
+
+
+
+ View Code
+
+
+
+
+
+
+
+This example deploys an AKS cluster, creates an Azure User Assigned Managed Identity, and sets credentials to manage access to the cluster.
+
+## Deploying the App
+
+To deploy your infrastructure, follow the below steps.
+
+### Prerequisites
+
+1. [Install Pulumi](https://www.pulumi.com/docs/get-started/install/)
+1. [Configure Azure Credentials](https://www.pulumi.com/docs/intro/cloud-providers/azure/setup/)
+
+### Steps
+
+After [cloning](https://github.com/pulumi/examples#checking-out-a-single-example) this repo, from this working directory, run these commands:
+
+1. Create a new stack, which is an isolated deployment target for this example:
+
+ ```bash
+ $ pulumi stack init dev
+ ```
+
+1. Set the Azure region location to use:
+
+ ```
+ $ pulumi config set azure-native:location westus2
+ ```
+
+1. Stand up the cluster by invoking pulumi
+ ```bash
+ $ pulumi up
+ ```
+
+1. After 3-4 minutes, your cluster will be ready, and the kubeconfig YAML you'll use to connect to the cluster will be available as an [Output](https://www.pulumi.com/docs/concepts/inputs-outputs/#outputs). You can save this kubeconfig to a file like so:
+
+ ```bash
+ $ pulumi stack output kubeconfig --show-secrets > kubeconfig.yaml
+ ```
+
+ Once you have this file in hand, you can interact with your new cluster as usual via `kubectl`:
+
+ ```bash
+ $ KUBECONFIG=./kubeconfig.yaml kubectl get nodes
+ ```
+
+1. From there, feel free to experiment. Simply making edits and running `pulumi up` will incrementally update your stack.
+
+1. Once you've finished experimenting, tear down your stack's resources by destroying and removing it:
+
+ ```bash
+ $ pulumi destroy --yes
+ $ pulumi stack rm --yes
+ ```
+
diff --git a/content/registry/packages/azure-native/how-to-guides/azure-yaml-aks-managed-identity.md b/content/registry/packages/azure-native/how-to-guides/azure-yaml-aks-managed-identity.md
new file mode 100644
index 000000000000..409204090b1e
--- /dev/null
+++ b/content/registry/packages/azure-native/how-to-guides/azure-yaml-aks-managed-identity.md
@@ -0,0 +1,77 @@
+---
+title: "Azure Kubernetes Service (AKS) Cluster using the native Azure Provider | YAML"
+h1: "Azure Kubernetes Service (AKS) Cluster using the native Azure Provider"
+linktitle: "Azure Kubernetes Service (AKS) Cluster using the native Azure Provider"
+meta_desc: "Azure Kubernetes Service (AKS) Cluster using the native Azure Provider How-to Guide using YAML"
+no_edit_this_page: true
+cloud: azure
+language: yaml
+layout: package
+---
+
+
+
+
+
+
+ View Code
+
+
+
+
+
+
+
+This example deploys an AKS cluster, creates an Azure User Assigned Managed Identity, and sets credentials to manage access to the cluster.
+
+## Deploying the App
+
+To deploy your infrastructure, follow the below steps.
+
+### Prerequisites
+
+1. [Install Pulumi](https://www.pulumi.com/docs/get-started/install/)
+1. [Configure Azure Credentials](https://www.pulumi.com/docs/intro/cloud-providers/azure/setup/)
+
+### Steps
+
+After cloning this repo, from this working directory, run these commands:
+
+1. Create a new stack, which is an isolated deployment target for this example:
+
+ ```bash
+ $ pulumi stack init dev
+ ```
+
+1. Set the Azure region location to use:
+
+ ```
+ $ pulumi config set azure-native:location westus2
+ ```
+
+1. Stand up the cluster by invoking pulumi
+ ```bash
+ $ pulumi up
+ ```
+
+1. After 3-4 minutes, your cluster will be ready, and the kubeconfig YAML you'll use to connect to the cluster will be available as an output. You can save this kubeconfig to a file like so:
+
+ ```bash
+ $ pulumi stack output kubeconfig --show-secrets > kubeconfig.yaml
+ ```
+
+ Once you have this file in hand, you can interact with your new cluster as usual via `kubectl`:
+
+ ```bash
+ $ KUBECONFIG=./kubeconfig.yaml kubectl get nodes
+ ```
+
+1. From there, feel free to experiment. Simply making edits and running `pulumi up` will incrementally update your stack.
+
+1. Once you've finished experimenting, tear down your stack's resources by destroying and removing it:
+
+ ```bash
+ $ pulumi destroy --yes
+ $ pulumi stack rm --yes
+ ```
+