You can do it, but is it a "best practice approach?", no it's not.
You should consider that MAC Authentication Bypass (MAB) uses MAC addresses which are trivial to spoof, especially on Windows. There is no cryptographic binding between the device, the user, and the network. MAB is mostly suitable only for non-802.1X-capable devices (printers, cameras, IoT).
For Windows, you can run on EAP-TLS or EAP-TEAP (EAP-Chaining).
EAP-TLS would be a Certificate-based authentication which can be considered as resistant to credential theft, replay, and spoofing. It works natively with Windows.
EAP-TEAP on other hand uses the combination of machine & user authentication in a single flow. It supports certificate-based authentication & credential or cert-based user authentication.
------------------------------
Shpat | ACEP | ACMP | ACCP | ACDP
Just an Aruba enthusiast and contributor by cases
If you find my comment helpful, KUDOS are appreciated.
------------------------------