Define "easy". What you consider easy may be difficult for someone else or very difficult for a bot. For example a1b2c3d4e5
is a very simple password for a human to figure out but a bot would probably struggle with it. There are lists of weak passwords that are available but in my experience MS doesn't use any of that. We use Azure B2C and every security pen test we get flagged for allowing "weak" passwords.
The best way to prevent "easy" passwords is to increase the password complexity rules. Changing the required char classes to include all types (upper, lower, digits, symbols) prevents simple passwords but not things like qwerty_1234
or qwerty_!234
. Unfortunately I don't know that you can do anything more complex. Intune, AFAIK, doesn't support custom password policies.