Merge branch 'main' of https://github.com/MicrosoftDocs/SupportArticles-docs-pr into dotnet-freshness-2025-batch2

Author: haywoodsloan

.openpublishing.redirection.teams.json

@@ -1,5 +1,8 @@
 {
   "redirections": [
-    
+    {
+      "source_path": "Teams/teams-rooms-and-devices/mtr-device-cannot-fetch-calendar.md",
+      "redirect_url": "/previous-versions/troubleshoot/content-retirement"
+     }    
   ]
 }

Exchange/ExchangeOnline/outlook-on-the-web-issues/cannot-open-attachments.md

@@ -14,8 +14,8 @@ search.appverid:
   - MET150
 appliesto: 
   - Exchange Online
-ms.date: 07/01/2025
-ms.reviewer: v-six
+ms.date: 07/15/2025
+ms.reviewer: fernandog
 ---
 # Can't open or view attachments in Outlook on the web
 
@@ -30,7 +30,7 @@ When Microsoft 365 users try to open or view attachments in email messages in Ou
 
 This issue occurs if the attachment is blocked by Outlook on the web. By default, Outlook on the web blocks attachments that have the following file name extensions:
 
-`.ade`,`.adp`,`.apk`,`.app`,`.appx`,`.appcontent-ms`,`.application`,`.appref-ms`,`.asp`,`.aspx`,`.asx`,`.bas`,`.bat`,`.bgi`,`.cab`,`.cdxml`,`.cer`,`.chm`,`.cmd`,`.cnt`,`.com`,`.cpl`,`.crt`,`.csh`,`.der`,`.diagcab`,`.exe`,`.fxp`,`.gadget`,`.grp`,`.hlp`,`.hpj`,`.hta`,`.htc`,`.img`,`.inf`,`.ins`,`.iso`,`.isp`,`.its`,`.jar`,`.jnlp`,`.js`,`.jse`,`.ksh`,`.lnk`,`.mad`,`.maf`,`.mag`,`.mam`,`.maq`,`.mar`,`.mas`,`.mat`,`.mau`,`.mav`,`.maw`,`.mcf`,`.mda`,`.mdb`,`.mde`,`.mdt`,`.mdw`,`.mdz`,`.mht`,`.mhtml`,`.msc`,`.msh`,`.msh1`,`.msh1xml`,`.msh2`,`.msh2xml`,`.mshxml`,`.msi`,`.msp`,`.mst`,`.msu`,`.ops`,`.osd`,`.pcd`,`.pif`,`.pl`,`.plg`,`.prf`,`.prg`,`.printerexport`,`.ps1`,`.ps1xml`,`.ps2`,`.ps2xml`,`.psc1`,`.psc2`,`.psd1`,`.psdm1`,`.pssc`,`.pst`,`.py`,`.pyc`,`.pyo`,`.pyw`,`.pyz`,`.pyzw`,`.reg`,`.scf`,`.scr`,`.sct`,`.settingcontent-ms`,`.shb`,`.shs`,`.theme`,`.tmp`,`.udl`,`.url`,`.vb`,`.vbe`,`.vbp`,`.vbs`,`.vhd`,`.vhdx`,`.vsmacros`,`.vsw`,`.webpnp`,`.website`,`.ws`,`.wsb`,`.wsc`,`.wsf`,`.wsh`,`.xbap`,`.xll`,`.xnk`,`.library-ms`,`.search-ms`
+`.ade`,`.adp`,`.apk`,`.app`,`.appx`,`.appcontent-ms`,`.application`,`.appref-ms`,`.asp`,`.aspx`,`.asx`,`.bas`,`.bat`,`.bgi`,`.cab`,`.cdxml`,`.cer`,`.chm`,`.cmd`,`.cnt`,`.com`,`.cpl`,`.crt`,`.csh`,`.der`,`.diagcab`,`.exe`,`.fxp`,`.gadget`,`.grp`,`.hlp`,`.hpj`,`.hta`,`.htc`,`.img`,`.inf`,`.ins`,`.iso`,`.isp`,`.its`,`.jar`,`.jnlp`,`.js`,`.jse`,`.ksh`,`.library-ms`,`.lnk`,`.mad`,`.maf`,`.mag`,`.mam`,`.maq`,`.mar`,`.mas`,`.mat`,`.mau`,`.mav`,`.maw`,`.mcf`,`.mda`,`.mdb`,`.mde`,`.mdt`,`.mdw`,`.mdz`,`.mht`,`.mhtml`,`.msc`,`.msh`,`.msh1`,`.msh1xml`,`.msh2`,`.msh2xml`,`.mshxml`,`.msi`,`.msp`,`.mst`,`.msu`,`.ops`,`.osd`,`.pcd`,`.pif`,`.pl`,`.plg`,`.prf`,`.prg`,`.printerexport`,`.ps1`,`.ps1xml`,`.ps2`,`.ps2xml`,`.psc1`,`.psc2`,`.psd1`,`.psdm1`,`.pssc`,`.pst`,`.py`,`.pyc`,`.pyo`,`.pyw`,`.pyz`,`.pyzw`,`.reg`,`.scf`,`.scr`,`.search-ms`,`.sct`,`.settingcontent-ms`,`.shb`,`.shs`,`.theme`,`.tmp`,`.udl`,`.url`,`.vb`,`.vbe`,`.vbp`,`.vbs`,`.vhd`,`.vhdx`,`.vsmacros`,`.vsw`,`.webpnp`,`.website`,`.ws`,`.wsb`,`.wsc`,`.wsf`,`.wsh`,`.xbap`,`.xll`,`.xnk`
 
 ## Resolution
 

Teams/TOC.yml

@@ -274,8 +274,6 @@ items:
       href: ./teams-rooms-and-devices/teams-rooms-device-keyboard-size-reduced.md
     - name: Teams Rooms app doesn't start automatically after updates
       href: ./teams-rooms-and-devices/teams-rooms-not-auto-start-after-windows-updates.md
-    - name: Teams Rooms devices can't fetch calendar
-      href: ./teams-rooms-and-devices/mtr-device-cannot-fetch-calendar.md
     - name: Teams Rooms Pro Management
       items:
       - name: Get support for Teams Rooms Pro Management

Teams/teams-rooms-and-devices/media/mtr-device-cannot-fetch-calendar/error.png

@@ -0,0 +1,67 @@
+---
+title: Troubleshoot Hybrid Runbook Worker Job Failures in Azure Automation
+description: Discusses some common issues that might occur when you run a runbook on Hybrid Runbook Worker.
+ms.date: 06/13/2025
+ms.reviewer: adoyle
+ms.service: azure-automation
+ms.custom: sap:Runbook not working as expected
+---
+
+# Hybrid Runbook Worker job isn't working as expected
+
+This article provides guidance for troubleshooting and resolving issues that affect Hybrid Runbook Worker in Azure Automation.
+
+> [!NOTE]
+> Azure Automation enables the recovery of runbooks that are deleted in the past 29 days. For more information, see [Restore deleted runbook](/azure/automation/manage-runbooks#restore-deleted-runbook).
+
+## Troubleshoot connectivity issues
+
+Connectivity problems are a common cause of issues that affect runbooks. Use the [Test Cloud Connectivity tool](/azure/azure-monitor/agents/agent-windows-troubleshoot?tabs=UpdateMMA#connectivity-issues) to verify that your environment is correctly configured.
+
+## General troubleshooting
+
+| **Issue** | **Resolution** |
+|----------|----------------|
+| Runbooks behave differently on a hybrid worker than in Azure Automation. | See [Runbook permissions](/azure/automation/automation-hrw-run-runbooks#runbook-permissions) for information about authentication differences. |
+| Error: No certificate was found. | Follow the "[No Certificate Found](/azure/automation/troubleshoot/hybrid-runbook-worker#no-cert-found)" section in the troubleshooting guide. |
+| You need to troubleshoot a custom runbook. | See [Troubleshoot runbook issues](/azure/automation/troubleshoot/runbooks). |
+| You need to check job status. | Review [job details and statuses](/azure/automation/automation-runbook-execution#job-statuses). |
+| Hybrid worker doesn't run jobs or is unresponsive. | Troubleshoot by using [Hybrid Runbook Worker diagnostics](/azure/automation/troubleshoot/hybrid-runbook-worker). |
+| Runbooks suddenly stop working. | Make sure that you [migrated to managed identity](/azure/automation/migrate-run-as-accounts-managed-identity?tabs=sa-managed-identity#cert-renewal) and that webhooks aren't expired. |
+| Need help with passing parameters into a webhook. | See [Start a runbook from a webhook](/azure/automation/automation-webhooks#parameters-used-when-the-webhook-starts-a-runbook). |
+| You want to use both `Az` and `AzureRM` modules in runbook. | This scenario isn't supported. Use only [Az modules in runbooks](/azure/automation/automation-update-azure-modules). |
+| Can't start or schedule a runbook. | Verify that the runbook is in a [published state](/azure/automation/manage-runbooks#publish-a-runbook). |
+| Runbook is suspended or failed unexpectedly. | Review [job statuses](/azure/automation/automation-runbook-execution#job-statuses). Add logging to the runbook by using [output streams](/azure/automation/automation-runbook-output-and-messages#working-with-message-streams). If the job fails three times, check [the automation limits](/azure/azure-resource-manager/management/azure-subscription-service-limits#automation-limits) and consider using a [Hybrid Worker](/azure/automation/automation-hybrid-runbook-worker). |
+
+
+### Windows Hybrid Runbook Worker issues
+
+| **Issue** | **Resolution** |
+|-----------|----------------|
+| Event 4502 appears in the Operations Manager log. | See [Event 4502](/azure/automation/troubleshoot/hybrid-runbook-worker#event-4502). |
+| Script using `Connect-MsolService` can't connect to Microsoft 365. | See [Sandbox can't connect to Microsoft 365](/azure/automation/troubleshoot/hybrid-runbook-worker#scenario-orchestratorsandboxexe-cant-connect-to-microsoft-365-through-proxy). |
+| Machine is running but not sending heartbeat data. | See [Hybrid worker not reporting](/azure/automation/troubleshoot/hybrid-runbook-worker#corrupt-cache). |
+
+
+### Linux Hybrid Runbook Worker issues
+
+| **Issue** | **Resolution** |
+|-----------|----------------|
+| Unexpected password prompt appears when using `sudo`. | See [Linux runbook worker prompts for password](/azure/automation/troubleshoot/hybrid-runbook-worker#prompt-for-password). |
+| Log file shows "The specified class does not exist." | See [Class does not exist error](/azure/automation/troubleshoot/hybrid-runbook-worker#class-does-not-exist). |
+| Linux job is stuck in **Running** state | 1. Switch to `sudo` permissions: `sudo su`<br>2. Make sure that the `hwd` service is running: `systemctl status hwd.service`<br>3. Open the following file in Hybrid Worker: `vi /lib/systemd/system/hwd.service`<br>4. Update the setting from `CPUQuota=25%` to `CPUQuota=` to make the usage unrestricted, as shown in the following example: <br><br>`[Unit]`<br>`Description=HW Service`<br>`After=network.target`<br>`[Service]`<br>`Type=simple`<br>`ExecStart=/usr/bin/python3 .../automationWorkerStarterScript.py`<br>`TimeoutStartSec=5`<br>`Restart=always`<br>`RestartSec=10s`<br>`TimeoutStopSec=600`<br>`CPUQuota=`<br>`KillMode=process`<br>`[Install]`<br>`WantedBy=multi-user.target`<br><br> 5. Restart the `hwd` service: <br>`systemctl daemon-reload` <br> `systemctl restart hwd.service`<br>|
+
+## Other error messages
+
+| **Error** | **Resolution** |
+|-----------|----------------|
+| "The subscription cannot be found" | This error usually means that the runbook isn't using a managed identity. Follow the steps in [Unable to find subscription](/azure/automation/troubleshoot/runbooks#unable-to-find-subscription). |
+| "Strong authentication enrollment is required." | See [Authentication to Azure failed due to MFA](/azure/automation/troubleshoot/runbooks#auth-failed-mfa). |
+| "No permission" or similar error | Make sure that the [managed identity has appropriate permissions](/azure/role-based-access-control/role-assignments-portal). |
+
+## Reference
+
+- [Automation Hybrid Runbook Worker overview](/azure/automation/automation-hybrid-runbook-worker)  
+- [Deploy a Windows Hybrid Runbook Worker](/azure/automation/automation-windows-hrw-install)  
+- [Deploy a Linux Hybrid Runbook Worker](/azure/automation/automation-linux-hrw-install)  
+- [Run runbooks on a Hybrid Runbook Worker](/azure/automation/automation-hrw-run-runbooks)

Teams/teams-rooms-and-devices/mtr-device-cannot-fetch-calendar.md

@@ -2,6 +2,8 @@
   href: welcome-automation.yml
 - name: Runbook not working as expected
   items:
+  - name: Hybrid Runbook Worker job isn't working
+    href: runbooks/runbook-fails-on-hybrid-worker.md
   - name: Runbook jobs get suspended
     href: runbooks/runbook-job-suspended.md
   - name: Troubleshoot error codes during runbook execution
@@ -14,3 +16,5 @@
     href: runbooks/troubleshoot-runbook-execution-issues.md
   - name: Troubleshoot runbook execution issues when using PowerShell
     href: runbooks/powershell-job-script-cmdlets-not-working.md
+  - name: Troubleshoot Hybrid Runbook Worker Job Failures
+    href: runbooks/troubleshoot-runbook-execution-issues.md