Last tested: Aug 19, 2020
Every case of this we have documented is due to some attribute of the /samlcallback url they're inputting into Azure being incorrect. Specifically:
https://instance.looker.com
instead of https://instance.looker.com/samlcallback
This content is subject to limited support.