Update Troubleshoot doc - 3

Author: NirajC-Microsoft

docs/TroubleShootingSteps.md

@@ -70,12 +70,16 @@ Use these as quick reference guides to unblock your deployments.
 
 ### Resource Identification & References
 
-<details>
-<summary><b>LinkedInvalidPropertyId/ ResourceNotFound/DeploymentOutputEvaluationFailed/ CanNotRestoreANonExistingResource / The language expression property array index is out of bounds</b></summary>
-  
-- Before using any resource ID, ensure it follows the correct format.
-- Verify that the resource ID you are passing actually exists.
-- Make sure there are no typos in the resource ID.
+| Issue/Error Code | Description | Steps to Resolve |
+|-----------------|-------------|------------------|
+| **LinkedInvalidPropertyId/ ResourceNotFound/DeploymentOutputEvaluationFailed/ CanNotRestoreANonExistingResource / The language expression property array index is out of bounds** | | - Before using any resource ID, ensure it follows the correct format<br>- Verify that the resource ID you are passing actually exists<br>- Make sure there are no typos in the resource ID<br>- Verify that the provisioning state of the existing resource is `Succeeded` by running the following command to avoid this error while deployment or restoring the resource:<br>`az resource show --ids <Resource ID> --query "properties.provisioningState"`<br>- Sample Resource IDs format:<br>  - Log Analytics Workspace Resource ID: `/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.OperationalInsights/workspaces/{workspaceName}`<br>  - Azure AI Foundry Project Resource ID: `/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MachineLearningServices/workspaces/{name}`<br>- You may encounter the error `The language expression property array index '8' is out of bounds` if the resource ID is incomplete. Please ensure your resource ID is correct and contains all required information, as shown in sample resource IDs<br>- For more information refer [Resource Not Found errors solutions](https://learn.microsoft.com/en-us/azure/azure-resource-manager/troubleshooting/error-not-found?tabs=bicep) |
+| **ParentResourceNotFound** | | - You can refer to the [Parent Resource Not found](https://learn.microsoft.com/en-us/azure/azure-resource-manager/troubleshooting/error-parent-resource?tabs=bicep) documentation if you encounter this error |
+| **PrincipalNotFound** | | - This error occurs when the **principal ID** (Service Principal, User, or Group) specified in a role assignment or deployment does not exist in the Azure Active Directory tenant<br>- It can also happen due to **replication delays** right after creating a new principal<br>**Example causes:**<br>- The specified **Object ID** is invalid or belongs to another tenant<br>- The principal was recently created but Azure AD has not yet replicated it<br>- Attempting to assign a role to a non-existing or deleted Service Principal/User/Group<br>**How to fix:**<br>1. Verify that the **principal ID is correct** and exists in the same directory/tenant: `az ad sp show --id <object-id>`<br>2. If the principal was just created, wait a few minutes and retry<br>3. Explicitly set the principalType property (ServicePrincipal, User, or Group) in your ARM/Bicep template to avoid replication delays<br>4. If the principal does not exist, create it again before assigning roles<br>- For more details, see [Azure PrincipalType documentation](https://learn.microsoft.com/en-us/azure/role-based-access-control/troubleshooting?tabs=bicep) |
+| **SubscriptionDoesNotHaveServer** | | - This issue happens when you try to reference an **Azure SQL Server** (`Microsoft.Sql/servers`) that does not exist in the selected subscription<br>- It can occur if: The SQL server name is typed incorrectly; The SQL server was **deleted** but is still being referenced; You are working in the **wrong subscription context**; The server exists in a **different subscription/tenant** where you don't have access<br>**Reproduce:**<br>Run an Azure CLI command with a non-existent server name:<br>`az sql db list --server sql-doesnotexist --resource-group myResourceGroup`<br>or<br>`az sql server show --name sql-caqfrhxr4i3hyj --resource-group myResourceGroup`<br>**Resolution:**<br>- Verify the SQL Server name exists in your subscription: `az sql server list --output table`<br>- Make sure you are targeting the correct subscription:<br>`az account show`<br>`az account set --subscription <subscription-id>`<br>- If the server was deleted, either restore it (if possible) or update references to use a valid existing server |
+
+---------------------------------
+
+ ### Network & Infrastructure Configuration
 - Verify that the provisioning state of the existing resource is `Succeeded` by running the following command to avoid this error while deployment or restoring the resource.
 
     ```