Forum Discussion
Conditional access policy not recognised
Hello everyone, We're evaulating Cloud Apps session/conditional access/session policies but have hit a weird snag. We have created a conditional access policy in EntraID with session control ...
Hi Mark,
I've actually got the exact same issue. I'm trying to block print from OWA on a non-compliance device. The creation of the CA and the Session Policy is very straightforward as you could also have noticed. However, I'm getting the same error.
The admin user has the Defender for Cloud Apps license applied; I've also applied the same license to the target users, but it hasn't made any difference.
Any luck from Microsoft Support?
Meantime if I find the cause of that error message, I will let you know.
I've actually got the exact same issue. I'm trying to block print from OWA on a non-compliance device. The creation of the CA and the Session Policy is very straightforward as you could also have noticed. However, I'm getting the same error.
The admin user has the Defender for Cloud Apps license applied; I've also applied the same license to the target users, but it hasn't made any difference.
Any luck from Microsoft Support?
Meantime if I find the cause of that error message, I will let you know.
Hi davide984
Still with MS support, I'm afraid. They've informed me that our EntraID tenant and Exchange Tenant do not match and asked us why. I've informed them that we've done nothing knowningly to make them different, if it were even possible for us to do so. They've gone back to the back end team for further investigation.
We've extended our trial, but it's frustrating that this showstopper doesn't seem to have an easy fix.
Still with MS support, I'm afraid. They've informed me that our EntraID tenant and Exchange Tenant do not match and asked us why. I've informed them that we've done nothing knowningly to make them different, if it were even possible for us to do so. They've gone back to the back end team for further investigation.
We've extended our trial, but it's frustrating that this showstopper doesn't seem to have an easy fix.