Hello,

I’ve been looking and the Conditional Access Policy for Token Protection but before implementing I checked Azure Sign-In logs. What I found is that when I use mu admin credentials (different than my user credentials) to access for example Azure Portal, Token Protection Sign in Session value is “Unbound”. When I use my standard user, all sign ins are logged with the Token value “bound”. We use hybrid joined devices. I have checked with my colleague and his Token Protection values are always “bound”, no matter if he uses his standard or admin account. What can be the reason? I cannot find much information about how to troubleshoot it. I’m worried that when I enable CA policy, I will cut myself off. 

​Hello, I’ve been looking and the Conditional Access Policy for Token Protection but before implementing I checked Azure Sign-In logs. What I found is that when I use mu admin credentials (different than my user credentials) to access for example Azure Portal, Token Protection Sign in Session value is “Unbound”. When I use my standard user, all sign ins are logged with the Token value “bound”. We use hybrid joined devices. I have checked with my colleague and his Token Protection values are always “bound”, no matter if he uses his standard or admin account. What can be the reason? I cannot find much information about how to troubleshoot it. I’m worried that when I enable CA policy, I will cut myself off.   Read More

​