Do you support PEAP, MSCHAPv2 or EAP-TTLS?

No. Passbeam only does EAP-TLS. Both sides use a certificate. The device proves who it is with a certificate from the client's own authority, and Passbeam proves who it is with a certificate the device already trusts.

PEAP-MSCHAPv2 and EAP-TTLS/PAP send a username and password inside a TLS tunnel. They're only safe if every device checks the server's certificate. One device that doesn't, near a fake access point with the right network name, gives away a password that works everywhere that person uses it. EAP-TLS has no password to give away.

There's also nothing to change when someone leaves. A shared Wi-Fi password is known by everyone who ever worked there. A certificate belongs to one device or one person, and stops working when their account does.

If a device is set to PEAP, it replies to Passbeam with the methods it wants instead, and the authentication log says so. Change the setting on the device. The 802.1X profiles Passbeam creates for Intune and other MDMs already set it correctly.