I work mostly with Cisco Jabber but I imagine it behaves similar. While the traffic is wrapped in TLS it is likely operating on a non-standard port for some of that data precisely so it can be identified. Looking at Microsoft's documentation that appears to be true. Particularly the audio, video and desktop sharing ranges. Which are probably the ones you care about the most.
That said you can set DSCP in a lot of ways. I tend to take the approach of trust but verify, in other words I check everything with an ACL to make sure it is marked appropriately. You can use Microsoft's own published address list and port number ranges to build a policy for the ports and IPs related to the actions you want to protect.
Just make sure to translate DSCP values appropriately between wired and wireless appropriately.
Microsoft's list:
https://support.office.com/en-us/articl ... 2#bkmk_lyo
MikroTik WMM Wiki:
https://wiki.mikrotik.com/wiki/Manual:WMM