update links

Author: ProfessorKendrick

articles/partner-solutions/dynatrace/.openpublishing.redirection.partner-solutions-dynatrace.json

@@ -33,7 +33,12 @@
         {
             "source_path_from_root": "/articles/partner-solutions/dynatrace/dynatrace-get-support.md",
             "redirect_url": "/azure/partner-solutions/dynatrace/support",
-            "redirect_document_id": true
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/partner-solutions/dynatrace/dynatrace-get-support.md",
+            "redirect_url": "/azure/partner-solutions/dynatrace/overview",
+            "redirect_document_id": false
         },
         {
             "source_path_from_root": "/articles/partner-solutions/dynatrace/dynatrace-troubleshoot.md",

articles/partner-solutions/new-relic/.openpublishing.redirection.partner-solutions-new-relic.json

@@ -18,7 +18,12 @@
         {
             "source_path_from_root": "/articles/partner-solutions/new-relic/new-relic-get-support.md",
             "redirect_url": "/azure/partner-solutions/new-relic/support",
-            "redirect_document_id": true
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/partner-solutions/new-relic/new-relic-get-support.md",
+            "redirect_url": "/azure/partner-solutions/new-relic/overview",
+            "redirect_document_id": false
         },
         {
             "source_path_from_root": "/articles/partner-solutions/new-relic/new-relic-troubleshoot.md",

articles/partner-solutions/new-relic/troubleshoot.md

@@ -45,7 +45,3 @@ New Relic manages the APIs for creating and managing resources, and for the stor
 If logs are being emitted and diagnostic settings remain active on monitored resources even after the New Relic resource is disabled or tag rules were modified to exclude certain resources, it's likely that there's a delete lock applied to the resources or the resource group containing the resource. This lock prevents the cleanup of the diagnostic settings, and hence, logs continue to be forwarded for those resources. To resolve the issue, remove the delete lock from the resource or the resource group. If the lock is removed after the New Relic resource is deleted, the diagnostic settings have to be cleaned up manually to stop log forwarding.
 
 [!INCLUDE [diagnostic-settings](../includes/diagnostic-settings.md)]
-
-## Next steps
-
-- [Get support for Azure Native New Relic Service](support.md)