Distinguish sleeping from discarded tabs
Microsoft explains that sleeping pauses background activity while discarding removes the page from memory and requires a reload when revisited. Those are different outcomes. A page reloading after a long inactive period can lose its local playback position or require session recovery.
Microsoft also documents activities that normally prevent sleeping, including active audio and casting. Do not assume that every background playback issue is caused by sleeping tabs; compare the actual page state and service behaviour.
Use a specific site decision where justified
Edge offers a site list for pages that should remain active. If the service’s supported workflow needs it, evaluate that site-specific option instead of disabling all performance features without a diagnosis.
Keep browser version and the relevant setting in the record. Performance features and their interface can evolve, so the current Microsoft guidance should take precedence over an old screenshot.
Separate Windows and browser playback
Windows Media Player, a native third-party app and Edge may use different media paths. A codec extension relevant to one Windows app does not guarantee that a website supports the same stream or account in Edge.
When a web video fails, first state whether sign-in succeeded, the player loaded and the error appeared before or during media playback. That gives a clearer support starting point than changing every system video setting.
Protect the account during cleanup
Clearing cookies or using a new browser profile changes site state and can sign you out. Keep the legitimate recovery details and avoid posting a private playback URL. A clean-session test is useful only when its changed conditions are recorded.