Skip to content

Commit d870a39

Browse files
committed
acrolinx updates
1 parent 3954ebb commit d870a39

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/virtual-desktop/troubleshoot-teams.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -13,15 +13,15 @@ This article describes known issues and limitations for Teams on Azure Virtual D
1313

1414
## Known issues and limitations
1515

16-
Using Teams in a virtualized environment is different from using Teams in a non-virtualized environment. For more information about the limitations of Teams in virtualized environments, check out [Teams for Virtualized Desktop Infrastructure](/microsoftteams/teams-for-vdi#known-issues-and-limitations).
16+
Using Teams in a virtualized environment is different from using Teams in a nonvirtualized environment. For more information about the limitations of Teams in virtualized environments, check out [Teams for Virtualized Desktop Infrastructure](/microsoftteams/teams-for-vdi#known-issues-and-limitations).
1717

18-
### Client deployment, installation, and setup
18+
### Client deployment, installation, and set up
1919

2020
- With per-machine installation, Teams on VDI isn't automatically updated the same way non-VDI Teams clients are. To update the client, you'll need to update the VM image by installing a new MSI.
2121
- Media optimization for Teams is only supported for the Remote Desktop client on machines running Windows 10 or later or macOS 10.14 or later.
2222
- Use of explicit HTTP proxies defined on the client endpoint device should work, but isn't supported.
2323
- Zoom in/zoom out of chat windows isn't supported.
24-
- Media optimizations is not supported for Teams running as a RemoteApp on macOS endpoints.
24+
- Media optimizations isn't supported for Teams running as a RemoteApp on macOS endpoints.
2525

2626
### Calls and meetings
2727

@@ -35,7 +35,7 @@ Using Teams in a virtualized environment is different from using Teams in a non-
3535
- If you've opened a window overlapping the window you're currently sharing during a meeting, the contents of the shared window that are covered by the overlapping window won't update for meeting users.
3636
- If you're sharing admin windows for programs like Windows Task Manager, meeting participants may see a black area where the presenter toolbar or call monitor is located.
3737
- Switching tenants can result in call-related issues such as screen sharing not rendering correctly. You can mitigate these issues by restarting your Teams client.
38-
- Teams does not support the ability to be on a native Teams call and a Teams call in the Azure Virtual Desktop session simultaneously while connected to a HID device.
38+
- Teams doesn't support the ability to be on a native Teams call and a Teams call in the Azure Virtual Desktop session simultaneously while connected to a HID device.
3939

4040
For Teams known issues that aren't related to virtualized environments, see [Support Teams in your organization](/microsoftteams/known-issues).
4141

0 commit comments

Comments
 (0)