Відео

nice video sir

Excellent!

Hi can you please explain the workflow for the identity protection..how the detection work,how investigation work and how remediation work and how the policies are framed..what is the use of conditional access policies and device compliance... please explain in detail

Hi John, great introduction. One comment to bypassing protected actions - admins could just delete protected Action to circumvent it and nothing prevents it.

Really nice video! Greetings from Brazil!

You ROCK! Your guide is better than the doc. Thanks a lot!

Very well done! I can't wait to up my CA skills with your other videos in the series!

Thank you for this useful video, but when will this feature be released out of preview mode ?

I learnt ADFS watching your videos many years ago :) (I can tell by your voice that you was the instructor behind the slides). Thank you very much for another great video.

One of my Favorite channels. Thanks so Much!!

subscribed! great stuff, thank you so much for not just reading the settings like some other youtube trainers but providing context and behind the scenes info, hugely appreciated!

Hi John, Thank you for this crystal clear insight into Authentication methods. My question is this: How to migrate legacy MFA/authentication methods to the new Entra/Azure AD Authentication method policies for multiple tenants at once? Thanks for your insights in advance!

With the SKI the smartcards could be anonymous and even pre-issued, that’s quite neat in addition to the high affinity. Is there an drawback if you don’t have attributes (for this specific Entra ID Login case)

When using windows Keystore, it should use the cryptong rsa provider, as it uses credential isolation. And potential even tpm, but I am not sure how to enforce this.

Even better than the last one. Thank you! Curious as to why you opted to use Pipedream instead of an Azure Function, especially since you did not validate the token in Pipedream.

Phenomenal. Thank you very much!

Nice video.

hi, after 5 months seems that UDP and private dns feature for private access is still not present. Do you have any idea of when will be ready ?

please do this for .net web core api with entity framework

Short of pausing the access client, is there any way to keep traffic from routing through the proxies when the PC is actually on the on-prem network?

I love the way you explained this in a way that is easily understandable. Subscribed.

These videos are great! Very clear concise explanations. I am learning alot from your vids. Thank so much!

Great content again, John! Thanks.

Thanks John. It's a shame the protected actions list is a little small right now but it's a good start. I would love to see adding a federated domain isn't included as a protected action.

Happy Christmas 🎄 and Happy December to you and your family Sir , Best wishes for everyone from Kolkata, West Bengal, India 🇮🇳

Awesome video - Thank you very much for sharing and explaining!

Great video John 👌

Thanks John, As per your commitment in one of the videos to make one video per week but I didn't see many uploaded recently. Can you please clarify when you gonna upload videos on other Authentication and Authorization methods. Thank you 😊

Your videos are amazing because you explain what you are doing.

Thank you for the video!

So informative. Thank you.

What a great video! I struggled with my understanding of modern authentication on some points. This helped me a lot.

Wow, Thanks for making it .

This was just ... well ... fantastic! Thanks a lot, I learnt a lot from this.

This content was so very helpful, your lab setup to see and test the token information is phenomenal. I wish I could duplicate this, to get a much better understanding of the authorization myself! Thanks John

Nice Work

What if you have users in an Azure Only environment without any server?

You bet John! Keep up the good work. Appreciate it! 👍

Hi John, thank you so much for you video. Can you explain how to create the other certificate templates, like CBAUserSetName and others, I'm a little confused in that step. Thank you so much.

I like anyone who goes back and edits in missing information afterwards (e.g. 'along with their public key' comment at 2:50). That shows thorough attention to detail and an awareness of the perspective of learners. Thanks very much.

John, I followed your steps to the letter but as soon as I test my pilot user , I put in the OTP and the it says Great job done. Then it loops repeatedly. I think this may be due to the Ssrp perhaps? This user doesn’t have a cell phone .. not kidding 😢 . how can I get around this or exclude them from forces to register a cell number . Thanks

This is completely irrelevant for modern cloud based Microsoft 365 Entra

Thank you for the interesting video. Maybe you know, how I can handle the MFA via Postman?

Amazing ! I like it ! Thank you so much ! Please could you share with us the url of your azure ad application for open id connect and oauth2.0 demo ?

thank you for sharing; it is very insightful and appreciated conversation. Absolutely, deep dive into the integration of on protocols like: kerberos, ntlm, ipsec, ikev1 how they fit in end to end in the Micrsoft Entra Architecture, would be edifying.

• Microsoft Entra (formerly Azure AD) Global Secure Access allows secure access to on-premises apps and resources through the cloud. It combines networking and identity. • It is currently in public preview, released on July 11, 2022. It will go through feedback and feature additions before general availability. • The components are Entra Internet Access and Entra Private Access. • Licensing will likely be a per user per month model, similar to other Microsoft 365 licenses. It may be included in E3/E5 or a separate premium SKU. • UDP support is planned for Q3/Q4 2022 calendar year. • More features and capabilities ("more goodness") are planned for release over the next weeks/months. • Private Access currently uses a proxy connector, separate from the App Proxy connector. In the future they will merge into one connector. • Multi-cloud support allows deploying connectors in Azure, AWS, GCP etc to bridge those environments. • It supports multi-session Windows Virtual Desktop, with some limitations currently. • It respects the native authentication protocol of the app, e.g. Kerberos or NTLM. • Private DNS resolution is on the roadmap but not supported yet. Traffic acquisition profiling allows accessing private resources for now. • Integration with SD-WAN solutions is planned further down the roadmap.

Thank you very much. It is easy to understand and learn.

Great Video..Expecting more

Very informative

Beautifully explained. Thx for taking your time to explain me this CA feature, I haven't been able to cover yet. P.S. The groove at the end of the video sounds like UB40, isn't it?