Authorization only with certificate takes over the default Sign in policy

[KevinW_]

If I create a new sign in for an authorization only policy(A), and then specify the site internally to point to a particular host which is in use for the default sign in policy(B) already, then the auth only policy(A) takes over the default sign in policy settings.

This is in the post i raised earlier, but this is another issue.

I have a default sign in policy which is using a certificate on the external interface which directs to our internal web server. If I configure the auth only policy, with a new certificate, on a new IP address, and point to the same resource as what is specified in the default one, then when I goto the default one I get the settings which have been applied in the auth only policy and not the default one.

Its like, you cant use the same resource for both a normal sign in page setup, and an auth only policy at the same time or the auth only one takes priority.

As far as I can see it should work seperately but its not working like

again, any help would be appreciated on how this is supposed to work. I have followed the docs on this, but it does not explain anything which is related to this problem I am seeing.

[KevinW_ · Accepted solution]

I found a line in the documentation:

If the IVE is used for OWA & Activesync, the hostnames for OWA access and

Activesync must be different

I think this is the cause of the problem because I am using the same exchange server for the auth only policy as what is published as the owa access.