Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
You can organize Microsoft eCDN supported live events in Viva Engage.
Microsoft Teams-powered live events
Viva Engage uses Microsoft Teams as the video broadcasting engine. The steps to enable Microsoft eCDN for this production type are the same as the steps for Teams live events. Follow this guide: How to Enable Microsoft eCDN for Your Tenant.
Optimizing Viva Engage browser performance
Microsoft eCDN requires that specific browser policies be configured so the service can collect NIC and local IP information from browser clients. Deploying the policy described below (VideoCaptureAllowedUrls) is required for Microsoft eCDN to function with Viva Engage live events. Without this configuration, eCDN cannot reliably assign viewers to the correct subnet groups, which can cause reduced peering efficiency and increased buffering or offloading to origin servers during high‑concurrency events.
Important
This policy is required for Microsoft eCDN to operate correctly with Viva Engage live events. Configure and deploy the VideoCaptureAllowedUrls policy to your managed browsers and devices before users join events.
VideoCaptureAllowedUrls
Configure the VideoCaptureAllowedUrls policy to explicitly allow video (camera) access for the Viva Engage domain.
| Registry element | Value |
|---|---|
| Path for Microsoft Edge | HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\ |
| Path for Google Chrome | HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\ |
| Key name | VideoCaptureAllowedUrls |
| Value name | 1 or other numeric value |
| Value 1 | https://engage.cloud.microsoft/ |
Firefox
Firefox doesn't expose an equivalent enterprise policy. Firefox administrators must rely on user-granted permissions for camera access; consider documenting this limitation for Firefox users.
Security and privacy
This policy only affects the specified Viva Engage origin (engage.cloud.microsoft) and doesn't change camera permissions for other sites. This configuration doesn't grant any greater camera privileges than a user explicitly allowing camera access in Teams or Teams on the web; it only removes the per‑visit prompt for the specified origin. Follow your organization's privacy approval process before deploying this policy.
How it works
- When a user joins a Viva Engage live event the browser checks whether camera access has been granted for the site.
- If camera access is available (via policy or previous user consent) the Teams iframe includes
allow="camera"and the page can collect full NIC and local IP information. - The extra NIC data enables accurate subnet assignment and stronger peer selection for eCDN, improving peering efficiency and reducing server load.
Benefits
- Improved peering efficiency and reduced buffering for large Viva Engage events
- More accurate subnet group assignment for multi‑NIC endpoints (for example, for viewers with always‑on VPNs)
- Reduced risk of network saturation during high‑concurrency events
Reversibility
To remove the configuration, delete the VideoCaptureAllowedUrls value or key. After removing the registry entries and restarting the browser, the Viva Engage website will no longer have camera permissions.
Important
Deploy these policies before users join Viva Engage live events. This configuration supersedes the WebRtcLocalIpsAllowedUrls setting described in How to Disable mDNS.