:Refactor docs so quick start instructions are for creating an AKS management cluster with workload identity

Author: alimaazamat

docs/book/src/getting-started-with-aks.md

@@ -0,0 +1,107 @@
+# Getting started with cluster-api-provider-azure
+
+## Prerequisites
+
+### Requirements
+
+<!-- markdown-link-check-disable-next-line -->
+- A [Microsoft Azure account](https://azure.microsoft.com/)
+  - Note: If using a new subscription, make sure to [register](https://learn.microsoft.com/azure/azure-resource-manager/management/resource-providers-and-types) the following resource providers:
+    - `Microsoft.Compute`
+    - `Microsoft.Network`
+    - `Microsoft.ContainerService`
+    - `Microsoft.ManagedIdentity`
+    - `Microsoft.Authorization`
+    - `Microsoft.ResourceHealth` (if the `EXP_AKS_RESOURCE_HEALTH` feature flag is enabled)
+- Install the [Azure CLI](https://learn.microsoft.com/cli/azure/install-azure-cli?view=azure-cli-latest)
+- A [supported version](https://github.com/kubernetes-sigs/cluster-api-provider-azure#compatibility) of `clusterctl`
+
+### Setting up your Azure environment
+
+  1. Login with the Azure CLI.
+
+   ```bash
+  az login
+   ```
+
+  2. List your Azure subscriptions.
+
+   ```bash
+  az account list -o table
+   ```
+
+  3. If more than one account is present, select the account that you want to use.
+
+   ```bash
+  az account set -s <SubscriptionId>
+   ```
+
+  4. Save your Subscription ID in an environment variable.
+
+  ```bash
+  export AZURE_SUBSCRIPTION_ID="<SubscriptionId>"
+  ```
+### Creating an AKS Management Cluster with Workload Identity
+
+  1. Create an AKS Cluster with Workload Identity and OIDC Endpoint Enabled.
+  ```bash
+  az aks create \
+  --resource-group <resource-group-name> \
+  --name <aks-cluster-name> \
+  --enable-oidc-issuer \
+  --enable-workload-identity \
+  --node-count 2 \
+  --node-vm-size Standard_B2s \
+  --generate-ssh-keys \
+  --location <region>
+  ```
+  
+  2. Retrieve Credentials for the AKS Cluster to interact with it using kubectl:
+  ```bash
+  az aks get-credentials --resource-group <resource-group-name> --name <aks-cluster-name>
+  ```
+
+  3. Retrieve the OIDC Issuer URL and OIDC issuer URL.
+  ```bash
+  az aks show \
+  --resource-group <resource-group-name> \
+  --name <aks-cluster-name> \
+  --query "oidcIssuerProfile.issuerUrl" -o tsv
+  ```
+  Hold onto the OIDC issuer URL for creating federated credentials.
+
+  4. Create a User Assigned Managed Identity (UAMI) to use for Workload Identity.
+  ```bash
+  az identity create \
+  --name <uami-name> \
+  --resource-group <resource-group-name> \
+  --location <region>
+  ```
+  Hold onto the UAMI clientID and principalID for the next step.
+
+  5. Assign the Contributor role to the UAMI so it can manage Azure resources.
+  ```bash
+  az role assignment create \
+  --assignee <uami-principal-id> \
+  --role Contributor \
+  --scope /subscriptions/<subscription-id>
+  ```
+
+  6. Add a Federated Credential to the UAMI
+
+To configure the federated credential for the UAMI, follow the detailed instructions in the [Azure Workload Identity: Federated identity credential for an Azure AD application](https://azure.github.io/azure-workload-identity/docs/topics/federated-identity-credential.html#federated-identity-credential-for-a-user-assigned-managed-identity).
+For CAPZ, the federated credential should be configured for the capz-manager service account in the capz-system namespace.
+
+  7. Annotate the capz-manager service account in the capz-system namespace with the UAMI's clientId:
+  ```bash
+  kubectl annotate serviceaccount capz-manager \
+  -n capz-system \
+  azure.workload.identity/client-id=<uami-client-id>
+  ```
+
+### Building your first cluster
+
+The recommended way to build a cluster is to install a CAPZ management cluster using [Cluster API Operator](https://github.com/kubernetes-sigs/cluster-api-operator), then utilizing a Helm chart to create a workload cluster, specifically an [ASO Managed Cluster](./managed/asomanagedcluster.md).
+
+To create a cluster manually, check out the [Cluster API Quick Start](https://cluster-api.sigs.k8s.io/user/quick-start.html) for in-depth instructions. Make sure to select the "Azure" tabs. If you are looking to install additional ASO CRDs, set `ADDITIONAL_ASO_CRDS` to the list of CRDs you want to install. Refer to adding additional CRDs for Azure Service Operator [here](./topics/aso.md#Using-aso-for-non-capz-resources).
+