With the Real-Time Audio-Video feature, you can use the client machine's webcam or microphone in a remote desktop or published application. Real-Time Audio-Video is compatible with standard conferencing applications and browser-based video applications, and it supports standard webcams, audio USB devices, and analog audio input.
Real-Time Audio-Video is supported only in Chrome, Microsoft Edge, and Firefox. The default video resolution is 320 x 240. The default Real-Time Audio-Video settings work well with most webcam and audio applications.
When a remote desktop or published application is connected to the client machine's webcam or microphone, before the remote desktop or published application can use to the webcam or microphone, the browser might ask for permission. Different browsers behave differently.
Microsoft Edge asks for permission every time. You cannot change this behavior. For more information, see https://blogs.windows.com/msedgedev/2015/05/13/announcing-media-capture-functionality-in-microsoft-edge.
Firefox asks for permission every time. You can change this behavior. For more information, see https://support.mozilla.org/en-US/kb/permissions-manager-give-ability-store-passwords-set-cookies-more?redirectlocale=en-US&redirectslug=how-do-i-manage-website-permissions.
Chrome asks for permission the first time. If you allow the device to be used, Chrome does not ask for permission again.
When a remote desktop is connected to the client machine's webcam or microphone, an icon for each device appears at the top of the sidebar. A red question mark appears over the device icon in the sidebar to indicate the permission request. If you allow a device to be used, the red question mark disappears. If you reject a permission request, the device icon disappears.
If Real-Time Audio-Video is being used in a remote desktop or published application session and you open a connection to a second remote desktop or published application, and if a security warning appears (for example, if a valid certificate was not installed), ignoring the warning and continuing to connect to the second remote desktop or published application causes Real-Time Audio-Video to stop working in the first session.