A family of System Center products that enable enterprise-wide management of virtual machines.
In Teams on AVD/VDI, this symptom usually points to a screen-sharing rendering or version issue rather than a meeting policy issue, especially since audio, video, and Whiteboard are working.
Check these items in order:
- Verify whether Screen Capture Protection is enabled on the AVD session.
- In optimized Teams for VDI, Screen Capture Protection can cause the presenter’s shared screen to appear as a black screen with only the mouse cursor.
- This is fixed only when both of these minimum versions are met:
- Teams 25060.205.3499.6849
- Remote Desktop client 1.2.6081 or Windows App 2.0.379
- If versions are lower, update them first.
- Check whether full monitor sharing is being used.
- In optimized VDI, full monitor sharing captures the Teams call monitor window itself.
- Other participants can see that call monitor, but video elements inside it appear as blank squares.
- Test with app/window sharing instead of full monitor sharing.
- If the issue is app sharing and the shared window freezes or becomes blank, stop sharing and share again.
- In Citrix environments, app sharing can freeze for other participants when a video element is destroyed during the session.
- A known workaround is to stop and reshare the window.
- This issue is resolved in Teams 24335.206.X.X or later.
- Check for cursor lag or sharing instability during app sharing.
- In some optimized VDI scenarios, app sharing can have mouse dragging or cursor lag.
- Stopping and reinitiating app sharing removes the lag.
- This is fixed in Teams 26149.x.x.x or later.
- Confirm the AVD network path allows VM-side screen sharing if that mode is in use.
- For AVD/W365, VM-side screensharing requires administrators to allow ID 11 and 12 on the VM network as described in Microsoft 365 URLs and IP address ranges.
- If this path is blocked, screen sharing can fail even when audio/video still works.
- Review resource usage on the AVD VM.
- In optimized VDI, outgoing screen sharing uses device and VM resources such as CPU, GPU, RAM, and network.
- If the user selects Optimize for video, Teams can ramp screen sharing up to 15 fps, which increases CPU usage.
- If CPU pressure is high, reduce load by avoiding Optimize for video for normal document sharing.
- If using Mac endpoints with AVD/W365, note a platform limitation.
- Outgoing screen sharing in end-to-end encrypted meetings is disabled on Mac endpoints.
Most likely causes for the exact “sharing” popup with no visible content for either side are:
- Screen Capture Protection enabled with unsupported Teams/Remote Desktop client versions
- Using full monitor share in optimized VDI and expecting the Teams call content to be visible
- A VM-side screen-sharing/network configuration issue in AVD
A practical test path is:
- Update Teams and the Remote Desktop client/Windows App to the minimum supported versions above.
- Start a new meeting.
- Share a single app window instead of the full desktop.
- Do not use Optimize for video for the test.
- If it still fails, have the AVD admin verify VM-side screen-sharing network requirements for ID 11 and 12.
References: