diff --git a/support/azure/partner-solutions/new-relic/resource-monitoring-troubleshoot.md b/support/azure/partner-solutions/new-relic/resource-monitoring-troubleshoot.md
@@ -20,7 +20,6 @@ This article helps you troubleshoot situations in which New Relic stops receivin
 
 - Access to the New Relic account that owns the ingest API key (API key admin or owner).
 - Access to the Azure subscription and resource group that contain the affected resources (Reader to view, Contributor/Owner to remediate or change billing).
-- Familiarity with the Azure portal, the New Relic portal, and basic CLI (Azure CLI or PowerShell) commands.
  
 ## Causes and solutions
 
diff --git a/support/azure/partner-solutions/toc.yml b/support/azure/partner-solutions/toc.yml
@@ -51,5 +51,6 @@ items:
       href: log-forwarding-persists.md
     - name: Log limitations
       href: log-limitations.md
-
-
+    - name: Resource monitoring stopped working
+      href: resource-monitoring-troubleshoot.md
+       
