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.
(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. https://t.co/3gm94YrHrS
It's been great. Awesome team and an exciting new area.
#MicrosoftEntra#SSE
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.
@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 https://t.co/3mCgGf3z0S
But the doc linked earlier in the thread needs some additional clarification.
@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.
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 https://t.co/0b3evwRUp3
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:
Who doesn't love Conditional Access in Azure AD?
Tomorrow you get to ask anything from the folks that build the feature plus get the ins and outs of all the new CA features that have come your way.
Click Set Reminder below! ๐
https://t.co/u4E1vAg9lU
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: https://t.co/Uc65aiCj8A