Azure Messaging SDK Troubleshooting

9 steps · start to finish.

1. 1
   Step 1

   Environment Setup

   ▶

   Verify MCP tools are available and output directory is ready.

   echo "=== ENVIRONMENT SETUP ==="
   mkdir -p /app/results
   
   # Verify required MCP tools are accessible
   for tool in mcp_azure_mcp_resourcehealth mcp_azure_mcp_documentation mcp_azure_mcp_eventhubs mcp_azure_mcp_servicebus mcp_azure_mcp_monitor; do
     echo "Checking: $tool"
   done
   
   echo "Output directory: /app/results"
   echo "Setup complete"
   

   Confirm that error_description is provided. If missing, ask the user to describe the error or symptom before continuing.

   ---

2. 2
   Step 2

   Identify the SDK and Version

   ▶

   Examine the user's prompt for SDK and version clues.

3. 3
   Step 3

   Check Resource Health

   ▶

   Use `mcp_azure_mcp_resourcehealth` to verify the namespace is healthy before assuming an SDK bug.

4. 4
   Step 4

   Classify the Error

   ▶

   Match the `error_description` against the following categories. Stop at the first match.

5. 5
   Step 5

   Look Up Documentation (max 3 rounds)

   ▶

   Use `mcp_azure_mcp_documentation` to search Microsoft Learn for the matched error category.

6. 6
   Step 6

   Diagnose with Logs (if namespace_name is known)

   ▶

   Query Azure Monitor for relevant error events from the last hour.

7. 7
   Step 7

   Verify Configuration

   ▶

   Check the following configuration parameters that commonly cause the reported error:

8. 8
   Step 8

   Recommend Fix

   ▶

   Compose the remediation recommendation. The recommendation must:

9. 9
   Step 9

   Iterate on Incomplete Diagnosis (max 3 rounds)

   ▶

   If the diagnosis is inconclusive after Steps 4–8: