More Windows references removed

Scenarios/AKS-Secure-Baseline-PrivateCluster/README.md

@@ -26,10 +26,8 @@ For this scenario, we have various IaC technology that you can choose from depen
 * Azure Monitor for Containers
 * Azure Firewall
 * Azure Front Door
-* Azure Application Proxy
 * MongoDB 
 * Helm
-* [Group managed service accounts on Windows deployments](https://learn.microsoft.com/en-us/azure/aks/use-group-managed-service-accounts) (GMSA)
 * [Secret store CSI driver](https://learn.microsoft.com/azure/aks/csi-secrets-store-driver)
 * [Azure RBAC for Kubernetes Authorization](https://learn.microsoft.com/azure/aks/manage-azure-rbac)
 * [Azure Active Directory pod-managed identities](https://learn.microsoft.com/azure/aks/use-azure-ad-pod-identity)

Scenarios/AKS-Secure-Baseline-PrivateCluster/Terraform/01-prerequisites.md

@@ -7,7 +7,6 @@
 
         - Contributor role is required at the subscription level to have the ability to create resource groups and perform deployments.
         - User Access Administrator role is required at the subscription level since you'll be performing role assignments to managed identities across various resource groups.
-        - Global Admin on Azure AD Tenant is required for setting up Azure Application Proxy. This setup is done manually. An admin could perform this step for you as it's the last step in the setup after deploying your application. 
     Please follow [these instructions](https://learn.microsoft.com/azure/active-directory/develop/howto-create-service-principal-portal) to create a service principal in Azure. 
 2. PowerShell terminal. This reference reference implementation uses PowerShell for deployment.
 3. Latest [Azure CLI installed](https://learn.microsoft.com/en-us/cli/azure/install-azure-cli)