prerequities updated

Author: Ravikirana-Microsoft

README.md

@@ -105,6 +105,24 @@ Use the [Azure pricing calculator](https://azure.microsoft.com/en-us/pricing/cal
 
 <br/>
 
+  Prerequisite — enable the Microsoft.Compute/EncryptionAtHost feature for every subscription (and region, if applicable) where you plan to deploy VMs or scale sets with encryptionAtHost: true. Repeat the steps below for each target subscription.
+
+  Steps to enable the feature:
+  1. Set the target subscription:
+     Run: <code>az account set --subscription "&lt;YourSubscriptionId&gt;"</code>
+  2. Register the feature (one time per subscription):
+     Run: <code>az feature register --name EncryptionAtHost --namespace Microsoft.Compute</code>
+  3. Wait until registration completes and shows "Registered":
+     Run: <code>az feature show --name EncryptionAtHost --namespace Microsoft.Compute --query properties.state -o tsv</code>
+  4. Refresh the provider (if required):
+     Run: <code>az provider register --namespace Microsoft.Compute</code>
+  5. Re-run the deployment after registration is complete.
+
+  Note: Feature registration can take several minutes. Ensure the feature is registered before attempting deployments that require encryptionAtHost.
+
+  Reference: Azure Host Encryption — https://learn.microsoft.com/azure/virtual-machines/disks-enable-host-based-encryption-portal?tabs=azure-cli
+
+
 >⚠️ **Important:** To avoid unnecessary costs, remember to take down your app if it's no longer in use,
 either by deleting the resource group in the Portal or running `azd down`.
 

docs/TroubleShootingSteps.md

@@ -297,35 +297,5 @@ The subscription 'xxxx-xxxx' cannot have more than 1 Container App Environments
 
 </details>
 
-<details>
-<summary><b>EncryptionAtHostFeatureNotEnabled</b></summary>
-
-This error appears when a resource (typically a Virtual Machine or scale set) sets the property <code>encryptionAtHost: true</code> but the subscription isn't enabled for the feature <code>Microsoft.Compute/EncryptionAtHost</code> in that region.
-
-Example error snippet:
-
-<pre>
-{"code":"InvalidTemplateDeployment","message":"The template deployment failed with error: 'The feature Microsoft.Compute/EncryptionAtHost is not enabled for subscription <sub-id> in location <region>.'"}
-</pre>
-
-Why it happens:
- - The host-level encryption capability is a gated feature. Subscriptions must register the feature (and sometimes wait for registration to complete) before provisioning VMs with it enabled.
- - Attempting to force it on before registration completes blocks deployment.
-
-How to fix:
- 1. Set the subscription
-        - Run: <code>az account set --subscription "yourSubIDHere"</code>
- 2. Register the feature (one time per subscription):
-        - Run: <code>az feature register --name EncryptionAtHost --namespace Microsoft.Compute</code>
- 3. Check status until it shows "Registered":
-        - <code>az feature show --name EncryptionAtHost --namespace Microsoft.Compute</code>
- 4. Re-run the deployment.
-
-Reference docs:
- - Azure Host Encryption: https://learn.microsoft.com/en-us/azure/virtual-machines/disks-enable-host-based-encryption-portal?tabs=azure-cli
-
-</details>
-<br/>
-<br/>
 💡 Note: If you encounter any other issues, you can refer to the [Common Deployment Errors](https://learn.microsoft.com/en-us/azure/azure-resource-manager/troubleshooting/common-deployment-errors) documentation.
 If the problem persists, you can also raise an bug in our [MACAE Github Issues](https://github.com/microsoft/Multi-Agent-Custom-Automation-Engine-Solution-Accelerator/issues) for further support.