The short answer
Use console-generated or officially documented Protect export endpoints. Importing third-party ONVIF cameras into Protect does not prove that Protect cameras export ONVIF or work with every viewer.
Work through the checks
Identify the camera by model, hardware revision, firmware and MAC address. Keep this inventory separate from passwords; two devices with similar names may expose different protocols.
Obtain an explicitly supported export URL from the UniFi Protect console or documented API. An RTSPS URL is not interchangeable with RTSP by editing its scheme, and importing ONVIF cameras is a separate workflow.
Decide whether the source is the camera itself or an NVR channel. Use the recorder address and recorder account for a recorder-provided stream, and check its channel numbering separately.
Test only the configured device and service port from the Windows computer. A successful TCP connection proves reachability to that port, not correct credentials or a decoded video image.
What to verify
Write down the exact outcome you need: live observation, a saved event, camera movement or long-term retention. Check each outcome separately instead of treating a visible stream as proof of all functions.
Sources and scope
AeoCam is available for Windows. Camera settings below describe protocol preparation, not a certification of a particular camera or a promise of every feature in every app version. Check the installed build and the Microsoft Store listing for current availability.
Vendor documents describe the camera or protocol. No physical-camera compatibility test is claimed here. Menus and capabilities can change with model and firmware.