Thank you for your response Timothy. I'll try bringing the utilization of Azure AD into the discussion but i feel there may be some hesitation due to the fact we have just adopted OneLogin...
That point aside..
After asking this question in other discussion forums, some suggest using the CNAME method?I've tried researching some of the responses I've received and can't seem to come to a conclusion. I know CNAME involves utilizing the DNS, but I don't believe HTTP redirect does?
Are there any pros vs. cons you're aware of?
Thanks
Alex Kim Use OneLogin to provide SSO into O365/Azure AD then.
And then this:
https://www.pluralsight.com/blog/tutorials/iis7-redirect-windows-server-2008
301 or 302 Scenario -
Pro: it is pretty lightweight and shouldn't be too bad to implement potentially.
Cons: It's a server - so it needs SLA maintenance - it may also be do-able with with a firewall too.
