View the original community article here
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:
- Not using the callback url, eg input
https://instance.looker.com
instead ofhttps://instance.looker.com/samlcallback
- There is a different host url in Admin/Settings than what is inputting into Azure (if for example, they have a vanity URL)
This content is subject to limited support.