Merge pull request #8253 from MicrosoftDocs/main

Auto push to live 2025-02-19 02:00:03

Author: Deland-Han

.openpublishing.redirection.json

@@ -12695,6 +12695,66 @@
     {
       "source_path": "support/mem/configmgr/update-management/wsus-not-sync-with-certificate-error-800b0109.md",
       "redirect_url": "/previous-versions/troubleshoot/configmgr/wsus-not-sync-with-certificate-error-800b0109"
+    },
+    {
+      "source_path": "support/dynamics-365/sales/app-does-not-appear-within-outlook.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/app-does-not-appear-within-outlook"
+    },
+    {
+      "source_path": "support/dynamics-365/sales/current-user-role-not-have-required-permissions.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/current-user-role-not-have-required-permissions"
+    },
+    {
+      "source_path": "support/dynamics-365/sales/errors-when-opening-365-app-outlook.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/errors-when-opening-365-app-outlook"
+    },
+    {
+      "source_path": "support/dynamics-365/sales/error-when-installing-crm-2016-outlook.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/error-when-installing-crm-2016-outlook"
+    },
+    {
+      "source_path": "support/dynamics-365/sales/experience-without-server-side-synchronization.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/experience-without-server-side-synchronization"
+    },
+    {
+      "source_path": "support/dynamics-365/sales/new-forms-formatted-incorrectly.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/new-forms-formatted-incorrectly"
+    },
+    {
+      "source_path": "support/dynamics-365/sales/something-went-wrong-during-sign.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/something-went-wrong-during-sign"
+    },
+    {
+      "source_path": "support/dynamics-365/sales/something-went-wrong-during-sign-in.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/something-went-wrong-during-sign-in"
+    },
+    {
+      "source_path": "support/dynamics-365/sales/the-authentication-was-not-successful.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/the-authentication-was-not-successful"
+    },
+    {
+      "source_path": "support/dynamics-365/sales/the-given-key-was-not-present-in-dictionary.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/the-given-key-was-not-present-in-dictionary"
+    },
+    {
+      "source_path": "support/dynamics-365/sales/this-organization-has-already-been-configured-error-when-connecting.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/this-organization-has-already-been-configured-error-when-connecting"
+    },
+    {
+      "source_path": "support/dynamics-365/sales/track-set-regarding-options-miss.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/track-set-regarding-options-miss"
+    },
+    {
+      "source_path": "support/dynamics-365/sales/troubleshoot-dynamics-365-app-outlook.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/troubleshoot-dynamics-365-app-outlook"
+    },
+    {
+      "source_path": "support/dynamics-365/sales/we-cannot-load-this-app.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/we-cannot-load-this-app"
+    },
+    {
+      "source_path": "support/dynamics-365/sales/your-device-is-currently-unsupported.md",
+      "redirect_url": "/troubleshoot/power-platform/dataverse/d365-app-outlook/your-device-is-currently-unsupported"
     }
   ]
 }

support/azure/.openpublishing.redirection.azure.json

@@ -6279,6 +6279,10 @@
         "source_path": "azure-kubernetes/connectivity/stale-watch-azure-ad-pod-identity-nmi-status-500.md",
         "redirect_url": "/troubleshoot/azure/azure-kubernetes/welcome-azure-kubernetes",
         "redirect_document_id": false
+      },
+      {
+        "source_path": "azure-monitor/app-insights/availability/profiler-troubleshooting.md",
+        "redirect_url": "/azure/azure-monitor/profiler/profiler-troubleshooting"
       }
   ]
 }

support/azure/azure-monitor/app-insights/availability/media/profiler-troubleshooting/profiler-web-job-log.png

@@ -65,8 +65,6 @@ items:
         href: app-insights/availability/missing-cpu-total-committed-memory-metrics.md
       - name: Portal connectivity issues
         href: app-insights/availability/troubleshoot-portal-connectivity.md
-      - name: Troubleshoot Application Insights Profiler
-        href: app-insights/availability/profiler-troubleshooting.md
       - name: Troubleshoot Code Optimizations (Preview)
         href: app-insights/availability/code-optimizations-troubleshooting.md
       - name: Troubleshoot user behavior analytics tools in Azure Application Insights

support/azure/azure-monitor/app-insights/availability/media/profiler-troubleshooting/profiler-web-job.png

@@ -121,7 +121,7 @@ VMs might restart because of issues within the VM itself. The workload or role t
 
 ### Storage-related forced shutdowns
 
-VMs in Azure rely on virtual disks for operating system and data storage that is hosted on the Azure Storage infrastructure. Whenever the availability or connectivity between the VM and the associated virtual disks is affected for more than 120 seconds, the Azure platform performs a forced shutdown of the VMs to avoid data corruption. The VMs are automatically powered back on after storage connectivity has been restored. The duration of the shutdown can be as short as five minutes but can be significantly longer.
+VMs in Azure rely on virtual disks for operating system and data storage that is hosted on the Azure Storage infrastructure. Whenever the availability or connectivity between the VM and the associated virtual disks is affected for more than 180 seconds, the Azure platform performs a forced shutdown of the VMs to avoid data corruption. The VMs are automatically powered back on after storage connectivity has been restored. The duration of the shutdown can be as short as five minutes but can be significantly longer.
 
 ### Other incidents