Caleb Baker

Posting a quick personal update. It’s time for me to try something new. I recently moved off the Conditional Access team but I'm happy to be continuing to work on Entra, in a new area. Over the years I've worked on CA, I'm thankful for having worked with so many of you.

(2/2) I still have a lot more to learn, so I'd love to hear your thoughts and feedback on our new offerings - please don't hesitate to reach out!

(1/2) A little while back I joined the team working on our new SSE offerings that announced today, Microsoft Entra Private Access and Microsoft Entra Internet Access. microsoft.com/en-us/security… It's been great. Awesome team and an exciting new area. #MicrosoftEntra #SSE

Tomorrow, I get to start talking about what I'm working on now and I'm very much looking forward to it. info.microsoft.com/ww-reimagine-s…

I’m looking forward to working with many of you again in the future. Looking back, it’s amazing to see the evolution of CA and I’m excited to watch all that is yet to come.

Posting a quick personal update. It’s time for me to try something new. I recently moved off the Conditional Access team but I'm happy to be continuing to work on Entra, in a new area. Over the years I've worked on CA, I'm thankful for having worked with so many of you.

@JefTek @azuread More details here #all-cloud-apps" target="_blank" rel="nofollow noopener">learn.microsoft.com/azure/active-d…

@tuna_gezer @NoUselessTech @DrAzureAD @JefTek The easiest way would be to use an 'in private' browser session. So, using device enrollment information isn't very hard to circumvent as well, as long as there are gaps in the platforms covered by policy.

@tuna_gezer @NoUselessTech @DrAzureAD @JefTek There are cases we'll use the information from device enrollment to determine platform, but this is really just best effort and when the information is already available. It's pretty easy for a registered enrolled device to appear like an unknown device.

@tuna_gezer @NoUselessTech @DrAzureAD @JefTek For example, if a policy requires a compliant device, but only for iOS, it would be really disruptive to for users on any device to register, so device platform can be determined.

@tuna_gezer @NoUselessTech @DrAzureAD @JefTek We describe the behavior in the docs here learn.microsoft.com/en-us/azure/ac… But the doc linked earlier in the thread needs some additional clarification.

@thijslecomte @dougsbaker @azuread This should no longer be an issue. Be sure to hit F5, then let me know if you're still seeing a problem.

@Caleb_B @dougsbaker @azuread Good to know, thank you ;)

@Caleb_B or @azuread what am I doing wrong here? all of a sudden I can't configure a risk-based CA policy with every time sign in frequency.

@thijslecomte @dougsbaker @azuread Also, this is UX only bug. As a workaround you can use MS Graph or PowerShell.

@thijslecomte @dougsbaker @azuread Will do. Turns out this is a known issue, and a fix has been made, just needs to go through validation and deployment.

@dougsbaker @thijslecomte @azuread I'm seeing a repro now. It must be related to new deployment. Looking into it now, thanks for reporting it.

@thijslecomte @Caleb_B @azuread Yeah sorry, it's only when I try to set it up new. my existing one is fine.

And for those of you who missed the announcement and are wondering what I'm talking about 😄 here's the filters for apps blog post techcommunity.microsoft.com/t5/microsoft-e…

We also know of one odd issue with the 'learn more' link on the filters for app page. Some characters were added to the end of link, that's stopping it from working. We have a fix rolling out. It's supposed to go here: learn.microsoft.com/azure/active-d…

Thanks again to everyone who could join us this week as we discussed the new Conditional Access filters for apps. If you missed it, you are still able to listen to the recording. Also, if you have feedback on filters for Conditional Access in general: