Hi Rahuleo
Thanks for the detailed write‑up, based on your testing, this looks like a behavior difference between the Windows OS projection flow and the Teams Rooms (MTR) experience.
Miracast itself is working correctly (since the PIN and connection flow function as expected in the Windows session), but in the MTR interface the PIN/approval UI is not surfaced, so the “Ask for PIN every time” scenario cannot complete.
For now, workarounds would be to allow casting without PIN or approve the request from the Windows admin session. I’d also recommend submitting feedback or opening a support request so the product team can review this behavior (note: as this is a public forum, we don’t have visibility into backend logs or the ability to escalate cases directly):
- On the device: More (…) > Settings > Report a problem
- Admin side: Microsoft 365 admin center > Support > New service request
- Windows feedback: Feedback Hub > Devices > Projection/Connect
This helps ensure the issue is properly reviewed by the Teams Rooms / Surface Hub engineering team.