> I am looking for directions to setup port security using a Microsoft NPS and MAC addresses.
This is not so much a Meraki issue, as a limitation on Microsoft NPS capabilities. Microsoft NPS can do this - you have to create a username in AD that is the MAC address and also make the password the MAC address.
I don't personally like how NPS does it this way, as anyone can now try logging into AD using the MAC address of a device on your network.
Only NPS (to my knowledge) does it this way - but it is "free" (as in, included in your Windows Server licence). You get what you pay for ...
It is more common with wired NPS deployments to use PEAP+MSCHAPv2 authentication. This lets you authenticate all AD members based on either (or both) of the computer AD account and the user AD account. You can also do EAP-TLS authentication, where you authenticate using a certificate (actually there are lots of options - these are my favourite two).
If you want to authenticate things like printers, you are more likely to get EAP-TLS working.
Note that you can have both methods enabled at the same time.
Meraki switches do support "port security" with a static MAC whitelist. This doesn't use RADIUS, or anything external.
https://documentation.meraki.com/MS/Port_and_VLAN_Configuration/Switch_Ports#Port_configuration
You can also mix both approaches. Use port security with a static MAC whitelist for switch ports used with printers and the like, and wired 802.1x with Microsoft NPS for "windows" switch ports.