Merge pull request #9254 from MicrosoftDocs/main

1 new MTRA issue, updated 1 MTRW issue, removed 2 MTRW issues and updated 1 ExO article

Author: Cloud-Writer

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

@@ -1,6 +1,6 @@
 ---
-title: Microsoft 365 users can't open or view attachments in Outlook on the web
-description: Describes an issue in which Outlook on the web attachments can't be viewed or opened in Microsoft 365. Provides a resolution and a workaround.
+title: Can't open or view attachments in Outlook on the web
+description: Provides a resolution for an issue in which Outlook on the web attachments can't be viewed or opened in Microsoft 365. 
 author: cloud-writer
 ms.author: meerak
 audience: ITPro
@@ -14,12 +14,12 @@ search.appverid:
   - MET150
 appliesto: 
   - Exchange Online
-ms.date: 01/24/2024
+ms.date: 07/01/2025
 ms.reviewer: v-six
 ---
-# Microsoft 365 users can't open or view attachments in Outlook on the web
+# Can't open or view attachments in Outlook on the web
 
-## Problem
+## Symptoms
 
 When Microsoft 365 users try to open or view attachments in email messages in Outlook on the web, they experience the following symptoms:
 
@@ -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`, `.appcontent-ms`, `.application`, `.appref-ms`, `.appx`, `.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`, `.msh2`, `.mshxml`, `.msh1xml`, `.msh2xml`, `.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`
+`.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`
 
 ## Resolution
 
@@ -52,7 +52,7 @@ Things to consider:
 
 ## Workaround
 
-Direct users to compress the files that they intend to send (for example, as a .zip file) and then send the compressed files as attachments.
+If the mailbox policy can't be changed, then direct users to compress the files that they intend to send, such as .zip file, and then send the compressed file as an attachment.
 
 ## More information
 

Teams/teams-rooms-and-devices/teams-rooms-known-issues-android.md

@@ -23,7 +23,7 @@ appliesto:
   - Microsoft Teams
 search.appverid: 
   - MET150
-ms.date: 05/29/2025
+ms.date: 07/01/2025
 ---
 # Known issues with Teams Rooms on Android
 
@@ -43,6 +43,7 @@ ms.date: 05/29/2025
 |Can't add, delete, or edit contacts on Teams phones|You can't perform the add, delete, and edit operations on contacts from Teams phones.|Use either the Teams desktop or the Teams web client to perform these actions.|
 |Can't resume a call after using **Consult first** option on Teams phones | After using the **Consult first** option in the **Transfer** menu when you select the **Resume** option to resume the call, the call fails. | End the call made by using the **Consult first** option and then resume the original call.|
 |Unable to assign speed dial to line keys on a sidecar|When you assign speed dial contacts to line keys on the sidecar that is connected to a touch phone device, they don't work.|No workaround is available for the speed dial contacts that you assigned by using the sidecar. However the speed dial contacts that're already set up and shared line delegates and other groups are automatically pinned on the sidecar.|
+|Speed dial line key doesn't transfer an active call.|In older Teams Phones versions, you could transfer an active call by selecting a line key that is configured as a speed dial for a specific contact.<br/><br/>Beginning with Teams Phones version 1.7.0 1449/1.0.94.2025165302, you're only able to make an outgoing call to the speed dial after you select it from the **Transfer** menu.|If you want to transfer active calls to specific contacts, configure line keys as speed dials for those contacts and assign the **Transfer** and **Consult Transfer** menu options to the appropriate line keys.|
 
 ## Limitations
 

Teams/teams-rooms-and-devices/teams-rooms-known-issues-windows.md

@@ -22,7 +22,7 @@ appliesto:
   - Microsoft Teams
 search.appverid: 
   - MET150
-ms.date: 06/12/2025
+ms.date: 07/01/2025
 ---
 # Known issues with Teams Rooms on Windows
 
@@ -37,12 +37,10 @@ ms.date: 06/12/2025
 |Teams Rooms device loses internet connectivity after installing a feature update for Windows| A Teams Rooms device that is connected to a network, which requires a proxy can't connect to the internet after installing a feature update for Windows, including an upgrade to Windows 11.<br/><br/>This issue occurs if the proxy setting for internet access on the affected device is configured for the LocalSystem instead of a system-wide proxy. The Windows feature update deletes the LocalSystem settings. This behavior is by design.|If your device has proxy settings set for the LocalSystem user, transfer those settings to the [system-wide proxy settings](/windows/client-management/mdm/networkproxy-csp) that are set and maintained through Mobile Device Management (MDM). Alternatively, you can use the [Set-WinInetProxy](https://www.powershellgallery.com/packages/WinInetProxy/0.1.0) PowerShell cmdlet to configure the system-wide proxy settings.</br></br>When you use system-wide proxy settings, they won't be affected when you install Windows feature updates on the device in future.|
 |Test service plans display in Teams Rooms Pro and Teams Rooms Basic licenses|IT Admins who assign user licenses in the Microsoft Teams admin center or in Microsoft Entra ID see the following test service plans in Teams Rooms Pro and Teams Rooms Basic licenses:<ul><li>Teams Rooms Test 1</li><li>Teams Rooms Test 2</li></ul> | No workaround is required. These service plans don't have any capabilities and can be ignored. They'll continue to display for the lifetime of the two SKUs.|
 |Xbox application window appears on a Teams Rooms device.|In a Teams Rooms on Windows device, when you select **Room Controls** on the console, an Xbox app window appears. In some cases, this window is followed by a pop-up window that displays the following warning message:<br/><br/>In some cases, this window is followed by a pop-up window that displays the following warning message:<br/><br/><i>Gaming Services required</i><br/><br/>The Xbox app is included as part of Windows but should not start automatically.|If you see the warning message, use the following steps to work around the issue:<ol><li>In the Teams Rooms device console, select **More** > **Settings**.</li><li>Select **Windows Settings**.</li><li>Sign in as an administrator.</li><li>Search for and select **Microsoft Store**.</li><li>Select **Library** in the navigation menu.</li><li>Select **Get updates**.</li><li>After all the applications, including the Xbox app finish updating, restart the Teams Rooms device.</li></ol><br/><br/>If you don't see a warning message, use the following steps to prevent the Xbox app from starting automatically:<ol><li>In the Xbox app window that appears, select **Sign in** > **Settings** in the menu.</li><li>Select **General**.</li><li>Uncheck the **Automatically launch app at startup option**.</li><li>Close the Xbox app window.</li></ol>|
-|Chat panel in Gallery view is blank.|You restart a Teams Rooms on Windows device and join a meeting. However you see that the chat panel in Gallery view is empty.<br/><br/>This issue occurs only with the first meeting that you join after restarting your device. Subsequent meetings are not affected.|To fix the issue, update to version 5.2.115.0 of the Teams Rooms app.|
-|The onscreen keyboard on a touch console device is missing or not responsive.|The onscreen keyboard on the touch console in a Teams Rooms for Windows device either doesn't work or doesn't appear.<br/><br/>Because of this issue, you're unable to perform the following actions:<ul><li>Enter text to call another user.</li><li>Add a user to a meeting.</li><li>Enter a username and password to access the Settings menu.</li></ul>|To fix the issue, update to version 5.2.115.0 of the Teams Rooms app.|
 |Teams Rooms device console displays an error message after updating the Teams Rooms app to 5.2.115.0.|You update the Teams Rooms app on your Teams Rooms for Windows device to version 5.2.115.0. As soon as the update is installed, the device console displays the following error message:<br/><br/><i>Teams is experiencing an error.</i><br/><br/>Even after restarting the device, the Teams Rooms app doesn't start.<br/><br/>In this scenario, the error message displays for one of the following reasons:<ul><li>The settings on the Teams Rooms device have been modified to prevent Edge WebView2 Runtime from being installed. The WebView2 control is required for the Teams Rooms app to function.</li><li>The local Skype user account on the Teams Rooms device has been renamed, disabled and replaced with either a different account or an AD/Microsoft Entra ID account.</li><li>Security policies that're applied to the Teams Rooms device are blocking the Skype user account from installing MSIX files.</li></ul><br/>**Note**: There are other scenarios when this error message might appear. However the information provided in this document is specific to Teams Rooms devices that were working as expected until the Teams Rooms app was updated to version 5.2.115.0.|Use one of the following workarounds as appropriate for your scenario.<br/><br/>**Edge WebView2 Runtime missing**<br/><br/>If the Edge WebView2 Runtime is not installed, use the following steps to install it:<ol><li>On the Teams Rooms device console, select **More** > **Settings**.</li><li>Select **Windows Settings**. </li><li>Sign in as an administrator.</li><li>Open Microsoft Edge and navigate to the [download page for Edge Webview2 Runtime](https://developer.microsoft.com/en-us/microsoft-edge/webview2/?form=MA13LH#download).</li><li>Select "x64" in the **Evergreen Standalone Installer** option to download the installer.</li><li>Browse to the downloaded installer file, then right-click and select **Run as administrator**.</li><li>After WebView2 Runtime is installed, restart the Teams Rooms device.</li></ol><br/>**Skype account modified**<br/><br/>If you modify the local Skype user account on the Teams Rooms device, the device breaks. Because [modifications to the Skype user account are not supported](/microsoftteams/rooms/security?tabs=Windows#software-security), the Teams Rooms device must be reset with the factory recovery media.<br/><br/>After the reset, the Skype user account must be left in its default state to ensure that the Teams Rooms app functions correctly.<br/>**Security policies blocking MSIX installation**<br/><br/>When you update to version 5.2 of the Teams Rooms app, there is no provision to fall back to an older version of the app. So if a security policy blocks non-admin users such as the Skype user account from installing MSIX files, the new Teams Rooms app will fail to launch. You need to update your security policies to resolve the issue.|
 |Unable to join some Webex meetings|When you select the **Join** button to join a Cisco Webex meeting from a Teams Rooms on Windows device, you're not connected to the meeting and see the home screen on the device instead.|No workaround is available at this time. Cisco is investigating the issue.|
 |Only see one camera's view even though multi-camera feature is turned on.|Your Teams Rooms on Windows device is configured for multiple cameras. However after the device restarts, remote users might see only the default camera's view.<br/><br/>This issue might occur only in the first meeting after the device restarts. The cameras function as expected in all subsequent meetings.|To work around the issue, end the first meeting after the device restarts, and start a second meeting.|
-|Front of Room view displays a blank, black screen on a remote access tool.|When you access a Teams Rooms on Windows console remotely by using tools such as the Teams Rooms Pro Management Portal (PMP), TeamViewer, Virtual Network Computing (VNC) etc., the Front of Room (FoR) monitors display a black image instead of the expected user interface.<br/><br/>The FoR monitors in the meeting room display the expected screen but show only a black image in the view on the remote access tool.<br/><br/>If you sign in to the Teams Rooms device by using administrator credentials, you see the Windows screen in the FoR view as expected.|No workaround is available at this time.|
+|Front of Room view displays a blank, black screen on a remote access tool.|When you access a Teams Rooms on Windows console remotely by using tools such as the Teams Rooms Pro Management Portal (PMP), TeamViewer, Virtual Network Computing (VNC) etc., the Front of Room (FoR) monitors display a black image instead of the expected user interface.<br/><br/>The FoR monitors in the meeting room display the expected screen but show only a black image in the view on the remote access tool.<br/><br/>If you sign in to the Teams Rooms device by using administrator credentials, you see the Windows screen in the FoR view as expected.|Restart your device to update to the latest configuration to fix the issue.|
 
 ## Hardware issues